Fix link in ISS introduction (#4198)

* Drop satellite if(n)def for iss
* Add link to KBase as additional resource

(cherry picked from commit 4e0f79c)

Author: aneta-petrova

guides/common/modules/con_synchronizing-content-between-servers.adoc

@@ -3,29 +3,26 @@
 
 In a {Project} setup with multiple {ProjectServer}s, you can use {ISS} (ISS) to synchronize content from one upstream server to one or more downstream servers.
 
-ifndef::satellite[]
 There are two possible ISS configurations of {Project}, depending on how you deployed your infrastructure:
 
 ISS Network Sync::
 If your upstream server can communicate with the downstream server over a network, you can synchronize content over HTTPS.
 +
 Configure your {Project} to synchronize content over a network.
+ifndef::satellite[]
 For more information, see xref:configuring-server-to-synchronize-content-over-a-network_{context}[].
+endif::[]
 
 ISS Export Sync::
 If your upstream and downstream servers are air gapped, you can synchronize content by using export and import.
 +
 Configure your {Project} to synchronize content by using export and import.
+ifndef::satellite[]
 For more information, see xref:configuring-projectserver-to-synchronize-content-by-using-exports_{context}[].
+endif::[]
 
 .Additional resources
 * For more information on ISS use cases and scenarios, see {PlanningDocURL}iss-scenarios_planning[{ISS} scenarios] in _{PlanningDocTitle}_.
-endif::[]
-
 ifdef::satellite[]
-There are two possible ISS configurations of {Project}, depending on how you deployed your infrastructure.
-Configure your {Project} for ISS as appropriate for your scenario.
-For more information, see {InstallingServerDisconnectedDocURL}iss-scenarios_{project-context}[{ISS} scenarios] in _{InstallingServerDisconnectedDocTitle}_.
-
-To change the Pulp export path, see https://access.redhat.com/solutions/7013903[Hammer content export fails with "Path '/the/path' is not an allowed export path"] in the _Red{nbsp}Hat Knowledgebase_.
+* https://access.redhat.com/solutions/7013903[Hammer content export fails with "Path '/the/path' is not an allowed export path" in the _Red{nbsp}Hat Knowledgebase_]
 endif::[]