HCP docs minor corrections

Author: mletalie

modules/rosa-hcp-classic-comparison.adoc

@@ -1,12 +1,12 @@
 // Module included in the following assemblies:
 //
-// * rosa_hcp/rosa-hcp-sts-creating-a-cluster-quickly.adoc 
+// * rosa_hcp/rosa-hcp-sts-creating-a-cluster-quickly.adoc
 
 :_content-type: CONCEPT
 [id="rosa-hcp-classic-comparison_{context}"]
 = Comparing ROSA with hosted control planes and ROSA Classic
 
-{hcp-title-first} offers a different way to create a managed {product-title} (ROSA) cluster. {hcp-title} offers a reduced-cost solution with focuses on reliability and efficiency. With a focus on efficiency, you can quickly create a new cluster and deploy applications in minutes. 
+{hcp-title-first} offers a different way to create a managed {product-title} (ROSA) cluster. {hcp-title} offers a reduced-cost solution with focuses on reliability and efficiency. With a focus on efficiency, you can quickly create a new cluster and deploy applications in minutes.
 
 {hcp-title} requires only a minimum of two nodes making it ideal for smaller projects while still being able to scale to support larger projects and enterprises.
 
@@ -15,31 +15,32 @@
 [cols="3a,8a,8a",options="header"]
 |===
 | {nbsp} +
-| Hosted Control Plane 
+| Hosted Control Plane
 | Classic
 
-| Cluster infrastructure hosting
-| {hcp-title} deploys control plane components, such as etcd, API server, and oauth, that are hosted separately on AWS in a Red Hat-owned and managed account. 
+| *Cluster infrastructure hosting*
+| {hcp-title} deploys control plane components, such as etcd, API server, and oauth, that are hosted separately on AWS in a Red Hat-owned and managed account.
 | ROSA Classic deploys the control plane components side by side with infrastructure and worker nodes that are hosted together in the customer’s same AWS account.
 
 | *Provisioning Time*
-| Approximately 10 minutes 
-| Approximately 40 minutes 
+| Approximately 10 minutes
+| Approximately 40 minutes
 
 | *Architecture*
 |
-    * Underlying control plane infrastructure is fully managed and directly unavailable to end customers except through dedicated and explicitly exposed endpoints
+    * Underlying control plane infrastructure is fully managed
+    * Customer can access control plane infrastructure through dedicated and explicitly exposed endpoints
     * Work nodes are hosted in the customer's AWS account
 |
     * Customer is responsible for hosting control plane and AWS infrastructure, while still being _managed_ by Red Hat
     * Work nodes are hosted in the customer's AWS account
-    
+
 | *Minimum Amazon EC2 footprint*
 | One cluster requires a minimum of two nodes
 | One cluster requires a minimum of seven nodes
 
-| *Deployment* 
-| 
+| *Deployment*
+|
     * Deploy using the ROSA CLI (`rosa`)
     * Customers provision "Hosted Clusters" that deploy the control plane components into Red Hat's AWS account
     * Customers provision "Machine Pools" that deploy worker nodes into the customer's AWS account
@@ -51,20 +52,20 @@
 | Selectively upgrade control plane and machine pools separately
 | Entire cluster is upgraded at one time
 
-| *Regional Availability* 
-| 
+| *Regional Availability*
+|
 * Europe - Frankfort (eu-central-1)
 * Europe - Ireland (eu-west-1)
 * US East - N. Virginia (us-east-1)
 * US East - Ohio (us-east-2)
 * US West - Oregon (us-west-2)
 * Asia Pacific - Jakarta (ap-southeast-3)
-| For AWS Region availability, see link:https://docs.aws.amazon.com/general/latest/gr/rosa.html[Red Hat OpenShift Service on AWS endpoints and quotas] in the AWS documentation. 
+| For AWS Region availability, see link:https://docs.aws.amazon.com/general/latest/gr/rosa.html[Red Hat OpenShift Service on AWS endpoints and quotas] in the AWS documentation.
 
-| *Compliance* 
-| 
+| *Compliance*
+|
     * Compliance certifications and FIPS are not yet available.
-| 
+|
     * Compliance specifics are located in the {product-title} documentation.
 |===