Merge pull request datarevenue-berlin#90 from spazm/feature/rst-clean-up

Fix warnings in documentation rst files.
k5tuck · Oct 18, 2021 · 2f340a0 · 2f340a0
2 parents a90ebab + eaa011d
commit 2f340a0
Show file tree

Hide file tree

Showing 2 changed files with 5 additions and 5 deletions.
diff --git a/docs/components/ory/technical.rst b/docs/components/ory/technical.rst
@@ -19,8 +19,8 @@ From the ORY Ecosystem we use two services:
     - ORY Oathkeeper
     - ORY Kratos
 
-* Although they were designed to work together, all ORY services are completely independent
-from each other *
+**Although they were designed to work together, all ORY services are completely independent
+from each other**
 
 ORY Oathkeeper
 --------------

diff --git a/docs/components/ory/usage.rst b/docs/components/ory/usage.rst
@@ -11,7 +11,7 @@ In order to configure access for an specific service, we need to specify Access
 All the Access Rules are defined in the file `access-rule-oathkeeper.yaml`
 (for convenience and maintainability)
 
-** Allow all access **::
+**Allow all access**::
 
     - id: oathkeeper-access-rule
       match:
@@ -30,7 +30,7 @@ All the Access Rules are defined in the file `access-rule-oathkeeper.yaml`
 This configuration will register all the incoming requests as a `guest` user, thus, not
 performing any credentials validation.
 
-** Authenticate User **::
+**Authenticate User**::
 
     - id: protected-service
       match:
@@ -53,7 +53,7 @@ Note that the Oathkeeper doesn't care about the authentication method that was u
 ORY Kratos, as long as it provides a valid Session Cookie.
 
 Identities and Providers
-~~~~~~~~~~~~~~~~~~~~
+~~~~~~~~~~~~~~~~~~~~~~~~
 
 Kratos allows setting up different Identities in which each one can have multiple authentication providers.