DOC-5045 RS: Fixing 7.4 relrefs

Author: rrelledge

content/operate/rs/7.4/databases/configure/proxy-policy.md

@@ -138,7 +138,7 @@ When the network on a single active proxy becomes the bottleneck,
 you might also look into enabling the multiple NIC support in RS. With
 nodes that have multiple physical NICs (Network Interface Cards), you
 can configure RS to separate internal and external traffic onto
-independent physical NICs. For more details, refer to [Manage IP addresses]({{< relref "/operate/rs/7.4/networking/multi-ip-ipv6" >}}).
+independent physical NICs. For more details, refer to [Manage IP addresses]({{< relref "/operate/rs/networking/multi-ip-ipv6" >}}).
 {{< /note >}}
 
 Having multiple proxies for a database can improve RS's ability for fast

content/operate/rs/7.4/networking/mdns.md

@@ -47,7 +47,7 @@ To prepare a client or node for mDNS:
         $ service avahi-daemon start
         ```
 
-1. If you are using [mDNS with IPv6 addresses]({{< relref "/operate/rs/7.4/networking/multi-ip-ipv6" >}}),
+1. If you are using [mDNS with IPv6 addresses]({{< relref "/operate/rs/networking/multi-ip-ipv6" >}}),
     update the hosts line in `/etc/nsswitch.conf` to:
 
     ```yaml

content/operate/rs/7.4/networking/private-public-endpoints.md

@@ -11,7 +11,7 @@ title: "Enable private and\_public database endpoints"
 weight: $weight
 url: '/operate/rs/7.4/networking/private-public-endpoints/'
 ---
-Each node in Redis Enterprise can be configured with [private and external IP addresses]({{< relref "/operate/rs/7.4/networking/multi-ip-ipv6" >}}). By default, Redis Enterprise Software databases expose a single endpoint, e.g. cluster.com (FQDN), using the external IP addresses, making it available to the public network (e.g. the internet). Additionally, the cluster can be configured to expose a private FQDN, which utilizes the private IP addresses for access from the private network only (e.g. VPC or an internal network).
+Each node in Redis Enterprise can be configured with [private and external IP addresses]({{< relref "/operate/rs/networking/multi-ip-ipv6" >}}). By default, Redis Enterprise Software databases expose a single endpoint, e.g. cluster.com (FQDN), using the external IP addresses, making it available to the public network (e.g. the internet). Additionally, the cluster can be configured to expose a private FQDN, which utilizes the private IP addresses for access from the private network only (e.g. VPC or an internal network).
 
 When you create a cluster via the UI, you can configure it to expose private and public endpoints.
 This is common for environments such as cloud platforms and enterprises.

content/operate/rs/7.4/references/cli-utilities/rladmin/node/addr.md

@@ -13,7 +13,7 @@ weight: $weight
 url: '/operate/rs/7.4/references/cli-utilities/rladmin/node/addr/'
 ---
 
-Sets the internal IP address of a node. You can only set the internal IP address when the node is down. See [Change internal IP address]({{< relref "/operate/rs/7.4/networking/multi-ip-ipv6#change-internal-ip-address" >}}) for detailed instructions.
+Sets the internal IP address of a node. You can only set the internal IP address when the node is down. See [Change internal IP address]({{< relref "/operate/rs/networking/multi-ip-ipv6#change-internal-ip-address" >}}) for detailed instructions.
 
 ```sh
 rladmin node <ID> addr set <IP address>