Add emphasis on cloning prerequisite for older branches (#4187)

Refs #4161

Users usually run into issues where the cloned {Project} server will communicate with the source {Project} instead of itself. To prevent this, users should always have the cloned server on an isolated network. Emphasizing the consequence of not doing so.

JIRA: https://issues.redhat.com/browse/SAT-31411
Specifically, this comment:
https://issues.redhat.com/browse/SAT-31411?focusedId=26829261&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-26829261

Co-authored-by: Akshay Gadhave <[email protected]>
(cherry picked from commit 0d91b6a)

Author: 2 people

guides/common/modules/proc_cloning-satellite-server.adoc

@@ -43,7 +43,7 @@ You can use a backup with or without Pulp data.
 Before you begin cloning, ensure the following conditions exist:
 
 * The target server is on an isolated network.
-This avoids unwanted communication with {SmartProxyServers} and hosts.
+This prevents the cloned {ProjectServer} from accidentally communicating with the source {ProjectServer}, {SmartProxyServers}, and hosts.
 * The target server has at least the same storage capacity as the source server.
 
 .Customized configuration files