Minor improvements to locality LB tasks (#8570)

content/en/docs/setup/install/multicluster/_index.md

@@ -2,7 +2,6 @@
 title: Install Multicluster
 description: Install an Istio mesh across multiple Kubernetes clusters.
 weight: 40
-icon: setup
 aliases:
     - /docs/setup/kubernetes/multicluster-install/
     - /docs/setup/kubernetes/multicluster/

content/en/docs/tasks/traffic-management/locality-load-balancing/_index.md

@@ -2,7 +2,6 @@
 title: Locality Load Balancing
 description: This series of tasks demonstrate how to configure locality load balancing in Istio.
 weight: 65
-icon: tasks
 keywords: [locality,load balancing,priority,prioritized,kubernetes,multicluster]
 simple_list: true
 content_above: true
@@ -11,7 +10,7 @@ aliases:
   - /help/ops/locality-load-balancing
   - /help/tasks/traffic-management/locality-load-balancing
   - /docs/ops/traffic-management/locality-load-balancing
-  - /docs/tasks/traffic-management/locality-load-balancing
+  - /docs/ops/configuration/traffic-management/locality-load-balancing
 owner: istio/wg-networking-maintainers
 test: n/a
 ---

content/en/docs/tasks/traffic-management/locality-load-balancing/before-you-begin/index.md

@@ -7,7 +7,7 @@ keywords: [locality,load balancing,priority,prioritized,kubernetes,multicluster]
 test: yes
 owner: istio/wg-networking-maintainers
 ---
-Before you begin tasks for locality load balancing, you must first
+Before you begin the locality load balancing tasks, you must first
 [install Istio on multiple clusters](/docs/setup/install/multicluster). The
 clusters must span three regions, containing four availability zones. The
 number of clusters required may vary based on the capabilities offered by

content/en/docs/tasks/traffic-management/locality-load-balancing/distribute/test.sh

@@ -95,8 +95,6 @@ configureDistribution
 verifyDistribution
 
 # @cleanup
-set +e # ignore cleanup errors
-
 source content/en/docs/tasks/traffic-management/locality-load-balancing/common.sh
 
 set_env_vars

content/en/docs/tasks/traffic-management/locality-load-balancing/failover/index.md

@@ -98,8 +98,9 @@ Repeat this several times and verify that the response is always the same.
 
 ## Failover to `region1.zone2`
 
-Next, trigger a failover to `region1.zone2`. To do this, you drain the
-the Envoy sidecar proxy for `HelloWorld` in `region1.zone1`:
+Next, trigger a failover to `region1.zone2`. To do this, you
+[drain the Envoy sidecar proxy](https://www.envoyproxy.io/docs/envoy/latest/intro/arch_overview/operations/draining#draining)
+for `HelloWorld` in `region1.zone1`:
 
 {{< text bash >}}
 $ kubectl --context="${CTX_R1_Z1}" exec \

content/en/docs/tasks/traffic-management/locality-load-balancing/failover/test.sh

@@ -71,8 +71,6 @@ failover_to_region2_zone3
 failover_to_region3_zone4
 
 # @cleanup
-set +e # ignore cleanup errors
-
 source content/en/docs/tasks/traffic-management/locality-load-balancing/common.sh
 
 set_env_vars