diff --git a/install.rst b/install.rst
index ea6ab76f1..a2805432e 100644
--- a/install.rst
+++ b/install.rst
@@ -146,28 +146,28 @@ server-proxy-uri
 
   Overrides the base URL used within the OpenAPI self-documentation hosted at the API root path. Use a complete URI syntax :code:`scheme:[//[user:password@]host[:port]][/]path[?query][#fragment]`. Ex. :code:`https://postgrest.com`
 
-.. code:: json
+  .. code:: json
 
-  {
-    "swagger": "2.0",
-    "info": {
-      "version": "0.4.3.0",
-      "title": "PostgREST API",
-      "description": "This is a dynamic API generated by PostgREST"
-    },
-    "host": "postgrest.com:443",
-    "basePath": "/",
-    "schemes": [
-      "https"
-    ]
-  }
+    {
+      "swagger": "2.0",
+      "info": {
+        "version": "0.4.3.0",
+        "title": "PostgREST API",
+        "description": "This is a dynamic API generated by PostgREST"
+      },
+      "host": "postgrest.com:443",
+      "basePath": "/",
+      "schemes": [
+        "https"
+      ]
+    }
 
 .. _jwt-secret:
 
 jwt-secret
 ----------
 
-  The secret or `JSON Web Key (JWK) <https://tools.ietf.org/html/rfc7517>`_ used to decode JWT tokens clients provide for authentication. For security the key must be at least thirty-two characters long. If this parameter is not specified then PostgREST refuses authentication requests. Choosing a value for this parameter beginning with the at sign such as :code:`@filename` loads the secret out of an external file. This is useful for automating deployments. Note that any binary secrets must be base64 encoded. Both symmetric and asymmetric cryptography are supported. For more info see :ref:`asym_keys`.
+  The secret or `JSON Web Key (JWK) <https://tools.ietf.org/html/rfc7517>`_ used to decode JWT tokens clients provide for authentication. For security the key must be **at least 32 characters long**. If this parameter is not specified then PostgREST refuses authentication requests. Choosing a value for this parameter beginning with the at sign such as :code:`@filename` loads the secret out of an external file. This is useful for automating deployments. Note that any binary secrets must be base64 encoded. Both symmetric and asymmetric cryptography are supported. For more info see :ref:`asym_keys`.
 
 .. _jwt-aud:
 
@@ -211,15 +211,15 @@ role-claim-key
 
   A JSPath DSL that specifies the location of the :code:`role` key in the JWT claims. This can be used to consume a JWT provided by a third party service like Auth0, Okta or Keycloak. Usage examples:
 
-.. code:: bash
+  .. code:: bash
 
-  # {"postgrest":{"roles": ["other", "author"]}}
-  # the DSL accepts characters that are alphanumerical or one of "_$@" as keys
-  role-claim-key = ".postgrest.roles[1]"
+    # {"postgrest":{"roles": ["other", "author"]}}
+    # the DSL accepts characters that are alphanumerical or one of "_$@" as keys
+    role-claim-key = ".postgrest.roles[1]"
 
-  # {"https://www.example.com/role": { "key": "author }}
-  # non-alphanumerical characters can go inside quotes(escaped in the config value)
-  role-claim-key = ".\"https://www.example.com/role\".key"
+    # {"https://www.example.com/role": { "key": "author }}
+    # non-alphanumerical characters can go inside quotes(escaped in the config value)
+    role-claim-key = ".\"https://www.example.com/role\".key"
 
 Running the Server
 ------------------