Automator: update istio.io@ reference docs (#15902)

content/en/docs/reference/config/annotations/index.html

@@ -422,28 +422,6 @@ If that backend becomes unhealthy, traffic will sent to <code>us-east</code>.</l
     </tr>
   </tbody>
 </table>
-<h2 id="SidecarEnableCoreDump">sidecar.istio.io/enableCoreDump</h2>
-<table class="annotations">
-  <tbody>
-    <tr>
-      <th>Name</th>
-      <td><code>sidecar.istio.io/enableCoreDump</code></td>
-    </tr>
-    <tr>
-      <th>Feature Status</th>
-      <td>Alpha</td>
-    </tr>
-    <tr>
-      <th>Resource Types</th>
-      <td>[Pod]</td>
-    </tr>
-    <tr>
-      <th>Description</th>
-      <td><p>Specifies whether or not an Envoy sidecar should enable core dump.</p>
-</td>
-    </tr>
-  </tbody>
-</table>
 <h2 id="SidecarExtraStatTags">sidecar.istio.io/extraStatTags</h2>
 <table class="annotations">
   <tbody>

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

@@ -2764,7 +2764,7 @@ No
 <td><code><a href="#MeshConfig-ExtensionProvider-HttpHeader">HttpHeader[]</a></code></td>
 <td>
 <p>Optional. Additional metadata to include in streams initiated to the GrpcService. This can be used for
-scenarios in which additional ad hoc authorization headers (e.g. "x-foo-bar: baz-key") are to
+scenarios in which additional ad hoc authorization headers (e.g. &ldquo;x-foo-bar: baz-key&rdquo;) are to
 be injected.</p>
 
 </td>

content/zh/docs/reference/config/annotations/index.html

@@ -422,28 +422,6 @@ If that backend becomes unhealthy, traffic will sent to <code>us-east</code>.</l
     </tr>
   </tbody>
 </table>
-<h2 id="SidecarEnableCoreDump">sidecar.istio.io/enableCoreDump</h2>
-<table class="annotations">
-  <tbody>
-    <tr>
-      <th>Name</th>
-      <td><code>sidecar.istio.io/enableCoreDump</code></td>
-    </tr>
-    <tr>
-      <th>Feature Status</th>
-      <td>Alpha</td>
-    </tr>
-    <tr>
-      <th>Resource Types</th>
-      <td>[Pod]</td>
-    </tr>
-    <tr>
-      <th>Description</th>
-      <td><p>Specifies whether or not an Envoy sidecar should enable core dump.</p>
-</td>
-    </tr>
-  </tbody>
-</table>
 <h2 id="SidecarExtraStatTags">sidecar.istio.io/extraStatTags</h2>
 <table class="annotations">
   <tbody>

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

@@ -2764,7 +2764,7 @@ No
 <td><code><a href="#MeshConfig-ExtensionProvider-HttpHeader">HttpHeader[]</a></code></td>
 <td>
 <p>Optional. Additional metadata to include in streams initiated to the GrpcService. This can be used for
-scenarios in which additional ad hoc authorization headers (e.g. “x-foo-bar: baz-key“) are to
+scenarios in which additional ad hoc authorization headers (e.g. &ldquo;x-foo-bar: baz-key&rdquo;) are to
 be injected.</p>
 
 </td>

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

@@ -23,7 +23,7 @@ This configuration scoping, among <a href="/zh/docs/ops/configuration/mesh/confi
 out unneeded configuration, to improve scalability of the mesh.
 A common misunderstanding is that restricting the configuration amounts to <em>blocking</em> the traffic.
 If requests are sent to destinations not included in the scoping, the traffic will be treated as
-<a href="docs/ops/configuration/traffic-management/traffic-routing/#unmatched-traffic">unmatched traffic</a>, which is often still allowed.
+<a href="/zh/docs/ops/configuration/traffic-management/traffic-routing/#unmatched-traffic">unmatched traffic</a>, which is often still allowed.
 The sidecar is not able to enforce an outbound traffic restriction (see <a href="/zh/docs/tasks/traffic-management/egress/egress-gateway/">Egress Gateways</a> for how to achieve this).</p>
 <p>Services and configuration in a mesh are organized into one or more
 namespaces (e.g., a Kubernetes namespace or a CF org/space). A <code>Sidecar</code>