From c8f65e2f8bbfa82adc03e98db5e3d4a1bdc00cca Mon Sep 17 00:00:00 2001
From: Kim Sondrup <kim@sondrup.io>
Date: Tue, 21 May 2024 15:42:29 +0200
Subject: [PATCH] Fix typo in closing tag for some code blocks (#3196)

---
 mesh/v1alpha1/istio.mesh.v1alpha1.pb.html     | 2 +-
 mesh/v1alpha1/proxy.pb.go                     | 2 +-
 mesh/v1alpha1/proxy.proto                     | 2 +-
 security/v1beta1/authorization_policy.pb.go   | 4 ++--
 security/v1beta1/authorization_policy.pb.html | 4 ++--
 security/v1beta1/authorization_policy.proto   | 4 ++--
 6 files changed, 9 insertions(+), 9 deletions(-)

diff --git a/mesh/v1alpha1/istio.mesh.v1alpha1.pb.html b/mesh/v1alpha1/istio.mesh.v1alpha1.pb.html
index b45656cd..28e636f0 100644
--- a/mesh/v1alpha1/istio.mesh.v1alpha1.pb.html
+++ b/mesh/v1alpha1/istio.mesh.v1alpha1.pb.html
@@ -4011,7 +4011,7 @@ No
 <td><code>envoyDebugHeaders</code></td>
 <td><code><a href="#ProxyConfig-ProxyHeaders-EnvoyDebugHeaders">EnvoyDebugHeaders</a></code></td>
 <td>
-<p>Controls various <code>X-Envoy-*</code> headers, such as <code>X-Envoy-Overloaded</code> and `X-Envoy-Upstream-Service-Time. If enabled,
+<p>Controls various <code>X-Envoy-*</code> headers, such as <code>X-Envoy-Overloaded</code> and <code>X-Envoy-Upstream-Service-Time</code>. If enabled,
 these headers will be included.
 If disabled, these headers will not be set. If they are already present, they will be preserved.
 See the <a href="https://www.envoyproxy.io/docs/envoy/latest/api-v3/extensions/filters/http/router/v3/router.proto#envoy-v3-api-field-extensions-filters-http-router-v3-router-suppress-envoy-headers">Envoy documentation</a> for more details.
diff --git a/mesh/v1alpha1/proxy.pb.go b/mesh/v1alpha1/proxy.pb.go
index 4de34ff7..8f48067e 100644
--- a/mesh/v1alpha1/proxy.pb.go
+++ b/mesh/v1alpha1/proxy.pb.go
@@ -2289,7 +2289,7 @@ type ProxyConfig_ProxyHeaders struct {
 	// If disabled, this header will not be set. If it is already present, it will be preserved.
 	// This header is enabled by default if not configured.
 	AttemptCount *ProxyConfig_ProxyHeaders_AttemptCount `protobuf:"bytes,4,opt,name=attempt_count,json=attemptCount,proto3" json:"attempt_count,omitempty"`
-	// Controls various `X-Envoy-*` headers, such as `X-Envoy-Overloaded` and `X-Envoy-Upstream-Service-Time. If enabled,
+	// Controls various `X-Envoy-*` headers, such as `X-Envoy-Overloaded` and `X-Envoy-Upstream-Service-Time`. If enabled,
 	// these headers will be included.
 	// If disabled, these headers will not be set. If they are already present, they will be preserved.
 	// See the [Envoy documentation](https://www.envoyproxy.io/docs/envoy/latest/api-v3/extensions/filters/http/router/v3/router.proto#envoy-v3-api-field-extensions-filters-http-router-v3-router-suppress-envoy-headers) for more details.
diff --git a/mesh/v1alpha1/proxy.proto b/mesh/v1alpha1/proxy.proto
index 4f632184..7af99b59 100644
--- a/mesh/v1alpha1/proxy.proto
+++ b/mesh/v1alpha1/proxy.proto
@@ -680,7 +680,7 @@ message ProxyConfig {
     // If disabled, this header will not be set. If it is already present, it will be preserved.
     // This header is enabled by default if not configured.
     AttemptCount attempt_count = 4;
-    // Controls various `X-Envoy-*` headers, such as `X-Envoy-Overloaded` and `X-Envoy-Upstream-Service-Time. If enabled,
+    // Controls various `X-Envoy-*` headers, such as `X-Envoy-Overloaded` and `X-Envoy-Upstream-Service-Time`. If enabled,
     // these headers will be included.
     // If disabled, these headers will not be set. If they are already present, they will be preserved.
     // See the [Envoy documentation](https://www.envoyproxy.io/docs/envoy/latest/api-v3/extensions/filters/http/router/v3/router.proto#envoy-v3-api-field-extensions-filters-http-router-v3-router-suppress-envoy-headers) for more details.
diff --git a/security/v1beta1/authorization_policy.pb.go b/security/v1beta1/authorization_policy.pb.go
index 7f627d56..dec40343 100644
--- a/security/v1beta1/authorization_policy.pb.go
+++ b/security/v1beta1/authorization_policy.pb.go
@@ -808,8 +808,8 @@ type Operation struct {
 	// - `/foo/{*}` matches `/foo/bar` but not `/foo/bar/baz`
 	// - `/foo/{**}/` matches `/foo/bar/`, `/foo/bar/baz.txt`, and `/foo//` but not `/foo/bar`
 	// - `/foo/{*}/bar/{**}` matches `/foo/buzz/bar/` and `/foo/buzz/bar/baz`
-	// - `/*/baz/{*}“ is not a valid path template since it includes `*` outside of a supported operator
-	// - `/**/baz/{*}“ is not a valid path template since it includes `**` outside of a supported operator
+	// - `/*/baz/{*}` is not a valid path template since it includes `*` outside of a supported operator
+	// - `/**/baz/{*}` is not a valid path template since it includes `**` outside of a supported operator
 	// - `/{**}/foo/{*}` is not a valid path template since `{**}` is not the last operator
 	// - `/foo/{*}.txt` is invalid since there are characters other than `{*}` in the path segment
 	//
diff --git a/security/v1beta1/authorization_policy.pb.html b/security/v1beta1/authorization_policy.pb.html
index 6a18b120..025bd83d 100644
--- a/security/v1beta1/authorization_policy.pb.html
+++ b/security/v1beta1/authorization_policy.pb.html
@@ -609,8 +609,8 @@ To be a valid path template, the path must not contain <code>*</code>, <code>{</
 <li><code>/foo/{*}</code> matches <code>/foo/bar</code> but not <code>/foo/bar/baz</code></li>
 <li><code>/foo/{**}/</code> matches <code>/foo/bar/</code>, <code>/foo/bar/baz.txt</code>, and <code>/foo//</code> but not <code>/foo/bar</code></li>
 <li><code>/foo/{*}/bar/{**}</code> matches <code>/foo/buzz/bar/</code> and <code>/foo/buzz/bar/baz</code></li>
-<li><code>/*/baz/{*}`` is not a valid path template since it includes </code>*` outside of a supported operator</li>
-<li><code>/**/baz/{*}`` is not a valid path template since it includes </code>**` outside of a supported operator</li>
+<li><code>/*/baz/{*}</code> is not a valid path template since it includes <code>*</code> outside of a supported operator</li>
+<li><code>/**/baz/{*}</code> is not a valid path template since it includes <code>**</code> outside of a supported operator</li>
 <li><code>/{**}/foo/{*}</code> is not a valid path template since <code>{**}</code> is not the last operator</li>
 <li><code>/foo/{*}.txt</code> is invalid since there are characters other than <code>{*}</code> in the path segment</li>
 </ul>
diff --git a/security/v1beta1/authorization_policy.proto b/security/v1beta1/authorization_policy.proto
index 4771c8d7..3b1fc04e 100644
--- a/security/v1beta1/authorization_policy.proto
+++ b/security/v1beta1/authorization_policy.proto
@@ -526,8 +526,8 @@ message Operation {
   // - `/foo/{*}` matches `/foo/bar` but not `/foo/bar/baz`
   // - `/foo/{**}/` matches `/foo/bar/`, `/foo/bar/baz.txt`, and `/foo//` but not `/foo/bar`
   // - `/foo/{*}/bar/{**}` matches `/foo/buzz/bar/` and `/foo/buzz/bar/baz`
-  // - `/*/baz/{*}`` is not a valid path template since it includes `*` outside of a supported operator
-  // - `/**/baz/{*}`` is not a valid path template since it includes `**` outside of a supported operator
+  // - `/*/baz/{*}` is not a valid path template since it includes `*` outside of a supported operator
+  // - `/**/baz/{*}` is not a valid path template since it includes `**` outside of a supported operator
   // - `/{**}/foo/{*}` is not a valid path template since `{**}` is not the last operator
   // - `/foo/{*}.txt` is invalid since there are characters other than `{*}` in the path segment
   //