tech review changes

SUSE · Oct 10, 2024 · bdad016 · bdad016
1 parent 837ece3
commit bdad016
Showing 1 changed file with 10 additions and 9 deletions.
diff --git a/xml/rmt_public_cloud.xml b/xml/rmt_public_cloud.xml
@@ -63,8 +63,9 @@ 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 to 3 VCPUS and a minimum of 8GB RAM to support the
-    &rmt; deployment. For example, in AWS this would be a EC2 T3 large instance.
+  <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> .
+    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">
@@ -97,7 +98,7 @@ To support &rmt; deployment, it is recommended to deploy a &rmt; instance from a
     <term>Disk space</term>
     <listitem>
       <para>
-        The &rmt; server requires sufficient disk space to mirror the &sliberty; LTSS 7 repositories.
+        The &rmt; server requires sufficient disk space to mirror the repositories.
         Downloaded packages are available in <filename>/var/lib/rmt/public/repo/</filename>. Disk space is dependent
         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.
@@ -133,12 +134,12 @@ Cloud NAT services. Azure offers similar services.
     <term>Connectivity for clients</term>
     <listitem>
       <para>
-      Clients can connect to &rmt; on ports 80 and 443.
-      When launching the &sles; instance to support &rmt; check if in AWS the network security group is configured to allow
-      inbound access to the &rmt; server from your clients (HTTP/HTTPS). For GCP, the firewall rules must be configured to allow
-      inbound access to the &rmt; server from your clients.
-When a &sles; 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. </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.
+  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>
          </listitem>
   </varlistentry>
 </variablelist>