Server container install adjustments (#3051)

modules/installation-and-upgrade/pages/general-requirements.adoc

@@ -3,9 +3,11 @@
 
 Before you begin installation, ensure that you have:
 
-. A {scc} account. This account gives you access to organization credentials and registration keys for {micro} {microversion} and {productname} Server and Proxy
-. Supported Browsers for {productname} {webui}
-. SSL certificates for your environment. By default {productname} {productnumber} uses a self-signed certificate.
+. A {scc} account.
+  This account gives you access to organization credentials and registration keys for {micro} {microversion} and {productname} Server and Proxy.
+. Supported Browsers for {productname} {webui}.
+. SSL certificates for your environment.
+  By default {productname} {productnumber} uses a self-signed certificate.
 
 
 The following section contains more information on these requirements.
@@ -18,14 +20,14 @@ Create an account with {scc} prior to deployment of {productname} {productnumber
 
 [[creating.scc.account.mgr]]
 .Procedure: Obtain Your Organization Credentials
-. Navigate to https://scc.suse.com/login in your Web browser.
+. Navigate to https://scc.suse.com/login in your web browser.
 . Log in to your SCC account, or follow the prompts to create a new account.
 . If you have not yet done so, click btn:[Connect to an Organization] and type or search for your organization.
-. Click btn:[Manage my Organizations] and select your organization from the list by clicking on the organization name.
-. Click the btn:[Organization] tab, and then select the btn:[Organization Credentials] tab.
+. Click btn:[Manage my Organizations] and select your organization from the list by clicking the organization name.
+. Click the btn:[Users] tab, and then select the btn:[Organization Credentials] sub-tab.
 . Record your login information for use during {productname} setup.
 
-Depending on your organization's setup, you might also need to activate your subscription, using the btn:[Activate Subscriptions] menu.
+Depending on your organization's setup, you might also need to activate your subscription, using the btn:[Activate Subscriptions] menu from the left navigation bar.
 
 For more information about using SCC, see https://scc.suse.com/docs/help.
 
@@ -34,7 +36,7 @@ For more information about using SCC, see https://scc.suse.com/docs/help.
 [[installation-general-supportedbrowsers]]
 == Supported Browsers for {productname} {webui}
 
-In order to use the {webui} to manage your {productname} environment, you will need to ensure you are running an up-to-date web browser.
+To use the {webui} to manage your {productname} environment, you must run an up to date web browser.
 
 {productname} is supported on:
 

modules/installation-and-upgrade/pages/hardware-requirements.adoc

@@ -169,7 +169,9 @@ For more information about managing a large number of clients, see xref:speciali
 
 |
 | [path]``/var/lib/containers/storage/volumes/srv-www``
-| Minimum 100 GB * Storage requirments should be calculated for the number of ISO distribution images, containers, and bootstrap repositories you will use. 
+| Minimum 100 GB
+
+* Storage requirments should be calculated for the number of ISO distribution images, containers, and bootstrap repositories you will use.
 
 |
 | [path]``/var/lib/containers/storage/volumes/var-cache`` (Squid)
@@ -179,14 +181,14 @@ For more information about managing a large number of clients, see xref:speciali
 
 
 By default the {productname} Proxy container caches packages in the [path]``/var/lib/containers/storage/volumes/var-cache/`` directory.
-If there is not enough space available in [path]``/var/lib/containers/storage/volumes/var-cache/``, the proxy will remove old, unused packages and replace them with newer packages.
+If there is not enough space available, the proxy will remove old, unused packages and replace them with newer packages.
 
 As a result of this behavior:
 
-* The larger [path]``/var/lib/containers/storage/volumes/var-cache/`` directory is on the proxy, the less traffic there will be between it and the {productname} Server.
+* The larger [path]``/var/lib/containers/storage/volumes/var-cache/`` directory is on the proxy, the less traffic will be between the proxy and the {productname} Server.
 * By making the [path]``/var/lib/containers/storage/volumes/var-cache/`` directory on the proxy the same size as [path]``/var/lib/containers/storage/volumes/var-spacewalk/`` on the {productname} Server, you avoid a large amount of traffic after the first synchronization.
 * The [path]``/var/lib/containers/storage/volumes/var-cache/`` directory can be small on the {productname} Server compared to the proxy.
-    For a guide to size estimation, see the <<server-hardware-requirements>> section.
+  For a guide to size estimation, see the <<server-hardware-requirements>> section.
 
 
 
@@ -209,17 +211,15 @@ endif::[]
 
 
 
-
-
 == Persistent Storage and Permissions
 
 Persistent volumes are created by default when deploying the container.
 
 However, it is recommended that the repositories and the database for {productname} are stored on separate storage devices.
 Such a setup helps avoid data loss in production environments.
 
-Storage devices must be setup prior to deploying the container.
-For more details see: xref:installation-and-upgrade:container-management/persistent-container-volumes.adoc[Persistent Container Volumes]
+Storage devices must be set up prior to deploying the container.
+For more details, see xref:installation-and-upgrade:container-management/persistent-container-volumes.adoc[Persistent Container Volumes].
 
 {productname} requires three different volumes:
 
@@ -232,7 +232,7 @@ Additionally, for on-premise installations, consider using logical volume manage
 The size of the disk for repositories storage is dependent on the number of distributions and channels you intend to manage with {productname}.
 See the tables in this section for guides to estimate the size required.
 
-On your {productname} Server, use this command to find all available storage devices:
+On the {productname} Server, use this command to find all available storage devices:
 
 ----
 hwinfo --disk | grep -E "Device File:"
@@ -285,7 +285,6 @@ drwxr-x--- 1 10556 10556 48 Apr 19 14:33 _data
 /var/lib/containers/storage/volumes/var-spacewalk:
 total 0
 drwxr-xr-x 1 10552 root 30 Apr 19 14:34 _data
-
 ----
 
 If required, change the permissions with these commands: