edits per peer review

#7090
OpenLiberty · Dec 8, 2023 · baa71b5 · baa71b5
1 parent 44a9f6a
commit baa71b5
Showing 1 changed file with 3 additions and 3 deletions.
diff --git a/modules/ROOT/pages/instanton.adoc b/modules/ROOT/pages/instanton.adoc
@@ -318,7 +318,7 @@ Currently, Open Liberty InstantOn is tested and supported on the following publi
 
 - link:https://aws.amazon.com/eks/[Amazon Elastic Kubernetes Service (EKS)]
 - link:https://azure.microsoft.com/en-us/products/kubernetes-service[Azure Kubernetes Service (AKS)]
-- link:https://www.redhat.com/en/technologies/cloud-computing/openshift[Red Hat OpenShift] (version 4.14 and later)
+- link:https://www.redhat.com/en/technologies/cloud-computing/openshift[Red Hat OpenShift (version 4.14 and later)]
 
 Other public cloud Kubernetes services might also work if they have the <<#required-to-restore,prerequisites>> to allow the InstantOn application process to restore.
 
@@ -340,7 +340,7 @@ When you deploy to Kubernetes, the container must be granted the `CHECKPOINT_RES
 
 ==== Red Hat OpenShift security context constraints
 
-To deploy applications to Red Hat OpenShift with InstantOn, you must specify a security context constraint (SCC) that at a minimum specifies a list of additional capabilities that are added to any pod. The following SSC yaml file example defines an SCC with the required capabilities by using the `defaultAddCapabilities` parameter :
+To deploy applications to Red Hat OpenShift with InstantOn, you must specify a security context constraint (SCC) that, at a minimum, specifies a list of additional capabilities that are added to any pod. The following SSC yaml file example defines an SCC with the required capabilities by using the `defaultAddCapabilities` parameter:
 
 [source,yaml]
 ----
@@ -349,7 +349,7 @@ defaultAddCapabilities:
 - SETPCAP
 ----
 
-The applications you deploy must be associated with an SCC that adds the required capabilities. For example, you might deploy an SCC called `liberty-instanton-scc` that adds the required capabilities. The following deployment yaml file example specifies the `serviceAccountName` parameter to set the SCC name to `liberty-instanton-scc`:
+The applications you deploy must be associated with an SCC that adds the required capabilities. For example, you might deploy an SCC called `liberty-instanton-scc` that adds the required capabilities. In the following example, the deployment yaml file specifies the `serviceAccountName` parameter to set the SCC name to `liberty-instanton-scc`:
 
 [source,yaml]
 ----