/docs/tasks/security/authentication/mtls-migration/index.md

[SataQiu]

Source File: /docs/tasks/security/authentication/mtls-migration/index.md Diff:

 diff --git a/content/en/docs/tasks/security/authentication/mtls-migration/index.md b/content/en/docs/tasks/security/authentication/mtls-migration/index.md
index 85cc5e904..a613d07f9 100644
--- a/content/en/docs/tasks/security/authentication/mtls-migration/index.md
+++ b/content/en/docs/tasks/security/authentication/mtls-migration/index.md
@@ -71,9 +71,10 @@ down once the migration is done.

     {{< text bash >}}
     $ kubectl get destinationrule --all-namespaces
-    NAMESPACE      NAME              AGE
-    istio-system   istio-policy      25m
-    istio-system   istio-telemetry   25m
+    NAMESPACE      NAME                                 HOST                                             AGE
+    istio-system   istio-multicluster-destinationrule   *.global                                         35s
+    istio-system   istio-policy                         istio-policy.istio-system.svc.cluster.local      35s
+    istio-system   istio-telemetry                      istio-telemetry.istio-system.svc.cluster.local   33s
     {{< /text >}}

 ## Configure clients to send mutual TLS traffic
@@ -111,7 +112,7 @@ You can also specify a subset of the clients' request to use `ISTIO_MUTUAL` mutu
 After verifying it works by checking [Grafana to monitor](/docs/tasks/observability/metrics/using-istio-dashboard/),
 then increase the rollout scope and finally apply to all Istio client services.

-## Lock down to mutual TLS (optional)
+## Lock down to mutual TLS

 After migrating all clients to Istio services, injecting Envoy sidecar, we can lock down the `httpbin.foo` to only accept mutual TLS traffic.