Fix broken links

docs/ops/events/cluster-config-overview.rst

@@ -29,14 +29,14 @@ Listeners and authentication
 ============================
 
 The cluster has an internal listener on port ``9093``, which supports mutual TLS authentication between the client and brokers.
-See `Creating a Kafka user with mutual TLS authentication <https://strimzi.io/docs/operators/latest/configuring.html#con-securing-client-authentication-str>`_ for details on how create a ``KafkaUser`` resource and use the corresponding Kubernetes ``Secret`` resource with client TLS certificates.
+See `Creating a Kafka user with mutual TLS authentication <https://strimzi.io/docs/operators/latest/deploying#con-securing-client-authentication-str>`_ for details on how create a ``KafkaUser`` resource and use the corresponding Kubernetes ``Secret`` resource with client TLS certificates.
 
 Authorization
 =============
 
 Authorization is enabled for this cluster.
 This means that that Kafka clients need a corresponding ``KafkaUser`` resource with corresponding access permissions.
-See the `Strimzi Authorization documentation <https://strimzi.io/docs/operators/latest/configuring.html#assembly-securing-kafka-clients-str>`_ for more information.
+See the `Strimzi Authorization documentation <https://strimzi.io/docs/operators/latest/deploying#con-securing-client-authorization-str>`_ for more information.
 
 Kafka configuration
 ===================

docs/ops/gke/gke-cluster-setup.rst

@@ -32,7 +32,7 @@ See the `Stackdriver Kubernetes Engine Monitoring <https://cloud.google.com/stac
 Istio
 =====
 
-At this time the `Istio on GKE <https://cloud.google.com/istio/docs/istio-on-gke>`_ is **disabled**.
+At this time the `Anthos Service Mesh <https://cloud.google.com/service-mesh/docs>`_ is **disabled**.
 We trialled Istio early in the Roundtable deployment, and decided to focus on more traditional ingress and continuous deployment in the initial phase.
 As Roundtable matures, we may revisit using a service mesh on Roundtable.