fixed warnings

applications/operators/olm-adding-operators-to-cluster.adoc

@@ -40,5 +40,5 @@ version of an Operator is available, the OLM creates an update request. As a
 cluster administrator, you must then manually approve that update request to
 have the Operator updated to the new version.
 
-include::modules/olm-installing-from-operatorhub-using-web-console.adoc[leveloffset=+2]
-include::modules/olm-installing-from-operatorhub-using-cli.adoc[leveloffset=+2]
+include::modules/olm-installing-from-operatorhub-using-web-console.adoc[leveloffset=+1]
+include::modules/olm-installing-from-operatorhub-using-cli.adoc[leveloffset=+1]

authentication/configuring-internal-oauth.adoc

@@ -12,7 +12,7 @@ Configuring these options will need to change because they're set in the master
 config file now.
 ====
 
-include::modules/oauth-server-overview.adoc[leveloffset=+2]
+include::modules/oauth-server-overview.adoc[leveloffset=+1]
 
 include::modules/oauth-internal-tokens.adoc[leveloffset=+1]
 

modules/identity-provider-oidc-CRD.adoc

@@ -29,7 +29,7 @@ spec:
     openID:
       clientID: ... <5>
       clientSecret: ... <6>
-      claims:
+      claims: <7>
         preferredUsername:
         - preferred_username
         name:
@@ -77,7 +77,7 @@ spec:
     type: OpenID
     openID:
       clientID: ...
-      clientSecret: ... 
+      clientSecret: ...
       ca: /path/to/ca.file <1>
       extraScopes: <2>
       - email

modules/nodes-nodes-problem-detector-customizing.adoc

@@ -26,7 +26,7 @@ kind: ConfigMap
 metadata:
   name: node-problem-detector
 data:
-    kernel-monitor.json: |  <8>
+    kernel-monitor.json: |  <1>
     {
         "plugin": "journald", <2>
         "pluginConfig": {
@@ -43,7 +43,7 @@ data:
                         "message": "kernel has no deadlock"  <7>
                 }
         ],
-        "rules": [
+        "rules": [ <8>
                 {
                         "type": "temporary",
                         "reason": "OOMKilling",
@@ -142,4 +142,3 @@ spec:
 <1> Sends the output to standard output (stdout).
 <2> Path to the error log.
 <3> Comma-separated path to the plug-in configuration files.
-

modules/nodes-scheduler-node-affinity-example.adoc

@@ -8,7 +8,7 @@
 The following examples demonstrate node affinity.
 
 [[admin-guide-sched-affinity-examples1]]
-=== Node Affinity with Matching Labels
+== Node Affinity with Matching Labels
 
 The following example demonstrates node affinity for a node and pod with matching labels:
 
@@ -50,7 +50,7 @@ pod-s1   1/1       Running      0          4m       IP1     node1
 ----
 
 [[admin-guide-sched-affinity-examples2]]
-=== Node Affinity with No Matching Labels
+== Node Affinity with No Matching Labels
 
 The following example demonstrates node affinity for a node and pod without matching labels:
 
@@ -93,4 +93,3 @@ Events:
  --------- -------- ----- ----              -------------  --------            ------
  1m        33s      8     default-scheduler Warning        FailedScheduling    No nodes are available that match all of the following predicates:: MatchNodeSelector (1).
 ----
-

modules/quotas-creating-object-count-quotas.adoc

@@ -3,7 +3,7 @@
 // * applications/quotas/quotas-setting-per-project.adoc
 
 [id='quota-creating-object-count-quotas-{context}']
-== Creating object count quotas
+= Creating object count quotas
 
 You can create an object count quota for all {product-title} standard namespaced
 resource types, such as `BuildConfig`, and `DeploymentConfig`. An object quota

modules/service-accounts-as-oauth-clients.adoc

@@ -31,7 +31,7 @@ account to `true`.
 * `redirect_uri` must match an annotation on the service account.
 
 [[redirect-uris-for-service-accounts]]
-=== Redirect URIs for Service Accounts as OAuth Clients
+== Redirect URIs for Service Accounts as OAuth Clients
 
 Annotation keys must have the prefix
 `serviceaccounts.openshift.io/oauth-redirecturi.` or