From 777ad0b8938b08feedb6c5f253d9e20b6ea7303c Mon Sep 17 00:00:00 2001 From: Jake Angerman Date: Thu, 28 Aug 2014 09:24:44 -0500 Subject: [PATCH] Update deploy-replica-set-with-auth.txt typo fix --- source/tutorial/deploy-replica-set-with-auth.txt | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/source/tutorial/deploy-replica-set-with-auth.txt b/source/tutorial/deploy-replica-set-with-auth.txt index fe0850e4ac1..8495616288e 100644 --- a/source/tutorial/deploy-replica-set-with-auth.txt +++ b/source/tutorial/deploy-replica-set-with-auth.txt @@ -16,7 +16,7 @@ key part of a complete security strategy. All MongoDB deployments support authentication. By default, MongoDB does not require authorization checking. You can enforce authorization -checking when deploying MongoDB, or on an existing deploying; however, +checking when deploying MongoDB, or on an existing deployment; however, you cannot enable authorization checking on a running deployment without downtime.