docs: RST documentation improvements and typo fixes (#65)

* docs: correct wording in JWT documentation for clarity

* docs: correct algorithm reference from HS386 to HS384 in JWT documentation

* docs: fix typo in UnsupportedAlgorithmError section

* docs: fix formatting in JWE documentation for class reference

* docs: correct text for generating an RSA key in JWK documentation

* docs: correct wording for clarity in JWK thumbprint method descriptions

* docs: format tenant placeholder in Azure configuration examples for clarity

Author: feteu

docs/guide/errors.rst

@@ -33,7 +33,7 @@ UnsupportedAlgorithmError
 .. versionadded:: 1.1.0
 
 By default, **ONLY recommended** :ref:`jwa` are allowed. With non recommended
-algorithms, you may encounter the ``UnsupportedAlgorithmError``` error.
+algorithms, you may encounter the ``UnsupportedAlgorithmError`` error.
 
 .. code-block:: python
 

docs/guide/jwe.rst

@@ -208,7 +208,7 @@ The syntax of a JWE using the flattened JWE JSON Serialization is as follows:
 
 It is flattened, it moves all the members out of the ``recipients`` field. To
 ``encrypt_json`` into a flattened serialization, you can construct a
-:class`jwe.FlattenedJSONEncryption` instead:
+:class:`jwe.FlattenedJSONEncryption` instead:
 
 .. code-block:: python
 

docs/guide/jwk.rst

@@ -70,7 +70,7 @@ It represents RSA keys.
 Generate an "RSA" key
 ~~~~~~~~~~~~~~~~~~~~~
 
-You can generate an "EC" key with a given key size (in bit):
+You can generate an "RSA" key with a given key size (in bit):
 
 .. code-block:: python
 
@@ -297,7 +297,7 @@ Key methods
 ``thumbprint``
 ~~~~~~~~~~~~~~
 
-Call this method will generate the thumbprint of the JWK, per RFC7638.
+Calling this method will generate the thumbprint of the JWK, per RFC7638.
 
 .. code-block:: python
 
@@ -323,7 +323,7 @@ You can also use the ``jwk.thumbprint`` method:
 
 .. versionadded:: 1.2.0
 
-Call this method will generate the JWK thumbprint URI, per RFC9278.
+Calling this method will generate the JWK thumbprint URI, per RFC9278.
 
 .. code-block:: python
 

docs/guide/jwt.rst

@@ -246,7 +246,7 @@ You can also pass a JWK Set to the ``key`` parameter of :meth:`encode` and
     jwt.encode(header, claims, key_set)
 
 The methods will find the correct key according to the ``kid`` you specified.
-If there is no ``kid`` in header, it will pick on randomly and add the ``kid``
+If there is no ``kid`` in header, it will pick one randomly and add the ``kid``
 of the key into header.
 
 A client would usually get the public key set from a public URL, normally the
@@ -362,7 +362,7 @@ You can find out the recommended algorithms at:
 - :ref:`JSON Web Signature Algorithms <jws_algorithms>`
 - :ref:`JSON Web Encryption Algorithms <jwe_algorithms>`
 
-For instance, ``HS386`` is not a recommended algorithm, and you want to use
+For instance, ``HS384`` is not a recommended algorithm, and you want to use
 this algorithm:
 
 .. code-block:: python

docs/recipes/azure.rst

@@ -68,7 +68,7 @@ the following format:
 
     https://login.microsoftonline.com/{tenant}/v2.0/.well-known/openid-configuration
 
-In the example provided, replace {tenant} with your specific Azure tenant ID or
+In the example provided, replace ``{tenant}`` with your specific Azure tenant ID or
 the tenant's globally unique identifier (GUID). The resulting URL will lead you
 to the OpenID configuration details. Then, the OpenID configuration endpoint for
 the above example could be:
@@ -88,7 +88,7 @@ can typically be found within the configuration as follows:
 
     https://login.microsoftonline.com/{tenant}/discovery/v2.0/keys
 
-Once again, remember to replace {tenant} with your Azure tenant ID or the appropriate identifier.
+Once again, remember to replace ``{tenant}`` with your Azure tenant ID or the appropriate identifier.
 In the above example, the ``jwks_uri`` could be:
 
 .. code-block:: none