further readme work

README.txt

@@ -44,7 +44,7 b' Prerequisites'
 
 This extension requires keyring_ and `mercurial_extension_utils`_ to
 work. In many cases both will be installed automatically while you
-install `mercurial_keyring`_, but you may need to control the process.
+install ``mercurial_keyring``, but you may need to control the process.
 
 The keyring_ library can usually be installed by::
 
@@ -164,7 +164,7 b' password.'
 
 Mercurial allows also for password in ``.hg/hgrc`` (either given by
 ``«prefix».password``, or embedded in url). If such password is found,
-Mercurial Keyring disables itself so it is used.
+Mercurial Keyring disables itself.
 
 
 Account-level configuration
@@ -183,9 +183,9 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
-`https://hg.acme.com/repositories/my_beautiful_app`, username
-`johnnny` will be used, and the same password reused. Similarly
+and as long as you will be using alias ``acme`` 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.
 
 With such config repository-level ``.hg/hgrc`` need only contain
@@ -245,7 +245,7 b' Implementation details'
 ======================
 
 The extension is monkey-patching the mercurial ``passwordmgr`` class
-to replace the find_user_password method. Detailed order of operations
+to replace the ``find_user_password`` method. Detailed order of operations
 is described in the comments inside `the code`_.
 
 History