Merge pull request #30972 from jboxman/context-underscore

Always precede {context} with underscore

Author: jboxman

modules/checking-project-status-using-the-CLI.adoc

@@ -2,7 +2,7 @@
 //
 // applications/projects/working-with-projects.adoc
 
-[id="checking-project-status-using-the-CLI{context}"]
+[id="checking-project-status-using-the-CLI_{context}"]
 = Checking project status using the CLI
 
 .Procedure

modules/deleting-a-project-using-the-CLI.adoc

@@ -2,7 +2,7 @@
 //
 // applications/projects/working-with-projects.adoc
 
-[id="deleting-a-project-using-the-CLI{context}"]
+[id="deleting-a-project-using-the-CLI_{context}"]
 = Deleting a project using the CLI
 
 When you delete a project, the server updates the project status to

modules/identity-provider-basic-authentication-troubleshooting.adoc

@@ -2,7 +2,7 @@
 //
 // * authentication/identity_providers/configuring-basic-authentication-identity-provider.adoc
 
-[id="identity-provider-basic-authentication-troubleshooting{context}"]
+[id="identity-provider-basic-authentication-troubleshooting_{context}"]
 = Basic authentication troubleshooting
 
 The most common issue relates to network connectivity to the backend server. For

modules/installation-about-restricted-network.adoc

@@ -50,7 +50,7 @@ Because of the complexity of the configuration for user-provisioned installation
 ====
 endif::osp,rhv[]
 
-[id="installation-restricted-network-limits{context}"]
+[id="installation-restricted-network-limits_{context}"]
 == Additional limits
 
 Clusters in restricted networks have the following additional limitations and restrictions:

modules/samples-operator-crd.adoc

@@ -3,7 +3,7 @@
 // * openshift_images/configuring_samples_operator.adoc
 
 
-[id="samples-operator-crd{context}"]
+[id="samples-operator-crd_{context}"]
 = Accessing the Cluster Samples Operator configuration
 
 You can configure the Cluster Samples Operator by editing the file with the provided

modules/service-accounts-default.adoc

@@ -8,7 +8,7 @@
 Your {product-title} cluster contains default service accounts for
 cluster management and generates more service accounts for each project.
 
-[id="default-cluster-service-accounts{context}"]
+[id="default-cluster-service-accounts_{context}"]
 == Default cluster service accounts
 
 Several infrastructure controllers run using service account credentials. The

modules/storage-ephemeral-storage-types.adoc

@@ -2,7 +2,7 @@
 //
 // storage/understanding-persistent-storage.adoc[leveloffset=+1]
 
-[id=storage-ephemeral-storage-types{context}]
+[id=storage-ephemeral-storage-types_{context}]
 = Types of ephemeral storage
 
 Ephemeral local storage is always made available in the primary

modules/virt-understanding-node-maintenance.adoc

@@ -3,7 +3,7 @@
 // * virt/node_maintenance/virt-node-maintenance.adoc
 // * virt/node_maintenance/virt-setting-node-maintenance.adoc
 
-[id="virt-understanding-node-maintenance{context}"]
+[id="virt-understanding-node-maintenance_{context}"]
 = Understanding node maintenance mode
 
 Placing a node into maintenance marks the node as unschedulable and drains all 

modules/web-console-disable.adoc

@@ -2,7 +2,7 @@
 //
 // * web_console/disabling-web-console.adoc
 
-[id="web-console-disable{context}"]
+[id="web-console-disable_{context}"]
 = Disabling the web console
 
 You can disable the web console by editing the

scalability_and_performance/using-cluster-loader.adoc

@@ -1,4 +1,4 @@
-[id="using_cluster_loader{context}"]
+[id="using_cluster_loader_{context}"]
 = Using Cluster Loader
 include::modules/common-attributes.adoc[]
 :context: