teleletry: fix format (#12915)

content/en/docs/tasks/observability/logs/telemetry-api/index.md

@@ -14,114 +14,114 @@ Previously users had to configure telemetry in the `MeshConfig` section of Istio
 
 1. Enable access logging
 
-{{< text bash >}}
-$ cat <<EOF | kubectl apply -n default -f -
-apiVersion: telemetry.istio.io/v1alpha1
-kind: Telemetry
-metadata:
-name: mesh-logging-default
-namespace: istio-system
-spec:
-  accessLogging:
-  - providers:
-    - name: envoy
-EOF
-{{< /text >}}
+    {{< text bash >}}
+    $ cat <<EOF | kubectl apply -n default -f -
+    apiVersion: telemetry.istio.io/v1alpha1
+    kind: Telemetry
+    metadata:
+      name: mesh-logging-default
+      namespace: istio-system
+    spec:
+      accessLogging:
+      - providers:
+        - name: envoy
+    EOF
+    {{< /text >}}
 
-The above example uses the built-in `envoy` access log provider, and we do not configure anything other than default settings.
+    The above example uses the built-in `envoy` access log provider, and we do not configure anything other than default settings.
 
 1. Disable access log for specific workload
 
-You can disable access log for `details` service with the following configuration:
+    You can disable access log for `details` service with the following configuration:
 
-{{< text bash >}}
-$ cat <<EOF | kubectl apply -n default -f -
-apiVersion: telemetry.istio.io/v1alpha1
-kind: Telemetry
-metadata:
-name: disable-details-logging
-namespace: istio-system
-spec:
-  selector:
-    matchLabels:
-      app: details
-  accessLogging:
-  - providers:
-    - name: envoy
-    disabled: true
-EOF
-{{< /text >}}
+    {{< text bash >}}
+    $ cat <<EOF | kubectl apply -n default -f -
+    apiVersion: telemetry.istio.io/v1alpha1
+    kind: Telemetry
+    metadata:
+      name: disable-details-logging
+      namespace: istio-system
+    spec:
+      selector:
+        matchLabels:
+          app: details
+      accessLogging:
+      - providers:
+        - name: envoy
+        disabled: true
+    EOF
+    {{< /text >}}
 
 1. Filter access log with workload mode
 
-You can disable inbound access log for `details` service with the following configuration:
+    You can disable inbound access log for `details` service with the following configuration:
 
-{{< text bash >}}
-$ cat <<EOF | kubectl apply -n default -f -
-apiVersion: telemetry.istio.io/v1alpha1
-kind: Telemetry
-metadata:
-name: disable-details-logging
-namespace: istio-system
-spec:
-  selector:
-    matchLabels:
-      app: details
-  accessLogging:
-  - providers:
-    - name: envoy
-    match:
-      mode: SERVER
-    disabled: true
-EOF
-{{< /text >}}
+    {{< text bash >}}
+    $ cat <<EOF | kubectl apply -n default -f -
+    apiVersion: telemetry.istio.io/v1alpha1
+    kind: Telemetry
+    metadata:
+      name: disable-details-logging
+      namespace: istio-system
+    spec:
+      selector:
+        matchLabels:
+          app: details
+      accessLogging:
+      - providers:
+        - name: envoy
+        match:
+          mode: SERVER
+        disabled: true
+    EOF
+    {{< /text >}}
 
 1. Filter access log with CEL expression
 
-The following configuration displays access log only when response code is greater or equal to 500:
+    The following configuration displays access log only when response code is greater or equal to 500:
 
-{{< text bash >}}
-$ cat <<EOF | kubectl apply -n default -f -
-apiVersion: telemetry.istio.io/v1alpha1
-kind: Telemetry
-metadata:
-name: disable-details-logging
-namespace: istio-system
-spec:
-  selector:
-    matchLabels:
-      app: httpbin
-  accessLogging:
-  - providers:
-    - name: envoy
-    filter:
-      expression: response.code >= 500
-EOF
-{{< /text >}}
+    {{< text bash >}}
+    $ cat <<EOF | kubectl apply -n default -f -
+    apiVersion: telemetry.istio.io/v1alpha1
+    kind: Telemetry
+    metadata:
+      name: disable-details-logging
+      namespace: istio-system
+    spec:
+      selector:
+        matchLabels:
+          app: httpbin
+      accessLogging:
+      - providers:
+        - name: envoy
+        filter:
+          expression: response.code >= 500
+    EOF
+    {{< /text >}}
 
 1. Set default filter access log with CEL expression
 
-The following configuration displays access logs only when the response code is greater or equal to 400 or the request went to the BlackHoleCluster or the PassthroughCluster:
-Note: The `xds.cluster_name` is only available with Istio release 1.16.2 and higher
+    The following configuration displays access logs only when the response code is greater or equal to 400 or the request went to the BlackHoleCluster or the PassthroughCluster:
+    Note: The `xds.cluster_name` is only available with Istio release 1.16.2 and higher
 
-{{< text bash >}}
-$ cat <<EOF | kubectl apply -f -
-apiVersion: telemetry.istio.io/v1alpha1
-kind: Telemetry
-metadata:
-name: default-exception-logging
-namespace: istio-system
-spec:
-  accessLogging:
-  - providers:
-    - name: envoy
-    filter:
-      expression: "response.code >= 400 || xds.cluster_name == 'BlackHoleCluster' ||  xds.cluster_name == 'PassthroughCluster' "
+    {{< text bash >}}
+    $ cat <<EOF | kubectl apply -f -
+    apiVersion: telemetry.istio.io/v1alpha1
+    kind: Telemetry
+    metadata:
+      name: default-exception-logging
+      namespace: istio-system
+    spec:
+      accessLogging:
+      - providers:
+        - name: envoy
+        filter:
+          expression: "response.code >= 400 || xds.cluster_name == 'BlackHoleCluster' ||  xds.cluster_name == 'PassthroughCluster' "
 
-EOF
-{{< /text >}}
+    EOF
+    {{< /text >}}
 
-For more information, see [Use expressions for values](/docs/tasks/observability/metrics/customize-metrics/#use-expressions-for-values)
+    For more information, see [Use expressions for values](/docs/tasks/observability/metrics/customize-metrics/#use-expressions-for-values)
 
 ## Work with OpenTelemetry provider