[Telepathy-commits] [telepathy-spec/master] AccountManager: improve wording of "don't be service-activatable"

Simon McVittie simon.mcvittie at collabora.co.uk
Fri Aug 29 09:52:10 PDT 2008


---
 spec/Account_Manager.xml |   12 ++++++------
 1 files changed, 6 insertions(+), 6 deletions(-)

diff --git a/spec/Account_Manager.xml b/spec/Account_Manager.xml
index 6c5c12b..608c287 100644
--- a/spec/Account_Manager.xml
+++ b/spec/Account_Manager.xml
@@ -31,12 +31,12 @@ Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301, USA.
         AccountManager interface.</p>
 
       <p>Until a mechanism exists for making a reasonable automatic choice
-        of AccountManager implementation, it is RECOMMENDED that
-        implementations do not register as an activatable service for the
-        AccountManager's well-known bus name. Instead, it is intended that
-        some component of the user's session will select and activate a
-        particular implementation, and that other Telepathy-enabled programs
-        can detect whether Telepathy is in use by checking whether the
+        of AccountManager implementation, implementations SHOULD NOT
+        register as an activatable service for the AccountManager's
+        well-known bus name. Instead, it is RECOMMENDED that some component
+        of the user's session will select and activate a particular
+        implementation, and that other Telepathy-enabled programs can
+        detect whether Telepathy is in use by checking whether the
         AccountManager's well-known name is in use at runtime.</p>
     </tp:docstring>
     <tp:added version="0.17.2"/>
-- 
1.5.6.3




More information about the Telepathy-commits mailing list