Fix some spelling errors

mesh/v1alpha1/config.proto

@@ -238,7 +238,7 @@ message MeshConfig {
   // The default service dependency setting associated with every workload
   // in the mesh.  Pilot will program the routes in the sidecars and
   // gateways accordingly. If omitted, sidecars will be configured to reach
-  // every service in the mesh. The default scope can be overriden by
+  // every service in the mesh. The default scope can be overridden by
   // supplying a ServiceDependency resource per namespace.
   DefaultServiceDependency default_service_dependency = 29;
 

mesh/v1alpha1/istio.mesh.v1alpha1.pb.html

@@ -312,7 +312,7 @@ <h2 id="MeshConfig">MeshConfig</h2>
 <p>The default service dependency setting associated with every workload
 in the mesh.  Pilot will program the routes in the sidecars and
 gateways accordingly. If omitted, sidecars will be configured to reach
-every service in the mesh. The default scope can be overriden by
+every service in the mesh. The default scope can be overridden by
 supplying a ServiceDependency resource per namespace.</p>
 
 </td>
@@ -656,7 +656,7 @@ <h2 id="Network-NetworkEndpoints">Network.NetworkEndpoints</h2>
 </ol>
 
 <p>a. By matching the registry name with one of the &ldquo;from<em>registries&rdquo;
-   in the mesh config. A &ldquo;from</em>registry&rdquo; can only be assinged to a
+   in the mesh config. A &ldquo;from</em>registry&rdquo; can only be assigned to a
    single network.</p>
 
 <p>b. By matching the IP against one of the CIDR ranges in a mesh

mesh/v1alpha1/network.proto

@@ -36,7 +36,7 @@ message Network {
   // 2. Explicitly:
   //
   //    a. By matching the registry name with one of the "from_registries"
-  //    in the mesh config. A "from_registry" can only be assinged to a
+  //    in the mesh config. A "from_registry" can only be assigned to a
   //    single network.
   //
   //    b. By matching the IP against one of the CIDR ranges in a mesh