fix validation errors and warnings (#2766)

* fix validation errors and warnings

Signed-off-by: Mykhailo Kuznietsov <mkuznets@redhat.com>

* fixup! fix validation errors and warnings

---------

Signed-off-by: Mykhailo Kuznietsov <mkuznets@redhat.com>

Author: mkuznyetsov

modules/administration-guide/pages/configuring-network-policies.adoc

@@ -38,12 +38,11 @@ spec:
     policyTypes:
     - Ingress
 ----
-====
-+
 <1> The {prod-short} namespace.
 The default is `{prod-namespace}`.
 <2> The empty `podSelector` selects all Pods in the {orch-namespace}.
-
+====
++
 * OPTIONAL: In case you applied link:https://docs.openshift.com/container-platform/{ocp4-ver}/networking/network_policy/multitenant-network-policy.html[Configuring multitenant isolation with network policy], you also must apply `allow-from-openshift-apiserver` and `allow-from-workspaces-namespaces` NetworkPolicies to `{prod-namespace}`. 
 The `allow-from-openshift-apiserver` NetworkPolicy allows incoming traffic from `openshift-apiserver` namespace to the `devworkspace-webhook-server` enabling webhooks.
 The `allow-from-workspaces-namespaces` NetworkPolicy allows incoming traffic from each user project to `che-gateway` pod.
@@ -70,11 +69,10 @@ spec:
   policyTypes:
     - Ingress
 ----
-====
-+
 <1> The {prod-short} namespace.
 The default is `{prod-namespace}`.
 <2> The `podSelector` only selects devworkspace-webhook-server pods
+====
 +
 .`allow-from-workspaces-namespaces.yaml`
 ====
@@ -98,11 +96,11 @@ spec:
   policyTypes:
     - Ingress
 ----
-====
-+
 <1> The {prod-short} namespace.
 The default is `{prod-namespace}`.
 <2> The `podSelector` only selects che-gateway pods
+====
++
 
 .Additional resources
 * xref:configuring-namespace-provisioning.adoc[]

modules/administration-guide/pages/creating-a-telemetry-plugin.adoc

@@ -33,7 +33,6 @@ This document describes the steps required to extend the {prod-short} telemetry
 
 A finished example of the telemetry backend is available link:https://github.com/che-incubator/devworkspace-telemetry-example-plugin[here].
 
-[discrete]
 == Creating a server that receives events
 
 For demonstration purposes, this example shows how to create a server that receives events from our telemetry plugin and writes them to standard output.

modules/administration-guide/pages/installing-che-in-the-cloud.adoc

@@ -3,7 +3,7 @@
 :keywords: overview, running-che-in-the-cloud, installing-che-in-the-cloud
 :navtitle: Installing {prod-short} in the cloud
 
-[id="installing-{prod-id-short}-locally"]
+[id="installing-{prod-id-short}-in-the-cloud"]
 = Installing {prod-short} in the cloud
 
 Deploy and run {prod} in the cloud.
@@ -16,7 +16,7 @@ Deploy and run {prod} in the cloud.
 
 == Deploying {prod-short} in the cloud
 
-Follow the instructions below to start the {prod-short} Server in the cloud using the `{prod-cli}` tool.
+Follow the instructions below to start the {prod-short} Server in the cloud by using the `{prod-cli}` tool.
 
 * xref:installing-che-on-openshift-using-cli.adoc[]
 * xref:installing-che-on-openshift-using-the-web-console.adoc[]

modules/end-user-guide/pages/starting-a-workspace-from-a-raw-devfile-url.adoc

@@ -46,8 +46,8 @@ You can pass your personal access token to the URL to access a devfile from *pri
 ----
 pass:c,a,q[{prod-url}]#__https://__<token>__@__<host>__/__<path_to_devfile> <1>
 ----
-+
 <1> Your personal access token that you generated on the Git provider's website.
+
 +
 This works for GitHub, GitLab, Bitbucket, Microsoft Azure, and other providers that support Personal Access Token.
 +