Merge pull request #114 from dragorosson/master

Proof MongoDB readme

mongodb/README.md

@@ -38,11 +38,11 @@ recommended number of slave servers are 3.
 
 ![Alt text](images/sharding.png "Sharding")
 
-Sharding works by partioning the data into seperate chunks and allocating
+Sharding works by partitioning the data into seperate chunks and allocating
 diffent ranges of chunks to diffrent shard servers. The figure above shows a
 collection which has 90 documents which have been sharded across the three
-server: the first shard getting ranges from 1-29,  and so on. When a client wants
-to access a certian document it contacts the query router (mongos process),
+servers: the first shard getting ranges from 1-29, and so on. When a client wants
+to access a certain document, it contacts the query router (mongos process),
 which in turn contacts the 'configuration node', a lightweight mongod
 process) that keeps a record of which ranges of chunks are distributed across
 which shards. 
@@ -128,8 +128,8 @@ Build the site with the following command:
 ---------------------------------------------
 
 Once configuration and deployment has completed we can check replication set
-availibitly by connecting to individual primary replication set nodes, 'mongo
---host 192.168.1.1 --port 2700' and issue the command to query the status of
+availability by connecting to individual primary replication set nodes, `mongo
+--host 192.168.1.1 --port 2700` and issue the command to query the status of
 replication set, we should get a similar output.
 
 		
@@ -150,7 +150,7 @@ replication set, we should get a similar output.
 				"optimeDate" : ISODate("2013-03-19T10:25:55Z"),
 				"self" : true
 			},
-		{
+			{
 				"_id" : 1,
 				"name" : "web3:2013",
 				"health" : 1,
@@ -162,8 +162,8 @@ replication set, we should get a similar output.
 				"lastHeartbeat" : ISODate("2013-03-19T10:26:33Z"),
 				"pingMs" : 1
 			}
-		],
-		"ok" : 1
+			],
+			"ok" : 1
 		}