PAYG requirement clarified. (#4461)

Author: 0rnela

.changelog

@@ -4,6 +4,8 @@
 # - Fixed error in Bat section of Upgrade Guide (bsc#1234567)
 # For guidelines: https://en.opensuse.org/openSUSE:Creating_a_changes_file_(RPM)#Changelog_section_.28.25changelog.29
 
+- Clarified requirement for PAYG in Installation and Upgrade
+  Guide (bsc#1236066)
 - Added information for proxy migration to Installation and
   Upgrade Guide (bsc#1214568)
 - Added reference to dry run documentation (bsc#1223368)

modules/installation-and-upgrade/pages/connect-payg.adoc

@@ -15,9 +15,9 @@ Then the {productname} Server has access to products on the RMT host that are no
 
 Before using {payg} feature make sure that: 
 
-* The {payg} instance is launched from the correct SUSE product image (for example, SLES, SLES for SAP, or SLE HPC) to allow access to the desired repositories
+* The {payg} instance is launched from the correct SUSE product image (for example, SLES, SLES for SAP, or SLE HPC) to allow access to the desired repositories.
 
-* {productname} Server has connectivity to the {payg} instance (ideally in the same region) either directly or via a bastion
+* {productname} Server has connectivity, directly or via a bastion, to the {payg} connection endpoint, which must be in the same region as the Server.
 
 * A basic {scc} account is required. Enter your valid {scc} credentials in menu:Admin[Setup Wizard > Organization Credentials]. This account is required for accessing the {productname} client tools for boostrapping regardless of {payg} instances.