From fa7dc773349208c8d31179b4f0624666c222c556 Mon Sep 17 00:00:00 2001
From: ian fogelman <ian.fogelman@mongodb.com>
Date: Tue, 10 Aug 2021 11:46:51 -0400
Subject: [PATCH] DOCSP-17376 Adding context that DWC appies to non-shard
 replcia sets.

---
 .../fact-set-global-write-concern-before-reconfig.rst         | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/source/includes/fact-set-global-write-concern-before-reconfig.rst b/source/includes/fact-set-global-write-concern-before-reconfig.rst
index d5dd545b5c0..4e09a2139b0 100644
--- a/source/includes/fact-set-global-write-concern-before-reconfig.rst
+++ b/source/includes/fact-set-global-write-concern-before-reconfig.rst
@@ -1,6 +1,6 @@
 Starting in MongoDB 5.0, you must explicitly set the global default
 :ref:`write concern <write-concern>` before attempting to reconfigure a
-:term:`replica set <replica set>` with a 
-:doc:`configuration </reference/replica-configuration>` 
+:ref:`non-sharded <sharded-vs-non-sharded-collections>` :term:`replica set <replica set>` with a
+:doc:`configuration </reference/replica-configuration>`
 that would change the implicit default write concern. To set the global
 default write concern, use the :dbcommand:`setDefaultRWConcern` command.