fix #18 by clarifying we are working from useaibility, incremental de…

…ployment

perspectives.

doc/index.rst

@@ -37,14 +37,15 @@ The technical Autocrypt approach
 --------------------------------------
 
 Autocrypt uses regular e-mail messages between people to piggyback
-necessary information to allow encrypting subsequent messages.  
-Under the hood, Autocrypt uses e-mail headers for this information
-transfer. By default, no key management is visible to users.
-See :doc:`features` for more technical and UI cornerstones.
-
-We are establishing this approach step-by-step using different "Levels"
-of implementation compliance.  We are currently documenting :doc:`Level
-0 <level0>`, which we aim to see supported in Spring of 2017 by various
-mailers.
+necessary information to allow encrypting subsequent messages; it
+adds a new "Autocrypt" e-mail header for transfering keys and 
+driving encryption behaviour. By default, key management is not visible 
+to users. See :doc:`features` for more technical and UI cornerstones.
+
+We are following this approach step-by-step using different "Levels"
+of implementation compliance.  Driven by usability concerns, we are
+refining and implementing :doc:`Level 0 <level0>` in several mail apps
+during spring 2017.  If you are interested to help please :doc:`join our
+channels and look at where we meet next <contact>`.
 
 See :doc:`contents` for an index of all docs and discussion results so far.

doc/level0.rst

@@ -1,13 +1,20 @@
-Guidance for Implementers of Autocrypt Level 0
-==============================================
-
-This document describes the basic capabilities required for a MUA to
-be Autocrypt-capable at Level 0.  Some Autocrypt-capable clients may
-choose to go beyond these features, and future Levels of Autocrypt may
-require more specific control.
-
-Throughout this document, we refer to a Mail User Agent (MUA) as
-though it was only capable of controlling a single e-mail account.  A
+Autocrypt Level 0: Enabling encryption, avoiding annoyances
+===========================================================
+
+This document describes the basic capabilities required for a mail app (MUA)
+to be Autocrypt-capable at Level 0.  The design of Level 0 is driven by
+usability concerns and by the realities of incremental deployment.  A user
+may use both Autocrypt-enabled mail apps and traditional plain ones
+and we'd like to avoid annoyances like unexpected unreadable mails
+while already supporting to turn on encryption explicitely.
+
+In other words, Level 0 does not support multi-device configurations which is
+rather intended and discussed as part of Level 1.  We want to keep Level 0
+minimal enough that it's easy for developers to adopt it and we can
+start to drive efforts from real-life experiences as soon as possible.
+
+Throughout this document, we refer to a mail apps or Mail User Agents (MUA)
+as though it was only capable of controlling a single e-mail account.  A
 MUA that is capable of connecting to multiple e-mail accounts should
 have a separate Autocrypt state for each e-mail account it has access
 to.