Fix isues generating html docs

Author: MarcialRosales

docs/oauth2-examples-okta.md

@@ -70,7 +70,7 @@ to groups and users.
 
 :::
 
-Finally, click on **Save** and write down the following values.
+Finally, click on **Save** and write down the following values:
 
 :::tip
 Take note of this value, as you will need them later to configure RabbitMQ:  
@@ -198,13 +198,14 @@ Edit `rabbitmq.conf` and proceed as follows:
 1. Replace `{okta_client_app_ID}` with your **okta_client_app_ID**
 2. Replace `{okta-issuer}` with your **okta-Issuer**
 3. Ensure **okta-Metadata-URI** matches this value `{okta-issuer}/.well-known/oauth-authorization-server`
-4. Else remove the {okta-issuer} from the {okta-Metadata-URI} and use result to update
-`auth_oauth2.discovery_endpoint_path`
+or `{okta-issuer}/.well-known/openid-configuration`
+4. Else you need to determine the path that follows the uri in `{okta-issuer}` and update
+`auth_oauth2.discovery_endpoint_path` accordingly. For instance, if **okta-Metadata-URI** is `{okta-issuer}/some-other-endpoint`, you update `auth_oauth2.discovery_endpoint_path` with the value `some-other-endpoint`.
 
 
 ### About OpenId Discovery Endpoint
 
-RabbitMQ uses the standard OpenId discovery endpoint path `./well-known/openid-configuration`. Okta supports this path in addition to `.well-known/oauth-authorization-server`. The only difference observed at the time of writing this guide is that the latter returns more values in the json attribute `claims_supported`.
+RabbitMQ uses the standard OpenId discovery endpoint path `.well-known/openid-configuration`. Okta supports this path in addition to `.well-known/oauth-authorization-server`. The only difference observed at the time of writing this guide is that the latter returns more values in the json attribute `claims_supported`.
 
 The RabbitMQ's template configuration provided in this example has this line commented out meaning that
 RabbitMQ will use the standard path. If you find any problems, try uncommenting this line.
@@ -223,8 +224,7 @@ make start-rabbitmq
 
 ## Verify RabbitMQ Management UI Access
 
-Go to RabbitMQ Management UI `https://localhost:15671`. Depending on your browser, ignore the security warnings (raised by the fact that a [self-signed certificate](./ssl#peer-verification) is used)
-to proceed.
+Go to RabbitMQ Management UI `https://localhost:15671`. Depending on your browser, ignore the security warnings (raised by the fact that a [self-signed certificate](./ssl#peer-verification) is used) to proceed.
 
 Once on the RabbitMQ Management UI page, click on the **Click here to log in** button,
 authenticate with your **okta user**.