Skip to content

Commit 567aa9d

Browse files
committed
Fixing some typos
1 parent f3f0270 commit 567aa9d

File tree

1 file changed

+3
-3
lines changed

1 file changed

+3
-3
lines changed

source/tutorial/deploy-replica-set.txt

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -21,14 +21,14 @@ system failures. A replica set of this size provides sufficient
2121
capacity to host many distributed read operations. While MongoDB's
2222
replica set functionality provides a great deal of flexibility and
2323
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.
2525

2626
Requirements
2727
------------
2828

2929
Three distinct systems, so that each system can run its own instance
3030
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
3232
within a virtual instance. For production environments, you should
3333
endeavor to maintain as much separation between the nodes: Deploy
3434
replica set members on distinct hardware, and on systems that draw
@@ -72,7 +72,7 @@ following options for more information: :option:`--port <mongod --port>`,
7272

7373
If you're running each :program:`mongod` instance on a distinct
7474
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
7676
<mongod --bind_ip>` option.
7777

7878
Log in with the :program:`mongo` shell to the first host. If you're

0 commit comments

Comments
 (0)