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

content/en/docs/reference/config/networking/destination-rule/index.html

@@ -604,6 +604,9 @@ No
 remains in warmup mode starting from its creation time for the duration of this window and
 Istio progressively increases amount of traffic for that endpoint instead of sending proportional amount of traffic.
 This should be enabled for services that require warm up time to serve full production load with reasonable latency.
+Please note that this is most effective when few new endpoints come up like scale event in Kubernetes. When all the
+endpoints are relatively new like new deployment, this is not very effective as all endpoints end up getting same
+amount of requests.
 Currently this is only supported for ROUND_ROBIN and LEAST_REQUEST load balancers.</p>
 
 </td>

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

@@ -42,6 +42,7 @@ system is undefined if two or more <code>Sidecar</code> configurations with a
 will be applied by default to all namespaces without a <code>Sidecar</code>
 configuration</em></em>. This global default <code>Sidecar</code> configuration should not have
 any <code>workloadSelector</code>.</p>
+<p><strong>NOTE 3</strong>: <em><em>A <code>Sidecar</code> is not applicable to gateways, even though gateways are istio-proxies</em></em>.</p>
 <p>The example below declares a global default <code>Sidecar</code> configuration
 in the root namespace called <code>istio-config</code>, that configures
 sidecars in all namespaces to allow egress traffic only to other

content/zh/docs/reference/config/networking/destination-rule/index.html

@@ -604,6 +604,9 @@ No
 remains in warmup mode starting from its creation time for the duration of this window and
 Istio progressively increases amount of traffic for that endpoint instead of sending proportional amount of traffic.
 This should be enabled for services that require warm up time to serve full production load with reasonable latency.
+Please note that this is most effective when few new endpoints come up like scale event in Kubernetes. When all the
+endpoints are relatively new like new deployment, this is not very effective as all endpoints end up getting same
+amount of requests.
 Currently this is only supported for ROUND_ROBIN and LEAST_REQUEST load balancers.</p>
 
 </td>

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

@@ -42,6 +42,7 @@ system is undefined if two or more <code>Sidecar</code> configurations with a
 will be applied by default to all namespaces without a <code>Sidecar</code>
 configuration</em></em>. This global default <code>Sidecar</code> configuration should not have
 any <code>workloadSelector</code>.</p>
+<p><strong>NOTE 3</strong>: <em><em>A <code>Sidecar</code> is not applicable to gateways, even though gateways are istio-proxies</em></em>.</p>
 <p>The example below declares a global default <code>Sidecar</code> configuration
 in the root namespace called <code>istio-config</code>, that configures
 sidecars in all namespaces to allow egress traffic only to other