diff --git a/networking/v1alpha3/virtual_service.pb.go b/networking/v1alpha3/virtual_service.pb.go
index e39c6392512..1210547308e 100644
--- a/networking/v1alpha3/virtual_service.pb.go
+++ b/networking/v1alpha3/virtual_service.pb.go
@@ -120,9 +120,13 @@ type VirtualService struct {
 	// dots in the name). In such a scenario, the FQDN of the host would be
 	// derived based on the underlying platform.
 	//
-	// **A host name can be defined by only one VirtualService**. A single
-	// VirtualService can be used to describe traffic properties for multiple
-	// HTTP and TCP ports.
+	// A single VirtualService can be used to describe all the traffic
+	// properties of the corresponding hosts, including those for multiple
+	// HTTP and TCP ports. Alternatively, the traffic properties of a host
+	// can be defined using more than one VirtualService, with certain
+	// caveats. Refer to the
+	// [Operations Guide](/help/ops/traffic-management/deploy-guidelines/#multiple-virtual-services-and-destination-rules-for-the-same-host)
+	// for details.
 	//
 	// *Note for Kubernetes users*: When short names are used (e.g. "reviews"
 	// instead of "reviews.default.svc.cluster.local"), Istio will interpret
diff --git a/networking/v1alpha3/virtual_service.pb.html b/networking/v1alpha3/virtual_service.pb.html
index aa61515fe10..8c022cad485 100644
--- a/networking/v1alpha3/virtual_service.pb.html
+++ b/networking/v1alpha3/virtual_service.pb.html
@@ -1658,9 +1658,13 @@ <h2 id="VirtualService">VirtualService</h2>
 dots in the name). In such a scenario, the FQDN of the host would be
 derived based on the underlying platform.</p>
 
-<p><strong>A host name can be defined by only one VirtualService</strong>. A single
-VirtualService can be used to describe traffic properties for multiple
-HTTP and TCP ports.</p>
+<p>A single VirtualService can be used to describe all the traffic
+properties of the corresponding hosts, including those for multiple
+HTTP and TCP ports. Alternatively, the traffic properties of a host
+can be defined using more than one VirtualService, with certain
+caveats. Refer to the
+<a href="/help/ops/traffic-management/deploy-guidelines/#multiple-virtual-services-and-destination-rules-for-the-same-host">Operations Guide</a>
+for details.</p>
 
 <p><em>Note for Kubernetes users</em>: When short names are used (e.g. &ldquo;reviews&rdquo;
 instead of &ldquo;reviews.default.svc.cluster.local&rdquo;), Istio will interpret
diff --git a/networking/v1alpha3/virtual_service.proto b/networking/v1alpha3/virtual_service.proto
index bae9cce4fa9..1c48599462d 100644
--- a/networking/v1alpha3/virtual_service.proto
+++ b/networking/v1alpha3/virtual_service.proto
@@ -121,9 +121,13 @@ message VirtualService {
   // dots in the name). In such a scenario, the FQDN of the host would be
   // derived based on the underlying platform.
   //
-  // **A host name can be defined by only one VirtualService**. A single
-  // VirtualService can be used to describe traffic properties for multiple
-  // HTTP and TCP ports.
+  // A single VirtualService can be used to describe all the traffic
+  // properties of the corresponding hosts, including those for multiple
+  // HTTP and TCP ports. Alternatively, the traffic properties of a host
+  // can be defined using more than one VirtualService, with certain
+  // caveats. Refer to the
+  // [Operations Guide](/help/ops/traffic-management/deploy-guidelines/#multiple-virtual-services-and-destination-rules-for-the-same-host)
+  // for details.
   //
   // *Note for Kubernetes users*: When short names are used (e.g. "reviews"
   // instead of "reviews.default.svc.cluster.local"), Istio will interpret