Fix small errors

doc/Contributing.md

@@ -34,7 +34,7 @@ A readability reviewer ensures that the reviewee is writing idiomatic code and f
 While there's no Go style guide, there is a set of recommendations in the Go community which add up to an implicit style guide.
 To make sure you're writing idiomatic Go code, please read the following documents:
 
-* Go Readablity slides: https://talks.golang.org/2014/readability.slide
+* Go Readability slides: https://talks.golang.org/2014/readability.slide
   * Talk about Go readability with many specific examples.
 * "Effective Go": https://golang.org/doc/effective_go.html
   * Recommendations for writing good Go code.

doc/DesignDocs.md

@@ -2,4 +2,4 @@ The pages below this navigation entry "Design Docs" represent the design conside
 that went behind some of the features implemented. They may not be necessarily up-to-date.
 
 Also, some of the ideas here may just be experimental proposals, and it's possible
-that such ideas might have been abandonned or not implemented yet.
+that such ideas might have been abandoned or not implemented yet.

doc/HorizontalReshardingWorkflowGuide.md

@@ -142,7 +142,7 @@ workflow.
 A "Retry" button will be enabled under the task node if the task failed (click
 the task node if your job get stuck but don't see the Retry button). Click this
 button if you have fixed the bugs and want to retry the failed task. You can
-retry as many times as you want if the task continuelly failed. The workflow
+retry as many times as you want if the task continually failed. The workflow
 can continue from your failure point once it is fixed.
 
 For example, you might forget to bring up a vtworker process. The task which

doc/SeparatingVttabletMysql.md

@@ -26,7 +26,7 @@ The following adjustments need to be made to VTTablet command line parameters:
 
 * Disable restores / backups, by not passing any backup command line
   parameters. Specifically, `-restore_from_backup` and
-  `-backup_storage_implementation` shoud not be set.
+  `-backup_storage_implementation` should not be set.
 
 Since master management and replication are not handled by Vitess, we just need
 to make sure the tablet type in the topology is correct before running

doc/Upgrading.md

@@ -26,7 +26,7 @@ Please use this upgrade order (unless otherwise noted in the release notes):
 - vtgate
 - application code which links client libraries
 
-*vtctld* is listed first to make sure that you can still adminstrate Vitess - or if not find out as soon as possible.
+*vtctld* is listed first to make sure that you can still administrate Vitess - or if not find out as soon as possible.
 
 ## Canary Testing
 

proto/query.proto

@@ -296,7 +296,7 @@ message ExecuteOptions {
 
   TransactionIsolation transaction_isolation = 9;
 
-  // skip_query_plan_cache specifies if the query plan shoud be cached by vitess.
+  // skip_query_plan_cache specifies if the query plan should be cached by vitess.
   // By default all query plans are cached.
   bool skip_query_plan_cache = 10;
 }

test/initial_sharding.py

@@ -631,7 +631,7 @@ def test_resharding(self):
     utils.run_vtctl(['DeleteTablet', '-allow_master',
                      shard_master.tablet_alias], auto_log=True)
 
-    # rebuild the serving graph, all mentions of the old shards shoud be gone
+    # rebuild the serving graph, all mentions of the old shards should be gone
     utils.run_vtctl(['RebuildKeyspaceGraph', 'test_keyspace'], auto_log=True)
 
     # delete the original shard

test/legacy_resharding.py

@@ -622,7 +622,7 @@ def test_resharding(self):
     utils.run_vtctl(['DeleteTablet', '-allow_master',
                      shard_1_master.tablet_alias], auto_log=True)
 
-    # rebuild the serving graph, all mentions of the old shards shoud be gone
+    # rebuild the serving graph, all mentions of the old shards should be gone
     utils.run_vtctl(
         ['RebuildKeyspaceGraph', 'test_keyspace'], auto_log=True)
 

test/merge_sharding.py

@@ -452,7 +452,7 @@ def test_merge_sharding(self):
     utils.run_vtctl(['DeleteShard', 'test_keyspace/-40'], auto_log=True)
     utils.run_vtctl(['DeleteShard', 'test_keyspace/40-80'], auto_log=True)
 
-    # rebuild the serving graph, all mentions of the old shards shoud be gone
+    # rebuild the serving graph, all mentions of the old shards should be gone
     utils.run_vtctl(['RebuildKeyspaceGraph', 'test_keyspace'], auto_log=True)
 
     # kill everything else

test/resharding.py

@@ -1214,7 +1214,7 @@ def test_resharding(self):
     utils.run_vtctl(['DeleteTablet', '-allow_master',
                      shard_1_master.tablet_alias], auto_log=True)
 
-    # rebuild the serving graph, all mentions of the old shards shoud be gone
+    # rebuild the serving graph, all mentions of the old shards should be gone
     utils.run_vtctl(
         ['RebuildKeyspaceGraph', 'test_keyspace'], auto_log=True)