diff --git a/ee/ucp/admin/install/plan-installation.md b/ee/ucp/admin/install/plan-installation.md
index 0f3ad54f09..f06c8fd620 100644
--- a/ee/ucp/admin/install/plan-installation.md
+++ b/ee/ucp/admin/install/plan-installation.md
@@ -36,7 +36,7 @@ node3.company.example.com
 
 ## Static IP addresses
 
-Docker UCP requires each node on the cluster to have a static IP address.
+Docker UCP requires each node on the cluster to have a static IPv4 address.
 Before installing UCP, ensure your network and nodes are configured to support
 this.
 
@@ -121,8 +121,8 @@ conflict with the underlying infrastructure:
 
 * The Pod Network -  Each Pod in Kubernetes is given an IP address from either
   the Calico or Azure IPAM services. In a default installation Pods are given
-  IP addresses on the `192.168.0.0/16` range. This can be customized at install
-  time using the `--pod-cidr` flag.
+  IP addresses on the `192.168.0.0/16` range. This can be customized at install time by passing the `--pod-cidr` flag to the 
+  [UCP install command](/reference/ucp/{{ site.ucp_version }}/cli/install/). 
 * The Services Network - When a user exposes a Service in Kubernetes it is
   accessible via a VIP, this VIP comes from a Cluster IP Range. By default on UCP
   this range is `10.96.0.0/16`. Beginning with 3.1.8, this value can be
@@ -147,7 +147,7 @@ firewall-cmd --reload
 In distributed systems like Docker UCP, time synchronization is critical
 to ensure proper operation. As a best practice to ensure consistency between
 the engines in a UCP cluster, all engines should regularly synchronize time
-with a Network Time Protocol (NTP) server. If a server's clock is skewed,
+with a Network Time Protocol (NTP) server. If a host node's clock is skewed,
 unexpected behavior may cause poor performance or even failures.
 
 ## Load balancing strategy
@@ -176,7 +176,8 @@ address or port number.
 If you want to install UCP in a high-availability configuration that uses
 a load balancer in front of your UCP controllers, include the appropriate IP
 address and FQDN of the load balancer's VIP by using
-one or more `--san` flags in the [install command](/reference/ucp/3.0/cli/install.md)
+one or more `--san` flags in the 
+[UCP install command](/reference/ucp/{{ site.ucp_version }}/cli/install/)
 or when you're asked for additional SANs in interactive mode.
 [Learn about high availability](../configure/set-up-high-availability.md).
 
diff --git a/network/index.md b/network/index.md
index be083b2652..c0c660557b 100644
--- a/network/index.md
+++ b/network/index.md
@@ -100,12 +100,12 @@ exist by default, and provide core networking functionality:
 The following two features are only possible when using Docker EE and managing
 your Docker services using Universal Control Plane (UCP):
 
-- The [HTTP routing mesh](/datacenter/ucp/2.2/guides/admin/configure/use-domain-names-to-access-services/)
+- The [HTTP routing mesh](/ee/ucp/interlock)
   allows you to share the same network IP address and port among multiple
   services. UCP routes the traffic to the appropriate service using the
   combination of hostname and port, as requested from the client.
 
-- [Session stickiness](/datacenter/ucp/2.2/guides/user/services/use-domain-names-to-access-services/#sticky-sessions) allows you to specify information in the HTTP header
+- [Session stickiness](/ee/ucp/interlock/usage/sessions/) allows you to specify information in the HTTP header
   which UCP uses to route subsequent requests to the same service task, for
   applications which require stateful sessions.