diff --git a/server_installation/topics/operating-mode/crossdc.adoc b/server_installation/topics/operating-mode/crossdc.adoc
index 0f00d2ee0c..308005c46c 100644
--- a/server_installation/topics/operating-mode/crossdc.adoc
+++ b/server_installation/topics/operating-mode/crossdc.adoc
@@ -137,7 +137,7 @@ For more detail about how caches can be configured see <<tuningcache>>.
 [[communication]]
 ==== Communication details
 
-{project_name} uses multiple, separate clusters of Infinispan caches. Every {project_name} node is in the cluster with the other {project_name} nodes in same data center, but not with the {project_name} nodes in different data centers. A {project_name} node does not communicate directly with the {project_name} nodes from different data centers. {project_name} nodes use external {jdgserver_name} servers for communication across data centers. This is done using the link:https://infinispan.org/docs/stable/titles/server/server.html#hot_rod[Infinispan Hot Rod protocol].
+{project_name} uses multiple, separate clusters of Infinispan caches. Every {project_name} node is in the cluster with the other {project_name} nodes in same data center, but not with the {project_name} nodes in different data centers. A {project_name} node does not communicate directly with the {project_name} nodes from different data centers. {project_name} nodes use external {jdgserver_name} servers for communication across data centers. This is done using the link:https://infinispan.org/docs/11.0.x/titles/hotrod_java/hotrod_java.html[Infinispan Hot Rod protocol].
 
 The Infinispan caches on the {project_name} side use link:https://infinispan.org/docs/stable/titles/configuring/configuring.html#remote_cache_store[`remoteStore`] configuration to offload data to a remote {jdgserver_name} cluster.
 {jdgserver_name} clusters in separate data centers then replicate that data to ensure it is backed up.
@@ -146,8 +146,6 @@ The receiving {jdgserver_name} server notifies the {project_name} servers in its
 
 See the <<archdiagram>> for more details.
 
-include::crossdc/assembly-setting-up-crossdc.adoc[leveloffset=3]
-
 [[setup]]
 ==== Setting up Cross DC with {jdgserver_name} {jdgserver_version}
 
@@ -634,6 +632,8 @@ should be immediately visible on any of 4 nodes as caches should be properly inv
 Event 'CLIENT_CACHE_ENTRY_REMOVED', key '193489e7-e2bc-4069-afe8-f1dfa73084ea', skip 'false'
 ```
 
+include::crossdc/assembly-setting-up-crossdc.adoc[leveloffset=3]
+
 [[administration]]
 ==== Administration of Cross DC deployment
 
diff --git a/server_installation/topics/operating-mode/crossdc/proc-configuring-remote-cache.adoc b/server_installation/topics/operating-mode/crossdc/proc-configuring-remote-cache.adoc
index 80d83b7241..40b1c0d273 100644
--- a/server_installation/topics/operating-mode/crossdc/proc-configuring-remote-cache.adoc
+++ b/server_installation/topics/operating-mode/crossdc/proc-configuring-remote-cache.adoc
@@ -126,7 +126,7 @@ For example, add a cache named `sessions` with the following configuration:
 [source,options="nowrap",subs=attributes+]
 ----
 Received new cluster view for channel keycloak: [node11|1] (2) [node11, node12]
------
+----
 
 ifeval::[{project_product}==true]
 [role="_additional-resources"]