@@ -21,14 +21,14 @@ system failures. A replica set of this size provides sufficient
21
21
capacity to host many distributed read operations. While MongoDB's
22
22
replica set functionality provides a great deal of flexibility and
23
23
specific definable node behaviors or types, it's best to avoid this
24
- additional complexity your application requires the functionality.
24
+ additional complexity until your application requires the functionality.
25
25
26
26
Requirements
27
27
------------
28
28
29
29
Three distinct systems, so that each system can run its own instance
30
30
of :program:`mongod`. For test systems you can run all three instances
31
- of the :program:`mongod` process on a local sys em.e . a laptop) or
31
+ of the :program:`mongod` process on a local system. e.g . a laptop) or
32
32
within a virtual instance. For production environments, you should
33
33
endeavor to maintain as much separation between the nodes: Deploy
34
34
replica set members on distinct hardware, and on systems that draw
@@ -72,7 +72,7 @@ following options for more information: :option:`--port <mongod --port>`,
72
72
73
73
If you're running each :program:`mongod` instance on a distinct
74
74
system, you can omit the :option:`--port <mongod --port>`
75
- option. YOu will also need to specify the :option:`--bind_ip
75
+ option. You will also need to specify the :option:`--bind_ip
76
76
<mongod --bind_ip>` option.
77
77
78
78
Log in with the :program:`mongo` shell to the first host. If you're
0 commit comments