Fix doc markup

doc/sources/admin/checkstate.rst

@@ -33,9 +33,9 @@ The plugin will respond to the HTTP request with:
 * HTTP code 500 if something went wrong
 * HTTP code 200 and the following JSON content if something went right
 
-```
-{"result":1,"version":"2.0.14"}
-```
+.. code:: json
+
+    {"result":1,"version":"2.0.14"}
 
 .. versionadded:: 2.0.14
    The *version* key is returned

doc/sources/admin/portalcustom.rst

@@ -137,11 +137,9 @@ To achieve this, you can create a rule in the Manager: select
    skin is applied.
 -  **Value**: the name of the skin to use.
 
-Example:
+Example::
 
-```
-$_url =~ m#^http://test1.example.com#
-```
+    $_url =~ m#^http://test1.example.com#
 
 Skin files
 ~~~~~~~~~~

doc/sources/admin/ssoaas.rst

@@ -47,9 +47,9 @@ Two different kinds of architecture are existing to do this:
     Some requests can be dropped by the central FastCGI/uWSGI server.
 
     Example below with an uWSGI server to prevent Load Balancer health check requests
-    being forwarded to the central DevOps Handler:
+    being forwarded to the central DevOps Handler ::
 
-    ```route-remote-addr = ^127\.0\.0\.25[34]$ break: 403 Forbidden for IP ${REMOTE_ADDR}```
+        route-remote-addr = ^127\.0\.0\.25[34]$ break: 403 Forbidden for IP ${REMOTE_ADDR}
 
 
 Example of a Central FastCGI architecture:

doc/sources/admin/upgrade_2_0_x.rst

@@ -186,17 +186,13 @@ LemonLDAP::NG version is returned by the CheckState plugin
 
 If you use the `/checkstate` URL to monitor LemonLDAP::NG, you may notice a slight change in the output format:
 
-*2.0.13* :
+*2.0.13* ::
 
-```
-{"result":1}
-```
+    {"result":1}
 
-*2.0.14* :
+*2.0.14* ::
 
-```
-{"result":1,"version":"2.0.14"}
-```
+    {"result":1,"version":"2.0.14"}
 
 Depending on your load balancer or monitoring configuration, this can cause false negatives.