Jira DOC-564: RS - Clarify how to enable public/private IP support

content/rs/administering/designing-production/networking/private-public-endpoints.md

@@ -1,52 +1,41 @@
 ---
 title: Private and Public Endpoints on Redis Enterprise Software
-description:
+linkTitle: Public and private endpoints
+description: Describes how to enable public and private endpoints for databases on a cluster.
 weight: $weight
 alwaysopen: false
 categories: ["RS"]
 ---
-The cluster can be configured to support both private and public IPs to
-connect to database endpoints through both public and private networks.
+The cluster can be configured to enable both access using private and public networks.
 
 In certain environments, and especially in cloud platforms, an instance
 can have both:
 
-- A private IP address that can be used only from within the internal
-    network
-- Public IP addresses that can be used from the public network
-    (Internet)
+- A private IP address available only within the internal network
 
-In this case, it is possible to configure Redis Enterprise Software to
-expose two sets of database endpoints in order to connect to the
-database through both the private and the public IP addresses.
+- Public IP addresses accessible from the Internet (public network)
+
+By default, Redis Enterprise Software databases expose a single endpoint.
+
+You can configure Redis Enterprise Software clusters to expose two endpoints.
 
 To enable this configuration you need to:
 
-- Make sure that the IPs are already bound to the server/instance.
-- Enable private and public endpoint support when the cluster is created, or
-    use rladmin to enable support for an existing cluster.
-- Configure public IP of the machine to be used for external traffic
-    in the node configuration.
-- Configure private IP to be used for both internal and external
-    traffic in the node configuration so it can be used for private
-    database endpoints.
+- Make sure that the IP addresses are already bound to the server/instance.
 
-Once this configuration is in place, both sets of endpoints are
-available for the databases in the cluster.
+- Select the **Enable private and public endpoint support** setting when creating the cluster.
 
-## Modifying an existing cluster
+    This setting is available when you set up a cluster.  It appears in the **Cluster configuration** section of the **Node configuration** screen.
 
-You can enable it by using the ***rladmin suffix add*** command.
+    {{<image filename="images/rs/node-configuration-endpoint-support.png" alt="The endpoint support setting appears in the **Cluster configuration section** of the **Node configuration** screen." >}}{{< /image >}}
 
-To add an internal FQDN/IP to a cluster:
+    If this setting is not enabled when the cluster is created, databases on the cluster support only a single endpoint.
 
-```sh
-rladmin suffix add name <internal.clustername.domain.com> internal
-```
+- Configure the public IP of the machine to be used for external traffic
+    in the node configuration.
 
-To add an internal FQDN/IP to a cluster, but signal to the cluster there
-is slave for DNS:
+- Configure private IP to be used for both internal and external
+    traffic in the node configuration so it can be used for private
+    database endpoints.
 
-```sh
-rladmin suffix add name <internal.clustername.domain.com> internal slave 10.0.1.1
-```
+When you finish, both sets of endpoints are available for databases in the cluster.