Update reference docs. (#3775)

content/docs/reference/config/istio.mesh.v1alpha1/index.html

@@ -622,12 +622,15 @@ inside a mesh and how to route to endpoints in each network. For example</p>
 
 <p>MeshNetworks(file/config map):
 networks:
-- network1:
+  network1:
   - endpoints:
-    - fromRegistry: registry1 #must match secret name inKubernetes
+    - fromRegistry: registry1 #must match secret name in Kubernetes
     - fromCidr: 192.168.100.0/22 #a VM network for example
     gateways:
     - registryServiceName: istio-ingressgateway.istio-system.svc.cluster.local
+      port: 15443
+      locality: us-east-1a
+    - address: 192.168.100.1
       port: 15443
       locality: us-east-1a</p>
 
@@ -762,8 +765,8 @@ adding the <code>ISTIO_META_NETWORK</code> environment variable to the sidecar.<
 <li><p>Explicitly:</p></li>
 </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 assigned to a
+<p>a. By matching the registry name with one of the &ldquo;fromRegistry&rdquo;
+   in the mesh config. A &ldquo;from_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

content/docs/reference/config/networking/v1alpha3/envoy-filter/index.html

@@ -24,7 +24,7 @@ The behavior is undefined if multiple EnvoyFilter configurations conflict
 with each other.</p>
 
 <p>The following example for Kubernetes enables Envoy&rsquo;s Lua filter for all
-inbound calls arriving at service port 8080 of the reviews service pod with
+inbound HTTP calls arriving at service port 8080 of the reviews service pod with
 labels &ldquo;app: reviews&rdquo;.</p>
 
 <pre><code class="language-yaml">apiVersion: networking.istio.io/v1alpha3
@@ -38,6 +38,7 @@ spec:
   - listenerMatch:
       portNumber: 8080
       listenerType: SIDECAR_INBOUND # will match with the inbound listener for reviews:8080
+      listenerProtocol: HTTP
     filterName: envoy.lua
     filterType: HTTP
     filterConfig:
@@ -65,10 +66,7 @@ proxies should be configured to use these additional filters.  The
 scope of label search is platform dependent. On Kubernetes, for
 example, the scope includes pods running in all reachable
 namespaces. Omitting the selector applies the filter to all proxies in
-the mesh.
-NOTE: There can be only one EnvoyFilter bound to a specific workload.
-The behavior is undefined if multiple EnvoyFilter configurations are
-specified for the same workload.</p>
+the mesh.</p>
 
 </td>
 </tr>
@@ -103,8 +101,11 @@ envoy.http<em>connection</em>manager.</p>
 <td><code>listenerMatch</code></td>
 <td><code><a href="#EnvoyFilter-ListenerMatch">EnvoyFilter.ListenerMatch</a></code></td>
 <td>
-<p>Filter will be added to the listener only if the match conditions are true.
-If not specified, the filters will be applied to all listeners.</p>
+<p>Filter will be added to the listener only if the match
+conditions are true.  If not specified, the filters will be
+applied to all listeners where possible, potentially resulting
+in invalid configurations. It is recommended to specify the
+listener match criteria for all filter insertions.</p>
 
 </td>
 </tr>
@@ -305,11 +306,11 @@ matches all listeners.</p>
 <td><code>listenerProtocol</code></td>
 <td><code><a href="#EnvoyFilter-ListenerMatch-ListenerProtocol">EnvoyFilter.ListenerMatch.ListenerProtocol</a></code></td>
 <td>
-<p>Selects a class of listeners for the same protocol. If not
-specified, applies to listeners on all protocols. Use the protocol
+<p>Selects a class of listeners for the same protocol. Use the protocol
 selection to select all HTTP listeners (includes HTTP2/gRPC/HTTPS
 where Envoy terminates TLS) or all TCP listeners (includes HTTPS
-passthrough using SNI).</p>
+passthrough using SNI). When adding a HTTP filter, the listenerProtocol
+should be set to HTTP.</p>
 
 </td>
 </tr>

content/docs/reference/config/networking/v1alpha3/sidecar/index.html

@@ -382,8 +382,7 @@ connections. Format should be 127.0.0.1:PORT or <code>unix:///path/to/socket</co
 <td>
 <p>Criteria used to select the specific set of pods/VMs on which this
 sidecar configuration should be applied. If omitted, the sidecar
-configuration will be applied to all workloads in the same config
-namespace.</p>
+configuration will be applied to all workloads in the same namespace.</p>
 
 </td>
 </tr>

content/docs/reference/config/networking/v1alpha3/virtual-service/index.html

@@ -736,9 +736,9 @@ spec:
   - match:
     - uri:
         exact: /v1/getProductRatings
-  redirect:
-    uri: /v1/bookRatings
-    authority: newratings.default.svc.cluster.local
+    redirect:
+      uri: /v1/bookRatings
+      authority: newratings.default.svc.cluster.local
   ...
 </code></pre>