README updates (a few language fixes, added note about GUI tools)

README.txt

@@ -71,7 +71,7 b' which can be installed by::'
 
     pip install --user mercurial_extension_utils
 
-but in some cases (Windows…) require more care. See
+but in some cases (Windows…) requires more care. See
 `mercurial_extension_utils`_ documentation.
     
 
@@ -92,14 +92,13 b' installation) and then enable it in ``~/'
     [extensions]
     mercurial_keyring = 
 
-To install as source clone, install keyring_ according to instructions above, then
-clone::
+To install using source clone, install keyring_ according to the
+instructions above, then clone::
     
     hg clone https://bitbucket.org/Mekk/mercurial_keyring/
     hg clone https://bitbucket.org/Mekk/mercurial-extension_utils/
 
-and configure Mercurial by telling it full path to the extension
-(in )::
+and configure Mercurial using  full path to the extension module::
 
     [extensions]
     mercurial_keyring = /path/to/mercurial_keyring/mercurial_keyring.py
@@ -110,15 +109,17 b' and configure Mercurial by telling it fu'
 Password backend configuration
 =======================================================
 
-The library should usually pick the most appropriate password backend
-without configuration. Still, if necessary, it can be configured using
-``keyringrc.cfg`` file.  Refer to keyring_ docs for more details.
+The most appropriate password backend should usually be picked without
+configuration (considering installed libraries, operating system,
+active desktop session). Still, if necessary, it can be configured
+using ``keyringrc.cfg`` file.  Refer to keyring_ docs for more
+details.
 
 .. note::
 
    With current (as I write) keyring (5.6), this file is (on Linux)
    located at ``~/.local/share/python_keyring/keyringrc.cfg`` and
-   it's example content look like::
+   it's example content looks like::
 
         [backend]
         default-keyring=keyring.backends.Gnome.Keyring
@@ -191,7 +192,7 b' directory). For example, write there::'
     mydep.prefix = https://dev.acmeorg.com
     mydep.username = drmartin
 
-and as long as you will be using alias ``acme`` for repositories like
+and as long as you use  ``acme`` alias for repositories like
 ``https://hg.acme.com/repositories/my_beautiful_app``, username
 ``johnny`` will be used, and the same password reused. Similarly
 any ``hg push bitbucket`` will share the same password.
@@ -205,7 +206,8 b' Additional advantage of this method is t'
 
 .. note::
 
-   Mercurial Keyring works well with `Path Pattern`_. On my setup I use::
+   Mercurial Keyring works well with `Path Pattern`_. On my setup I use
+   prefix as above, and::
 
        [path_pattern]
        bitbucket.local = ~/devel/{below}
@@ -286,6 +288,32 b' path. It can be used in two ways:'
 
     hg keyring_clear https://bitbucket.org/Mekk/mercurial_keyring
 
+Managing passwords using GUI tools
+------------------------------------------------------
+
+Many password backends provide GUI tools for password management,
+for example Gnome Keyring passwords can be managed using ``seahorse``,
+and KDE Wallet using ``kwalletmanager``. Those GUI tools can be used
+to review, edit, or delete saved passwords.
+
+Unfortunately, as I write, keyring_ library does not allow one to
+configure how/where exactly saved passwords are put in the hierarchy,
+and the place is not always intuitive. For example, in KDE Wallet, all
+passwords saved using ``mercurial_keyring`` show up in the folder
+named ``Python``.
+
+.. note::
+
+   This is slightly problematic in case ``mercurial_keyring`` is not
+   the only program using keyring_ library. Passwords saved by another
+   Python application or script (which also uses keyring_) will be put
+   into the same place, and it may be unclear which password belongs
+   to which program. To remedy this, ``mercurial_keyring`` applies
+   slightly unusual labels of the form
+   ``«username»@@«urlprefix»@Mercurial`` (for example my bitbucket
+   password is labelled ``Mekk@@https://bitbucket.org@Mercurial``).
+
+
 Implementation details
 =======================================================