diff --git a/source/tutorial/manage-sharded-cluster-config-server.txt b/source/tutorial/manage-sharded-cluster-config-server.txt
index 5500830526a..39f4faf1da5 100644
--- a/source/tutorial/manage-sharded-cluster-config-server.txt
+++ b/source/tutorial/manage-sharded-cluster-config-server.txt
@@ -33,11 +33,11 @@ For redundancy, all production :term:`sharded clusters <sharded cluster>`
 should deploy three config servers processes on three different
 machines.
 
-Do not use only a single config server for production deployments.
-Only use a single config server deployments for testing.  You should
+Do not use a single config server for production deployments.
+Only use single config server deployments for testing.  You should
 upgrade to three config servers immediately if you are shifting to
 production.  The following process shows how to convert a test
-deployment with only one config server to production deployment with
+deployment with only one config server to a production deployment with
 three config servers.
 
 #. Shut down all existing MongoDB processes in the cluster. This