Fix inconsistencies with referencing my-rhdh-secrets

Author: GitHub Actions

modules/installation/proc-configuring-an-rhdh-instance-with-tls-in-kubernetes.adoc

@@ -119,8 +119,8 @@ data:
 <1> The base URL to the Kubernetes control plane. You can run the `kubectl cluster-info` command to get the base URL.
 <2> Set the value of this parameter to `false` to enable the verification of the TLS certificate.
 <3> Optional: The link to the Kubernetes dashboard managing the ARO cluster.
-<4> Optional: Pass the service account token using a `K8S_SERVICE_ACCOUNT_TOKEN` environment variable that you can define in your `{my-product-secrets}` secret.
-<5> Pass the CA data using a `K8S_CONFIG_CA_DATA` environment variable that you can define in your `{my-product-secrets}` secret.
+<4> Optional: Pass the service account token using a `K8S_SERVICE_ACCOUNT_TOKEN` environment variable that you define in your `{my-product-secrets}` secret.
+<5> Pass the CA data using a `K8S_CONFIG_CA_DATA` environment variable that you define in your `{my-product-secrets}` secret.
 
 . Save the configuration changes.
 

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

@@ -45,10 +45,9 @@ data:
 ----
 --
 
-. Create a Secret named `{my-product-secret}` and add a key named `BACKEND_SECRET` with a `Base64-encoded` string as value:
+. 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:
 +
 --
-.`{my-product-secrets}` fragment
 [source,yaml,subs="+quotes,+attributes"]
 ----
 apiVersion: v1
@@ -110,10 +109,9 @@ spec:
 ----
 --
 
-. Set up a Google-managed certificate by creating a `ManagedCertificate` object which you must attach to the Ingress.
+. Set up a Google-managed certificate by creating a `ManagedCertificate` object which you must attach to the Ingress as shown in the following example:
 +
 --
-.Example of a `ManagedCertificate` object
 [source,yaml,subs="attributes+"]
 ----
 apiVersion: networking.gke.io/v1

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

@@ -114,7 +114,7 @@ data:
 ----
 --
 
-. Create a Secret named `{my-product-secrets}` and add a key named `BACKEND_SECRET` with a `Base64-encoded` string value as shown in the following example:
+. Create a secret named `{my-product-secrets}` and add a key named `BACKEND_SECRET` with a `Base64-encoded` string value as shown in the following example:
 +
 --
 [source,yaml,subs="+quotes,+attributes"]