From 62473382b22c0129f0a5a11e324fa98f74863f70 Mon Sep 17 00:00:00 2001
From: Henrik Blidh <henrik.blidh@nedomkull.com>
Date: Wed, 10 Feb 2021 11:13:32 +0100
Subject: [PATCH] Update README.rst

---
 README.rst | 8 ++++----
 1 file changed, 4 insertions(+), 4 deletions(-)

diff --git a/README.rst b/README.rst
index f7fbd1d..0d5a725 100644
--- a/README.rst
+++ b/README.rst
@@ -56,7 +56,7 @@ See the `cryptography package's documentation for details <https://cryptography.
 Usage
 -----
 
-`bankid.jsonclient.BankIDJSONClient` is the client to be used to
+``BankIDJSONClient`` is the client to be used to
 communicate with the BankID service. It uses the JSON API released in February 2018.
 
 JSON client
@@ -72,7 +72,7 @@ Connection to production server is the default in the client. If test
 server is desired, send in the ``test_server=True`` keyword in the init
 of the client.
 
-WHen using the JSON client, all authentication and signing calls requires
+When using the JSON client, authentication and signing calls requires
 the end user's ip address to be included in all calls. An authentication order
 is initiated as such:
 
@@ -97,8 +97,8 @@ and a sign order is initiated in a similar fashion:
         'orderRef': 'a9b791c3-459f-492b-bf61-23027876140b'
     }
 
-Since the `BankIDJSONClient` is using the BankID ``v5`` JSON API, the `personal_number` can now be omitted when calling
-`authenticate` and `sign`. See `BankID Relying Party Guidelines <https://www.bankid.com/utvecklare/rp-info>`_
+Since the ``BankIDJSONClient`` is using the BankID ``v5`` JSON API, the ``personal_number`` can now be omitted when calling
+``authenticate`` and ``sign``. See `BankID Relying Party Guidelines <https://www.bankid.com/utvecklare/rp-info>`_
 for more information about this.
 
 The status of an order can then be studied by polling