review feedback

xml/rmt_public_cloud.xml

@@ -15,8 +15,8 @@
     </dm:docmanager>
   </info>
   <para>
-You can deploy a &sls; instance to support &rmt; in Amazon Web Services(AWS), Google Cloud Platform(GCP), and Microsoft Azure.
-The Repository Mirroring Tool (RMT) is included in &sls; starting with version 15. </para>
+You can deploy a &sls; instance to support &rmt; in Amazon Web Services (AWS), Google Cloud Platform (GCP), and Microsoft Azure.
+&rmt; is included in &slsa; starting with version 15. </para>
   <para>
   The following example shows a generic cloud architecture for the &rmt; deployment. Your deployment may look different based
   on your networking requirements. </para>
@@ -31,14 +31,14 @@ The Repository Mirroring Tool (RMT) is included in &sls; starting with version 1
   <sect1 xml:id="sec-rmt-byos-image">
 <title>Using a bring-your-own-subscription image</title>
 <para>
-SUSE provides images for &sls; in Amazon Web Services, Google Cloud, and Microsoft Azure. There are two types of images available;
+SUSE provides images for &slsa; in Amazon Web Services, Google Cloud and Microsoft Azure. There are two types of images available:
 PAYG (Pay-As-You-Go) and BYOS (Bring-Your-Own-Subscription). These images are updated at regular intervals and it is suggested that you deploy
 new instances from the latest version of the image to ensure the most recent security updates are in place.
-To support &rmt; deployment, it is recommended to deploy a &rmt; instance from a BYOS image.
+To support &rmt; deployment, we recommend deploying an &rmt; instance from a BYOS image.
 </para>
 <sect2 xml:id="sec-rmt-byos-image-where">
   <title>Finding images in the cloud marketplace </title>
-  <para>Where to find the relevant image in each of the cloud provider is shown below: </para>
+  <para>The location of the relevant image in each of the cloud provider is shown below: </para>
   <figure>
     <title>Google Cloud</title>
     <mediaobject>
@@ -63,18 +63,20 @@ To support &rmt; deployment, it is recommended to deploy a &rmt; instance from a
       </imageobject>
        </mediaobject>
   </figure>
-  <para>It is recommended to start with an instance type with 2 or more vCPUs and a minimum of 8GB RAM to support
-    the &rmt; deployment. For example on Amazon EC2, this could be a <literal>t3.large</literal> instance type, in Microsoft Azure it could be a <literal>B2as_v2</literal> .
+  <para>It is recommended to start with an instance type that has at least
+    two vCPUs and a minimum of 8&nbsp;GB RAM to support the &rmt; deployment.
+    For example, on Amazon EC2, this could be a <literal>t3.large</literal>
+    instance type, and in Microsoft Azure, it could be a <literal>B2as_v2</literal>
     The instance can be rightsized as needed and depends on the number of clients being managed and updated by the &rmt; server.
     </para>
 </sect2>
 <sect2 xml:id="sec-rmt-byos-image-registration">
-  <title>Registering the &sls; instance</title>
-  <para>After the &sls; instance deployment, you must register the instance with the SUSE Customer Center.</para>
+  <title>Registering the &slsa; instance</title>
+  <para>After the &slsa; instance deployment, you must register the instance with the SUSE Customer Center.</para>
   <note>
     <title>&suse; account</title>
     <para>
-     Registering with the &scc; requires a SUSE account. In case you do not have
+     Registering with the &scc; requires a SUSE account. If you do not have
      a SUSE account yet, go to the &scc; home page (<link
      xlink:href="https://scc.suse.com/"/>) to create one.
     </para>
@@ -86,9 +88,9 @@ To support &rmt; deployment, it is recommended to deploy a &rmt; instance from a
    <screen>&prompt.user; <command>gcloud compute ssh <replaceable>GCE_INSTANCE_IP</replaceable></command></screen>
    <para>Azure:</para>
    <screen>&prompt.user; <command>ssh <replaceable>AZURE_USER_ID</replaceable>@<replaceable>SERVER_IP</replaceable></command></screen>
