diff --git a/source/includes/fact-unique-replica-set-names.rst b/source/includes/fact-unique-replica-set-names.rst
index cf2b682a1c4..0b078cd4dfb 100644
--- a/source/includes/fact-unique-replica-set-names.rst
+++ b/source/includes/fact-unique-replica-set-names.rst
@@ -1,3 +1,3 @@
-If your application connects to more than one replica set, each set
-should have a distinct name. Some drivers group replica set
-connections by replica set name.
+If your application connects to more than one replica set, each set must
+have a distinct name. Some drivers group replica set connections by 
+replica set name.
\ No newline at end of file
diff --git a/source/includes/steps-deploy-replica-set.yaml b/source/includes/steps-deploy-replica-set.yaml
index 2537b107ffd..4db80bc1ab1 100644
--- a/source/includes/steps-deploy-replica-set.yaml
+++ b/source/includes/steps-deploy-replica-set.yaml
@@ -10,12 +10,12 @@ content: |
    For each member, start a :binary:`~bin.mongod` instance with the
    following settings:
 
-   - Set :setting:`replication.replSetName` option to the replica set name,
-
-     .. include:: /includes/fact-unique-replica-set-names.rst
+   - Set :setting:`replication.replSetName` option to the replica set 
+     name. If your application connects to more than one replica set, 
+     each set must have a distinct name.
 
    - Set :setting:`net.bindIp` option to the hostname/ip or a comma-delimited
-     list of hostnames/ips, and
+     list of hostnames/ips.
 
    - Set any other settings as appropriate for your deployment.