Skip to content

Improve readability #866

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
wants to merge 1 commit into from
Closed
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 3 additions & 3 deletions source/tutorial/manage-sharded-cluster-config-server.txt
Original file line number Diff line number Diff line change
Expand Up @@ -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
Expand Down