-  <para>To register the &sls; instance with SCC: </para>
+  <para>To register the &slsa; instance with SCC: </para>
   <screen>&prompt.sudo; <command>SUSEConnect -e <replaceable>EMAIL_ADDRESS</replaceable> -r <replaceable>REGISTRATION_CODE </replaceable></command></screen>
-  <para>The registration code is available, once you log in to  SCC. </para>
+  <para>The registration code is available once you log in to  SCC. </para>
 </sect2>
 </sect1>
 <sect1><title>Considerations when using &rmt;</title>
@@ -103,7 +105,7 @@ To support &rmt; deployment, it is recommended to deploy a &rmt; instance from a
         on the number of repositories you mirror. We recommend a minimum of 1.5 times the total size of all enabled repositories.
         It is a best practice to provision an additional disk volume to support this requirement.
         You can either mount the volume to <filename>/var/lib/rmt/public/repo/</filename> on instance creation or immediately after the launch.
-        For Azure, it is an additional disk volume. An Amazon EBS volume for AWS and a persistent disk volume for GCP.
+        For Azure, this is an additional disk volume. For AWS, it is an Amazon EBS volume and for GCP, it is a persistent disk volume .
               </para>
          </listitem>
   </varlistentry>
@@ -112,8 +114,8 @@ To support &rmt; deployment, it is recommended to deploy a &rmt; instance from a
     <listitem>
       <para>
         A static IP address or a DNS name is required in order for clients to connect to the &rmt; server.
-        In Azure, AWS and GCP, a Cloud Service Provider(CSP) provided DNS is assigned when the instance is launched.
-        This IP or DNS may change if the instance is recreated. For Azure, consider using a static IP address to provide a consistent
+        In Azure, AWS and GCP, a DNS provided by the Cloud Service Provider (CSP) is assigned when the instance is launched.
+        This IP or DNS may change if the instance is re-created. For Azure, consider using a static IP address to provide a consistent
         connection point for your clients. In AWS, this would be an elastic IP or Route53. In GCP, this would be a cloud DNS
         record that uses a static IP address.
         </para>
@@ -124,8 +126,8 @@ To support &rmt; deployment, it is recommended to deploy a &rmt; instance from a
     <listitem>
       <para>
       The &rmt; server can connect to SCC on ports 80 and 443. There are many ways to provide connectivity.
-For example, in AWS, connectivity to SCC can be provided via an AWS Internet Gateway, an AWS NAT Gateway, or via a local data center (VPN/DX Connection) but this is dependent
-on whether the &rmt; instance is in a public or private subnet. GCP provides direct access to the internet via the VPC routes or
+For example, in AWS, connectivity to SCC can be provided via an AWS Internet Gateway, an AWS NAT Gateway, or via a local data center (VPN/DX Connection) but this is depends
+on whether the &rmt; instance is in a public or private subnet. GCP provides direct access to the Internet via the VPC routes or
 Cloud NAT services. Azure offers similar services.
         </para>
          </listitem>
@@ -135,8 +137,8 @@ Cloud NAT services. Azure offers similar services.
     <listitem>
       <para>
         Clients can connect to &rmt; on ports 80 and 443.
-        When launching the &sles; instance to support &rmt; check if network connectivity allows inbound access to the &rmt; server from your clients (HTTP/HTTPS).
-  For AWS, when a &sles; instance is launched to support &rmt;, it is possible to use an existing AWS security group or a new one.
+        When launching the &slsa; instance to support &rmt;, check if network connectivity allows inbound access to the &rmt; server from your clients (HTTP/HTTPS).
+  For AWS, when a &slsa; instance is launched to support &rmt;, it is possible to use an existing AWS security group or a new one.
   The security group must be configured to allow inbound access to the &rmt; server from your clients.
   For GCP, the firewall rules must be configured to allow inbound access to the &rmt; server from your clients.
    </para>