Fix inconsistencies with referencing my-rhdh-secrets

Author: GitHub Actions

modules/installation/proc-deploy-rhdh-instance-gke.adoc

@@ -45,19 +45,20 @@ data:
 ----
 --
 
-. Create a secret named `{my-product-secret}` and add a key named `BACKEND_SECRET` with a `Base64-encoded` string value as shown in the following example:
+. Create a `_<my-product-secrets>_` secret and add a key named `BACKEND_SECRET` with a `Base64-encoded` string value as shown in the following example:
 +
 --
 [source,yaml,subs="+quotes,+attributes"]
 ----
 apiVersion: v1
 kind: Secret
 metadata:
-  name: `{my-product-secret}`
+  name: `_<my-product-secrets>_` # <1>
 stringData:
   # TODO: See https://backstage.io/docs/auth/service-to-service-auth/#setup
   BACKEND_SECRET: "xxx"
 ----
+<1> Replace `<my-product-secrets>` with a unique identifier for your secret configuration.
 
 [IMPORTANT]
 ====
@@ -105,8 +106,9 @@ spec:
         - name: "app-config-rhdh"
     extraEnvs:
       secrets:
-        - name: `{my-product-secret}`
+        - name: `_<my-product-secrets>_` # <1>
 ----
+<1> Replace `<my-product-secrets>` with a unique identifier for your secret configuration.
 --
 
 . Set up a Google-managed certificate by creating a `ManagedCertificate` object which you must attach to the Ingress as shown in the following example:

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

@@ -147,8 +147,9 @@ spec:
         - name: "app-config-rhdh"
     extraEnvs:
       secrets:
-        - name: `{my-product-secret}`
+        - name: `_<my-product-secrets>_` # <1>
 ----
+<1> Replace `<my-product-secrets>` with a unique identifier for your secret configuration.
 --
 
 . Apply the CR manifest to your namespace: