diff --git a/mesh/v1alpha1/config.pb.go b/mesh/v1alpha1/config.pb.go
index 1ff777bc3a..a2fc4ed69e 100644
--- a/mesh/v1alpha1/config.pb.go
+++ b/mesh/v1alpha1/config.pb.go
@@ -4201,7 +4201,7 @@ type MeshConfig_ExtensionProvider_GrpcService struct {
 	// Optional. Specifies the timeout for the GRPC request.
 	Timeout *duration.Duration `protobuf:"bytes,1,opt,name=timeout,proto3" json:"timeout,omitempty"`
 	// Optional. Additional metadata to include in streams initiated to the GrpcService. This can be used for
-	// scenarios in which additional ad hoc authorization headers (e.g. “x-foo-bar: baz-key“) are to
+	// scenarios in which additional ad hoc authorization headers (e.g. "x-foo-bar: baz-key") are to
 	// be injected.
 	InitialMetadata []*MeshConfig_ExtensionProvider_HttpHeader `protobuf:"bytes,2,rep,name=initial_metadata,json=initialMetadata,proto3" json:"initial_metadata,omitempty"`
 }
diff --git a/mesh/v1alpha1/config.proto b/mesh/v1alpha1/config.proto
index 0b4d7e2d90..3907021350 100644
--- a/mesh/v1alpha1/config.proto
+++ b/mesh/v1alpha1/config.proto
@@ -1279,7 +1279,7 @@ message MeshConfig {
       google.protobuf.Duration timeout = 1;
 
       // Optional. Additional metadata to include in streams initiated to the GrpcService. This can be used for
-      // scenarios in which additional ad hoc authorization headers (e.g. “x-foo-bar: baz-key“) are to
+      // scenarios in which additional ad hoc authorization headers (e.g. "x-foo-bar: baz-key") are to
       // be injected.
       repeated HttpHeader initial_metadata = 2;
     }
diff --git a/mesh/v1alpha1/istio.mesh.v1alpha1.pb.html b/mesh/v1alpha1/istio.mesh.v1alpha1.pb.html
index 104db5f9f2..1d81c3d5c5 100644
--- a/mesh/v1alpha1/istio.mesh.v1alpha1.pb.html
+++ b/mesh/v1alpha1/istio.mesh.v1alpha1.pb.html
@@ -2425,7 +2425,7 @@ <h4 id="MeshConfig-ExtensionProvider-GrpcService">GrpcService</h4>
 </div></td>
 <td>
 <p>Additional metadata to include in streams initiated to the GrpcService. This can be used for
-scenarios in which additional ad hoc authorization headers (e.g. “x-foo-bar: baz-key“) are to
+scenarios in which additional ad hoc authorization headers (e.g. &ldquo;x-foo-bar: baz-key&rdquo;) are to
 be injected.</p>
 
 </td>