From 4c2d965f325ab7bf7f95532d38acf6573c636b6d Mon Sep 17 00:00:00 2001 From: Jake Angerman Date: Tue, 12 Aug 2014 23:12:22 -0500 Subject: [PATCH] Update master-slave.txt typo fixes --- source/core/master-slave.txt | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/source/core/master-slave.txt b/source/core/master-slave.txt index 79668a73043..3af71e7e146 100644 --- a/source/core/master-slave.txt +++ b/source/core/master-slave.txt @@ -111,7 +111,7 @@ with a master if: - The slave stops (i.e. shuts down) and restarts later after the master has overwritten the relevant operations from the master. -When slaves, are out of sync, replication stops. Administrators must +When slaves are out of sync, replication stops. Administrators must intervene manually to restart replication. Use the :dbcommand:`resync` command. Alternatively, the :option:`--autoresync ` allows a slave to restart replication automatically, @@ -250,7 +250,7 @@ Convert a Master-Slave Deployment to a Replica Set To convert a master-slave deployment to a replica set, restart the current master as a one-member replica set. Then remove the data -directors from previous secondaries and add them as new secondaries to +directories from previous secondaries and add them as new secondaries to the new replica set. 1. To confirm that the current instance is master, run: