Rhidp 5375 consistent mentions to the product project

modules/dynamic-plugins/proc-create-plugin-tgz-file.adoc

@@ -50,7 +50,7 @@ To create a plugin registry using HTTP server on {ocp-short}, run the following
 .Example commands to build and deploy an HTTP server in {ocp-short}
 [source,terminal]
 ----
-oc project rhdh
+oc project {my-product-namespace}
 oc new-build httpd --name=plugin-registry --binary
 oc start-build plugin-registry --from-dir=dynamic-plugins-root --wait
 oc new-app --image-stream=plugin-registry

modules/installation/proc-install-rhdh-airgapped-environment-ocp-helm.adoc

@@ -94,7 +94,7 @@ If an x509 error occurs, verify that you have link:https://access.redhat.com/sol
 +
 [source,terminal]
 ----
-oc get imagestream -n <project_name>
+oc get imagestream -n {my-product-namespace}
 ----
 
 . Enable local image lookup for both images by running the following commands:

modules/installation/proc-install-rhdh-ocp-helm-cli.adoc

@@ -14,7 +14,7 @@ You can use the Helm CLI to install {product} on {ocp-brand-name}.
 * You have installed the Helm CLI tool.
 
 .Procedure
-. Create and activate the _<rhdh>_ {ocp-short} project:
+. Create and activate the _<{my-product-namespace}>_ {ocp-short} project:
 +
 [subs="quotes+"]
 ----

modules/installation/proc-rhdh-deploy-aks-helm.adoc

@@ -108,7 +108,7 @@ The previous command configures the Kubernetes client and sets the current conte
 helm repo add openshift-helm-charts https://charts.openshift.io/
 ----
 
-. Create and activate the _<rhdh>_ namespace:
+. Create and activate the _<{my-product-namespace}>_ namespace:
 +
 [source,terminal,subs="quotes+"]
 ----

modules/installation/proc-rhdh-deploy-aks-operator.adoc

@@ -56,13 +56,13 @@ kubectl -n <your_namespace> create secret docker-registry rhdh-pull-secret \
 . Create an Ingress manifest file, named `rhdh-ingress.yaml`, specifying your {product-short} service name as follows:
 +
 --
-[source,yaml]
+[source,yaml,subs="+attributes,+quotes"]
 ----
 apiVersion: networking.k8s.io/v1
 kind: Ingress
 metadata:
   name: rhdh-ingress
-  namespace: <your_namespace>
+  namespace: {my-product-namespace}
 spec:
   ingressClassName: webapprouting.kubernetes.azure.com
   rules:
@@ -153,18 +153,18 @@ spec:
 . Apply the CR manifest to your namespace:
 +
 --
-[source,terminal]
+[source,terminal,subs="+attributes,+quotes"]
 ----
-kubectl -n <your_namespace> apply -f rhdh.yaml
+kubectl -n {my-product-namespace} apply -f rhdh.yaml
 ----
 --
 
 . Access the deployed {product-short} using the URL: `https://<app_address>`, where <app_address> is the Ingress address obtained earlier (for example, `https://108.141.70.228`).
 . Optional: To delete the CR, run the following command:
 +
 --
-[source,terminal]
+[source,terminal,subs="+attributes,+quotes"]
 ----
-kubectl -n <your_namespace> delete -f rhdh.yaml
+kubectl -n {my-product-namespace} delete -f rhdh.yaml
 ----
 --

modules/observe/proc-admin-enabling-metrics-ocp-operator.adoc

@@ -20,20 +20,20 @@ Currently, the {product} Operator does not support creating a `ServiceMonitor` c
 
 . Create the `ServiceMonitor` CR as a YAML file:
 +
-[source,yaml]
+[source,yaml,subs="+attributes,+quotes"]
 ----
 apiVersion: monitoring.coreos.com/v1
 kind: ServiceMonitor
 metadata:
   name: <custom_resource_name> # <1>
-  namespace: <project_name> # <2>
+  namespace: {my-product-namespace} # <2>
   labels:
     app.kubernetes.io/instance: <custom_resource_name>
     app.kubernetes.io/name: backstage
 spec:
   namespaceSelector:
     matchNames:
-      - <project_name>
+      - {my-product-namespace}
   selector:
     matchLabels:
       rhdh.redhat.com/app: backstage-<custom_resource_name>

modules/observe/proc-forward-audit-log-splunk.adoc

@@ -82,14 +82,14 @@ serviceAccount:
 +
 --
 .Example `inputs` configuration
-[source,yaml]
+[source,yaml,subs="+attributes,+quotes"]
 ----
 inputs:
   - name: my-app-logs-input
     type: application
     application:
       includes:
-        - namespace: my-developer-hub-namespace
+        - namespace: {my-product-namespace}
       containerLimit:
         maxRecordsPerSecond: 100
 ----

modules/proc-create-plugin.adoc

@@ -11,7 +11,7 @@ You can create a plugin for the {product-short} application.
 
 .Procedure
 
-. In the terminal application, run the following command from the root of your {product-short} project:
+. In the terminal application, run the following command from the root of your {my-product-namespace} project:
 +
 --
 [source,terminal]

modules/upgrade/proc-upgrade-rhdh-helm.adoc

@@ -29,10 +29,10 @@ It might take a few minutes to delete the resources in the older versions and to
 
 . Log in to the {ocp-short} cluster as the cluster administrator and switch to the project or namespace in which {product-short} was installed.
 +
-[source,terminal]
+[source,terminal,subs="+attributes,+quotes"]
 ----
 oc login -u <user> -p <password> https://api.<HOSTNAME>:6443
-oc project <your_namespace>
+oc project {my-product-namespace}
 ----
 
 . For a new version of the {product-short} Helm chart, run the following upgrade command: