Update sharding.rst (#151)

* Update sharding.rst

Correcting two instances of "to" should be "too".

* Updating sharding.rst (2)

Fixed a third improper use "to" instead of "too".

src/cluster/sharding.rst

@@ -267,10 +267,10 @@ time you move a shard. As this can take quite some time, it is not recommended.
 Reshard? No, Preshard!
 ======================
 
-Reshard? Nope. It can not be done. So do not create databases with to few
+Reshard? Nope. It can not be done. So do not create databases with too few
 shards.
 
-If you can not scale out more because you set the number of shards to low, then
+If you can not scale out more because you set the number of shards too low, then
 you need to create a new cluster and migrate over.
 
 #. Build a cluster with enough nodes to handle one copy of your data.
@@ -291,7 +291,7 @@ you need to create a new cluster and migrate over.
 
 Creating more shards than you need and then move the shards around is called
 presharding. The number of shards you need depends on how much data you are
-going to store. But, creating to many shards increases the complexity without
+going to store. But, creating too many shards increases the complexity without
 any real gain. You might even get lower performance. As an example of this, we
 can take the author's (15 year) old lab server. It gets noticeably slower with
 more than one shard and high load, as the hard drive must seek more.