docs: fix typo in API access rules and improve layout (#599)

Signed-off-by: Tom Fenech <[email protected]>

docs/docs/api-access-rules.md

@@ -97,7 +97,9 @@ Access Rules have four principal keys:
     matching strategy (glob or regexp) is defined in the global configuration
     file as `access_rules.matching_strategy`. This matcher ignores query
     parameters. Regular expressions (or glob patterns) are encapsulated in
-    brackets `<` and `>`. Regular expressions examples:
+    brackets `<` and `>`.
+
+    Regular expressions examples:
     - `https://mydomain.com/` matches `https://mydomain.com/` and does not match
       `https://mydomain.com/foo` or `https://mydomain.com`.
     - `<https|http>://mydomain.com/<.*>` matches:`https://mydomain.com/` or
@@ -108,7 +110,8 @@ Access Rules have four principal keys:
     - `http://mydomain.com/<(?!protected).*>` matches
       `http://mydomain.com/resource` and does not match
       `http://mydomain.com/protected`
-      [Glop](http://tldp.org/LDP/GNU-Linux-Tools-Summary/html/x11655.htm)
+
+    [Glob](http://tldp.org/LDP/GNU-Linux-Tools-Summary/html/x11655.htm)
       patterns examples:
     - `https://mydomain.com/<m?n>` matches `https://mydomain.com/man` and does
       not match `http://mydomain.com/foo`.

docs/versioned_docs/version-v0.37/api-access-rules.md

@@ -88,7 +88,9 @@ Access Rules have four principal keys:
     matching strategy (glob or regexp) is defined in the global configuration
     file as `access_rules.matching_strategy`. This matcher ignores query
     parameters. Regular expressions (or glob patterns) are encapsulated in
-    brackets `<` and `>`. Regular expressions examples:
+    brackets `<` and `>`.
+
+    Regular expressions examples:
     - `https://mydomain.com/` matches `https://mydomain.com/` and does not match
       `https://mydomain.com/foo` or `https://mydomain.com`.
     - `<https|http>://mydomain.com/<.*>` matches:`https://mydomain.com/` or
@@ -99,7 +101,8 @@ Access Rules have four principal keys:
     - `http://mydomain.com/<(?!protected).*>` matches
       `http://mydomain.com/resource` and does not match
       `http://mydomain.com/protected`
-      [Glop](http://tldp.org/LDP/GNU-Linux-Tools-Summary/html/x11655.htm)
+
+    [Glob](http://tldp.org/LDP/GNU-Linux-Tools-Summary/html/x11655.htm)
       patterns examples:
     - `https://mydomain.com/<m?n>` matches `https://mydomain.com/man` and does
       not match `http://mydomain.com/foo`.

docs/versioned_docs/version-v0.38/api-access-rules.md

@@ -88,7 +88,9 @@ Access Rules have four principal keys:
     matching strategy (glob or regexp) is defined in the global configuration
     file as `access_rules.matching_strategy`. This matcher ignores query
     parameters. Regular expressions (or glob patterns) are encapsulated in
-    brackets `<` and `>`. Regular expressions examples:
+    brackets `<` and `>`.
+
+    Regular expressions examples:
     - `https://mydomain.com/` matches `https://mydomain.com/` and does not match
       `https://mydomain.com/foo` or `https://mydomain.com`.
     - `<https|http>://mydomain.com/<.*>` matches:`https://mydomain.com/` or
@@ -99,7 +101,8 @@ Access Rules have four principal keys:
     - `http://mydomain.com/<(?!protected).*>` matches
       `http://mydomain.com/resource` and does not match
       `http://mydomain.com/protected`
-      [Glop](http://tldp.org/LDP/GNU-Linux-Tools-Summary/html/x11655.htm)
+
+    [Glob](http://tldp.org/LDP/GNU-Linux-Tools-Summary/html/x11655.htm)
       patterns examples:
     - `https://mydomain.com/<m?n>` matches `https://mydomain.com/man` and does
       not match `http://mydomain.com/foo`.