From 62b36d1f51e47960c4862e628ff0fe78cc4fb144 Mon Sep 17 00:00:00 2001 From: Jake Angerman Date: Thu, 17 Apr 2014 09:48:59 -0500 Subject: [PATCH] Update reconfigure-replica-set-with-unavailable-members.txt typo fix --- .../reconfigure-replica-set-with-unavailable-members.txt | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/source/tutorial/reconfigure-replica-set-with-unavailable-members.txt b/source/tutorial/reconfigure-replica-set-with-unavailable-members.txt index 81dae54a207..31c5e537afe 100644 --- a/source/tutorial/reconfigure-replica-set-with-unavailable-members.txt +++ b/source/tutorial/reconfigure-replica-set-with-unavailable-members.txt @@ -34,7 +34,7 @@ This procedure lets you recover while a majority of :term:`replica set` members are down or unreachable. You connect to any surviving member and use the ``force`` option to the :method:`rs.reconfig()` method. -The ``force`` option forces a new configuration onto the. Use this procedure only to +The ``force`` option forces a new configuration onto the member. Use this procedure only to recover from catastrophic interruptions. Do not use ``force`` every time you reconfigure. Also, do not use the ``force`` option in any automatic scripts and do not use ``force`` when there is still a :term:`primary`.