Incorporated Lindsey's comment

Author: pabel-rh

assemblies/assembly-configuring-readonlyrootfilesystem.adoc

@@ -3,7 +3,7 @@
 [id="{context}"]
 = Configuring readOnlyRootFilesystem in {product}
 
-The {product} deployment consists of two containers, an `initContainer` that installs the Dynamic Plugins, and a backend container which runs the application. The `initContainer` has the `readOnlyRootFilesystem` option enabled by default. To enable this option on the backend container, you must either have permission to deploy resource through Helm or to create or update a CR for Operator-backed deployments. You can manually configure the `readOnlyRootFilesystem` option on the backend container by using the following methods:
+The {product} deployment consists of two containers: an `initContainer` that installs the Dynamic Plugins, and a backend container that runs the application. The `initContainer` has the `readOnlyRootFilesystem` option enabled by default. To enable this option on the backend container, you must either have permission to deploy resources through Helm or to create or update a CR for Operator-backed deployments. You can manually configure the `readOnlyRootFilesystem` option on the backend container by using the following methods:
 
 include::modules/configuring-readonlyrootfilesystem/proc-configuring-readonlyrootfilesystem-option-in-rhdh-operator-deployment.adoc[leveloffset=+1]
 

modules/configuring-readonlyrootfilesystem/proc-configuring-readonlyrootfilesystem-option-in-rhdh-helm-chart-deployment.adoc

@@ -2,7 +2,7 @@
 = Configuring the readOnlyRootFilesystem option in a {product} Helm chart deployment
 
 .Procedure
-. When you are deploying {product-short} using the Helm chart, add the `readOnlyRootFilesystem: true` line to the `containerSecurityContext` section in your `values.yaml` file. For example:
+. In your 'values.yaml' file, add the `readOnlyRootFilesystem: true` line to the `containerSecurityContext` section. For example:
 +
 ====
 [source,yaml,subs="+attributes,+quotes"]

modules/configuring-readonlyrootfilesystem/proc-configuring-readonlyrootfilesystem-option-in-rhdh-operator-deployment.adoc

@@ -1,11 +1,11 @@
 [id="proc-configuring-readonlyrootfilesystem-option-in-rhdh-operator-deployment"]
 = Configuring the readOnlyRootFilesystem option in a {product} Operator deployment
 
-When you are deploying {product-short} using the Operator, specify a `patch` for the `deployment` in your `{product-custom-resource-type}` custom resource (CR) that applies the `readOnlyRootFilesystem` option to the `securityContext` section in the {product-short} backend container.
+When you are deploying {product-short} using the Operator, you must specify a `patch` for the `deployment` in your `{product-custom-resource-type}` custom resource (CR) that applies the `readOnlyRootFilesystem` option to the `securityContext` section in the {product-short} backend container.
 
 .Procedure
 
-. Add the `securityContext` specification in your CR. For example:
+. In your `{product-custom-resource-type}` CR, add the `securityContext` specification in your CR. For example:
 +
 ====
 [source,yaml,subs="+attributes,+quotes"]
@@ -17,8 +17,9 @@ spec:
         template:
           spec:
             containers:
-              - name: backstage-backend
+              - name: backstage-backend <1>
                 securityContext:
                   readOnlyRootFilesystem: true
 ----
-====
+====
+<1> Name of the main container defined in the Operator default configuration.