summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorali-mir <ali.mir@mongodb.com>2021-07-22 14:45:05 +0000
committerEvergreen Agent <no-reply@evergreen.mongodb.com>2021-07-22 15:42:46 +0000
commit491301856f66409cbc57106d785153f40316a44a (patch)
tree4ebf3bed28ae69b4b22b4e34e2c73978bfde60fb
parentfda1dfa7f00600df025b19248605715a6cd47cd8 (diff)
downloadmongo-491301856f66409cbc57106d785153f40316a44a.tar.gz
SERVER-53437 Fix formatting error in default write concern section in replication arch guide
-rw-r--r--src/mongo/db/repl/README.md2
1 files changed, 1 insertions, 1 deletions
diff --git a/src/mongo/db/repl/README.md b/src/mongo/db/repl/README.md
index c86abaff099..4e1edfdf648 100644
--- a/src/mongo/db/repl/README.md
+++ b/src/mongo/db/repl/README.md
@@ -97,7 +97,7 @@ to shards, which means the default write concern on shards will always be consis
cluster. We don't want to specify `{w: "majority"}` for shard replica sets
that can keep a primary due to an arbiter's vote, but lose the ability to acknowledge majority
writes if a majority of data-bearing nodes goes down. So if the result of the DWCF for any replica
-set in the cluster is `{w: 1`}`, we require the cluster to set a CWWC. Once set, we disallow
+set in the cluster is `{w: 1}`, we require the cluster to set a CWWC. Once set, we disallow
unsetting it so we can prevent PSA shards from implicitly defaulting to `{w: "majority"}` for
reasons mentioned above. However, if a user decides to set the CWWC to `{w: "majority"}`
for a PSA set, they may do so. We assume that in this case the user understands