@@ -21,7 +21,7 @@ replica sets as a more sophisticated form of traditional master-slave
21
21
replication. [#master-slave]_ In master-slave replication, a
22
22
:term:`master` node accepts writes while one or more :term:`slave`
23
23
nodes replicate those write operations and thus maintain data sets
24
- identical to the master. In MongoDB terms , the member that accepts write
24
+ identical to the master. In MongoDB deployments , the member that accepts write
25
25
operations is the **primary**, and the replicating members are the
26
26
**secondaries**.
27
27
@@ -59,19 +59,19 @@ variety of ways, as listed here. For details, see
59
59
60
60
You can configure a member as any of the following:
61
61
62
- - Secondary-Only --- This member cannot become primary. See
62
+ - ** Secondary-Only**: These members cannot become primary. See
63
63
:ref:`replica-set-secondary-only-members`.
64
64
65
- - Hidden --- This member is invisible to client applications. See
65
+ - ** Hidden**: These members are invisible to client applications. See
66
66
:ref:`replica-set-hidden-members`.
67
67
68
- - Delayed --- This member applies operations from the primary's :term:`oplog` with
68
+ - ** Delayed**: These members apply operations from the primary's :term:`oplog` with
69
69
a specified delay. See :ref:`replica-set-delayed-members`.
70
70
71
- - Arbiters --- This member does not hold data and exists solely to
71
+ - ** Arbiters**: These members do not hold data and exist solely to
72
72
participate in :term:`elections <election>`. See :ref:`replica-set-arbiters`.
73
73
74
- - Non-Voting --- This member cannot vote in elections. See
74
+ - ** Non-Voting**: These members cannot vote in elections. See
75
75
:ref:`replica-set-non-voting-members`.
76
76
77
77
Failover
0 commit comments