diff --git a/Google-Summer-of-Code-2016.md b/Google-Summer-of-Code-2016.md
index 96b7b31..6aad009 100644
--- a/Google-Summer-of-Code-2016.md
+++ b/Google-Summer-of-Code-2016.md
@@ -274,20 +274,22 @@ irc.freenode.net](https://kiwiirc.com/client/irc.freenode.net/openkeychain))
 if the secret key is no longer accessible (either the actual key has
 been lost or its password forgotten), and is usually the last recourse in
 such cases. This task would involve allowing OpenKeychain to both generate
-and use revocation certificates.
+and use revocation certificates. This is more of a UX design and UI
+implementation problem than a technical challenge, since the operations
+in question are already supported in the backend. As such, it is well
+suited for getting to know the Android framework and first steps in user
+interface design.
 
 The two components:
-<ul>
-<li> Creation: Allowing users to create a revocation certificate for a given
+* Creation: Allowing users to create a revocation certificate for a given
 key from within OpenKeychain (this would involve saving the revoked public key).
-<li> Application: Revocation certificates come in two forms - as a revoked public key,
+* Application: Revocation certificates come in two forms - as a revoked public key,
 and much less frequently, as a detached revocation signature. In the case of
 the latter the certificate must first be applied to the correct public key before
 proceeding. In either case, the revoked key must then be uploaded to a keyserver to 
-complete the revocation process. The revocation and upload should be atomic.
-</ul>
+complete the revocation process.
 
-This is a smaller task which we expect to take only one or two weeks, which
+This is a smaller task which we expect to take only a couple of weeks, which
 makes it suitable as a secondary goal and providing a change of pace for some
 time while working on another task.