diff --git a/source/includes/downgrade-path.rst b/source/includes/downgrade-path.rst
index 890a144aa05..a23a81e1b10 100644
--- a/source/includes/downgrade-path.rst
+++ b/source/includes/downgrade-path.rst
@@ -1 +1,3 @@
+.. include:: /includes/upgrade-downgrade-replica-set.rst
+
 Once upgraded to |newversion|, if you need to downgrade, we recommend |downgrading| to the latest patch release of |downgradeversion|.
diff --git a/source/includes/upgrade-downgrade-replica-set.rst b/source/includes/upgrade-downgrade-replica-set.rst
new file mode 100644
index 00000000000..4fe8e76ff67
--- /dev/null
+++ b/source/includes/upgrade-downgrade-replica-set.rst
@@ -0,0 +1,5 @@
+.. important::
+
+   Before you upgrade or downgrade a replica set, ensure all replica set
+   members are running. If you do not, the upgrade or downgrade will not
+   complete until all members are started.
\ No newline at end of file
diff --git a/source/tutorial/upgrade-revision.txt b/source/tutorial/upgrade-revision.txt
index 642906a3459..b5a65b1641f 100644
--- a/source/tutorial/upgrade-revision.txt
+++ b/source/tutorial/upgrade-revision.txt
@@ -173,6 +173,8 @@ To upgrade a replica set, upgrade each member individually, starting with
 the :term:`secondaries <secondary>` and finishing with the
 :term:`primary`. Plan the upgrade during a predefined maintenance window.
 
+.. include:: /includes/upgrade-downgrade-replica-set.rst
+
 .. note::
 
    Starting in MongoDB 4.0.7, change streams use a version 1 ``v1``