Fixup doc (#3088)

Signed-off-by: Anatolii Bazko <abazko@redhat.com>

Author: tolusha

modules/administration-guide/nav.adoc

@@ -42,7 +42,7 @@
 *** xref:configuring-workspace-target-namespace.adoc[]
 *** xref:provisioning-namespaces-in-advance.adoc[]
 *** xref:configuring-a-user-namespace.adoc[]
-*** xref:configuring-direct-namespace-creation-on-openshift.adoc[]
+*** xref:configuring-kubernetes-namespace-creation-on-openshift.adoc[]
 ** xref:configuring-server-components.adoc[]
 *** xref:mounting-a-secret-as-a-file-or-an-environment-variable-into-a-container.adoc[]
 *** xref:advanced-configuration-options-for-the-che-server-component.adoc[]

modules/administration-guide/pages/configuring-a-user-namespace.adoc

@@ -54,7 +54,7 @@ after being deleted from {prod-namespace} namespace:
 che.eclipse.org/sync-retain-on-delete: "true"
 ----
 +
-Add the following annotation to prevent workspace restarts when the ConfigMap is mounted:
+Add the following annotation to prevent workspace restarts when the ConfigMap is created:
 +
 [source,yaml,subs="+attributes,+quotes"]
 ----
@@ -116,7 +116,7 @@ after being deleted from {prod-namespace} namespace:
 che.eclipse.org/sync-retain-on-delete: "true"
 ----
 +
-Add the following annotation to prevent workspace restarts when the Secret is mounted:
+Add the following annotation to prevent workspace restarts when the Secret is created:
 +
 [source,yaml,subs="+attributes,+quotes"]
 ----
@@ -156,7 +156,7 @@ Add the annotation below if you want the `PersistentVolumeClaim` to be deleted i
 che.eclipse.org/sync-retain-on-delete: "false"
 ----
 +
-Add the following annotation to prevent workspace restarts when the `PersistentVolumeClaim` is mounted:
+Add the following annotation to prevent workspace restarts when the `PersistentVolumeClaim` is created:
 +
 [source,yaml,subs="+attributes,+quotes"]
 ----

…ect-namespace-creation-on-openshift.adoc …tes-namespace-creation-on-openshift.adocmodules/administration-guide/pages/configuring-direct-namespace-creation-on-openshift.adoc renamed to modules/administration-guide/pages/configuring-kubernetes-namespace-creation-on-openshift.adoc modules/administration-guide/pages/configuring-direct-namespace-creation-on-openshift.adoc renamed to modules/administration-guide/pages/configuring-kubernetes-namespace-creation-on-openshift.adoc

@@ -4,8 +4,8 @@
 :navtitle: Configuring direct namespace creation on OpenShift
 :page-aliases:
 
-[id="configuring-direct-namespace-creation-on-openshift"]
-= Configuring direct namespace creation on OpenShift
+[id="configuring-kubernetes-namespace-creation-on-openshift"]
+= Configuring {kubernetes} namespace creation on OpenShift
 
 By default, on {ocp} clusters, {prod-short} uses the ProjectRequest API to create projects. This triggers cluster-specific link:https://docs.openshift.com/container-platform/latest/applications/projects/configuring-project-creation.html[Project Templates], which can apply additional resources or policies.
 
@@ -17,7 +17,7 @@ On {ocp}, you can bypass Project Templates and create standard {kubernetes} Name
 
 .Procedure
 
-. Set the `createNamespaceDirectly` field to `true`:
+. Set the `createKubernetesNamespaces` field to `true`:
 +
 [source,shell,subs="+quotes,+attributes,+macros"]
 ----
@@ -28,7 +28,7 @@ On {ocp}, you can bypass Project Templates and create standard {kubernetes} Name
     "spec": {
       "devEnvironments": {
         "defaultNamespace": {
-          "createNamespaceDirectly": true
+          "createKubernetesNamespaces": true
         }
       }
     }