attempt to fix rst rendering on bitbucket

README.rst

@@ -95,12 +95,12 @@ server.
 
 This program:
 
-  * can be used directly with ``AuthorizedKeysCommand`` (the username
-    parameter is ignored).
+* can be used directly with ``AuthorizedKeysCommand`` (the username parameter
+  is ignored).
 
-  * does not require a patched OpenSSH server.
+* does not require a patched OpenSSH server.
 
-  * does not scale well to a large number of user keys.
+* does not scale well to a large number of user keys.
 
 Using ``django-sshkey-lookup-by-username``
 ------------------------------------------
@@ -112,11 +112,11 @@ user.
 
 This program:
 
-  * can be used directly with ``AuthorizedKeysCommand``.
+* can be used directly with ``AuthorizedKeysCommand``.
 
-  * does not require a patched OpenSSH server.
+* does not require a patched OpenSSH server.
 
-  * is ideal if each Django user corresponds to a system user account.
+* is ideal if each Django user corresponds to a system user account.
 
 Using ``django-sshkey-lookup-by-fingerprint``
 ---------------------------------------------
@@ -126,30 +126,30 @@ Using ``django-sshkey-lookup-by-fingerprint``
 This program prints all SSH public keys that match the given fingerprint.  The
 fingerprint is determined by the first of the following that is found:
 
-  1. The ``SSH_KEY_FINGERPRINT`` environment variable, which should contain
-     the MD5 fingerprint of the key (this is the second field generated by
-     ``ssh-keygen -l``).
+1. The ``SSH_KEY_FINGERPRINT`` environment variable, which should contain the
+   MD5 fingerprint of the key (this is the second field generated by
+   ``ssh-keygen -l``).
 
-  2. The ``SSH_KEY`` environment variable, which should contain the key in
-     standard openssh format (the same format as ``~/.ssh/id_rsa.pub``), is
-     sent to ``ssh-keygen -l`` to determine the fingerprint.
+2. The ``SSH_KEY`` environment variable, which should contain the key in
+   standard openssh format (the same format as ``~/.ssh/id_rsa.pub``), is sent
+   to ``ssh-keygen -l`` to determine the fingerprint.
 
-  3. The key in standard openssh format is read from standard input and is
-     sent to ``ssh-keygen -l`` to determine the fingerprint.
+3. The key in standard openssh format is read from standard input and is sent
+   to ``ssh-keygen -l`` to determine the fingerprint.
 
 This program:
 
-  * can be used directly with ``AuthorizedKeysCommand`` (the username
-    parameter is ignored).
+* can be used directly with ``AuthorizedKeysCommand`` (the username parameter
+  is ignored).
 
-  * requires a patched OpenSSH server; compatible patches can be found at one
-    of the following locations:
+* requires a patched OpenSSH server; compatible patches can be found at one of
+  the following locations:
 
-      - openssh-akcenv_ (this is the preferred patch)
-      - openssh-stdinkey_
+  - openssh-akcenv_ (this is the preferred patch)
+  - openssh-stdinkey_
 
-  * is ideal if you want all Django users to access SSH via a shared system
-    user account and be identified by their SSH public key.
+* is ideal if you want all Django users to access SSH via a shared system user
+  account and be identified by their SSH public key.
 
 Using ``django-sshkey-lookup``
 ------------------------------