[docs] Minor updates

Author: alorence

docs/index.rst

@@ -42,12 +42,12 @@ your project, follow other topics in the menu.
    quickstart.rst
    server.rst
    procedure_registration.rst
-   backends.rst
    authentication.rst
    error_handling.rst
+   backends.rst
    security.rst
-   faq.rst
    references.rst
+   faq.rst
    migration_guide.rst
 
 .. toctree::

docs/quickstart.rst

@@ -48,7 +48,7 @@ Create an ``RpcServer`` instance and register your first procedure
         return a + b
 
 Remote procedures are Python functions decorated with the server's ``register_procedure`` decorator.
-Both server and procedure registration can be customized. See ...
+Both server and procedure registration can be customized. See :ref:`Procedures registration`
 
 Serve the procedures
 --------------------
@@ -70,7 +70,7 @@ to this view in your project's ``urls.py``
 The server's view is already configured with CSRF exemption and POST-only restrictions.
 
 Async Support
-^^^^^^^^^^^^
+^^^^^^^^^^^^^
 
 For Django projects using ASGI and async views, you can use the async version of the view:
 
@@ -100,10 +100,10 @@ directly with your favourite HTTP client
 .. code-block:: bash
    :caption: JSON-RPC example
 
-    ~  $ curl -X POST localhost:8000/rpc -H "Content-Type: application/json" -d '{"id": 1, "method": "system.listMethods", "jsonrpc": "2.0"}'
+    ~$ curl -X POST localhost:8000/rpc -H "Content-Type: application/json" -d '{"id": 1, "method": "system.listMethods", "jsonrpc": "2.0"}'
     {"id": 1, "jsonrpc": "2.0", "result": ["add", "system.listMethods", "system.methodHelp", "system.methodSignature"]}
 
-    ~  $ curl -X POST localhost:8000/rpc -H "Content-Type: application/json" -d '{"id": 2, "method": "add", "params": [5, 9], "jsonrpc": "2.0"}'
+    ~$ curl -X POST localhost:8000/rpc -H "Content-Type: application/json" -d '{"id": 2, "method": "add", "params": [5, 9], "jsonrpc": "2.0"}'
     {"id": 2, "jsonrpc": "2.0", "result": 14}
 
 .. code-block:: python

docs/security.rst

@@ -30,7 +30,7 @@ All built-in XML-RPC backends are configured with protections against XXE/DoS:
 - etree backend (xml.etree.ElementTree)
   - Uses defusedxml.ElementTree for parsing and serialization.
   - Forbidden constructs (DTD, entities, external references) raise defusedxml exceptions, which are translated into
-    RPCInsecureRequest.
+  RPCInsecureRequest.
   - Malformed XML raises RPCParseError.
 
 - xmltodict backend
@@ -39,7 +39,7 @@ All built-in XML-RPC backends are configured with protections against XXE/DoS:
 
 - lxml backend
   - Uses a hardened lxml.etree.XMLParser with resolve_entities=False, no_network=True, dtd_validation=False,
-    load_dtd=False, huge_tree=False.
+  load_dtd=False, huge_tree=False.
   - XMLSyntaxError is mapped to RPCParseError.
 
 What you will see on insecure input

docs/server.rst

@@ -25,8 +25,8 @@ to the request's protocol (JSON-RPC or XML-RPC).
 Protocol restriction
 ^^^^^^^^^^^^^^^^^^^^
 
-Using the ``supported_protocol`` argument, you can make sure a given server will handle only JSON-RPC or XML-RPC requests.
-This can be used to set up protocol-specific servers.
+Using the ``supported_protocol`` argument, you can configure a given server to handle only JSON-RPC or XML-RPC
+requests. This can be used to set up protocol-specific servers.
 
 Default: ``supported_protocol = Protocol.ALL``
 
@@ -67,7 +67,9 @@ Default: ``register_system_procedures = True``
     # server won't register the system.* procedures
 
 .. warning::
-  Disabling the system procedure registration may prevent some clients (in particular, XML-RPC ones) to send request to your server, use at your own risks.
+
+  Disabling the system procedure registration may prevent some clients (in particular, XML-RPC ones) to
+  send request to your server, use at your own risk.
 
 Authentication
 ^^^^^^^^^^^^^^
@@ -206,4 +208,5 @@ You can create multiple server.
     ]
 
 .. warning::
+
   This section needs more detailed explanation & examples