diff --git a/api/envoy/admin/v2alpha/config_dump.proto b/api/envoy/admin/v2alpha/config_dump.proto
index 5e3a14592ba22..e5ddc6cce62a9 100644
--- a/api/envoy/admin/v2alpha/config_dump.proto
+++ b/api/envoy/admin/v2alpha/config_dump.proto
@@ -170,10 +170,10 @@ message ClustersConfigDump {
 }
 
 // Envoy's RDS implementation fills this message with all currently loaded routes, as described by
-// their RouteConfiguration objects. Static routes configured in the bootstrap configuration are
-// separated from those configured dynamically via RDS. Route configuration information can be used
-// to recreate an Envoy configuration by populating all routes as static routes or by returning them
-// in RDS responses.
+// their RouteConfiguration objects. Static routes that are either defined in the bootstrap configuration
+// or defined inline while configuring listeners are separated from those configured dynamically via RDS.
+// Route configuration information can be used to recreate an Envoy configuration by populating all routes
+// as static routes or by returning them in RDS responses.
 message RoutesConfigDump {
   message StaticRouteConfig {
     // The route config.
diff --git a/api/envoy/admin/v3/config_dump.proto b/api/envoy/admin/v3/config_dump.proto
index 8a527f6fd9bc5..6e2e5952b3e50 100644
--- a/api/envoy/admin/v3/config_dump.proto
+++ b/api/envoy/admin/v3/config_dump.proto
@@ -201,10 +201,10 @@ message ClustersConfigDump {
 }
 
 // Envoy's RDS implementation fills this message with all currently loaded routes, as described by
-// their RouteConfiguration objects. Static routes configured in the bootstrap configuration are
-// separated from those configured dynamically via RDS. Route configuration information can be used
-// to recreate an Envoy configuration by populating all routes as static routes or by returning them
-// in RDS responses.
+// their RouteConfiguration objects. Static routes that are either defined in the bootstrap configuration
+// or defined inline while configuring listeners are separated from those configured dynamically via RDS.
+// Route configuration information can be used to recreate an Envoy configuration by populating all routes
+// as static routes or by returning them in RDS responses.
 message RoutesConfigDump {
   option (udpa.annotations.versioning).previous_message_type =
       "envoy.admin.v2alpha.RoutesConfigDump";
diff --git a/generated_api_shadow/envoy/admin/v2alpha/config_dump.proto b/generated_api_shadow/envoy/admin/v2alpha/config_dump.proto
index 5e3a14592ba22..e5ddc6cce62a9 100644
--- a/generated_api_shadow/envoy/admin/v2alpha/config_dump.proto
+++ b/generated_api_shadow/envoy/admin/v2alpha/config_dump.proto
@@ -170,10 +170,10 @@ message ClustersConfigDump {
 }
 
 // Envoy's RDS implementation fills this message with all currently loaded routes, as described by
-// their RouteConfiguration objects. Static routes configured in the bootstrap configuration are
-// separated from those configured dynamically via RDS. Route configuration information can be used
-// to recreate an Envoy configuration by populating all routes as static routes or by returning them
-// in RDS responses.
+// their RouteConfiguration objects. Static routes that are either defined in the bootstrap configuration
+// or defined inline while configuring listeners are separated from those configured dynamically via RDS.
+// Route configuration information can be used to recreate an Envoy configuration by populating all routes
+// as static routes or by returning them in RDS responses.
 message RoutesConfigDump {
   message StaticRouteConfig {
     // The route config.
diff --git a/generated_api_shadow/envoy/admin/v3/config_dump.proto b/generated_api_shadow/envoy/admin/v3/config_dump.proto
index 8a527f6fd9bc5..6e2e5952b3e50 100644
--- a/generated_api_shadow/envoy/admin/v3/config_dump.proto
+++ b/generated_api_shadow/envoy/admin/v3/config_dump.proto
@@ -201,10 +201,10 @@ message ClustersConfigDump {
 }
 
 // Envoy's RDS implementation fills this message with all currently loaded routes, as described by
-// their RouteConfiguration objects. Static routes configured in the bootstrap configuration are
-// separated from those configured dynamically via RDS. Route configuration information can be used
-// to recreate an Envoy configuration by populating all routes as static routes or by returning them
-// in RDS responses.
+// their RouteConfiguration objects. Static routes that are either defined in the bootstrap configuration
+// or defined inline while configuring listeners are separated from those configured dynamically via RDS.
+// Route configuration information can be used to recreate an Envoy configuration by populating all routes
+// as static routes or by returning them in RDS responses.
 message RoutesConfigDump {
   option (udpa.annotations.versioning).previous_message_type =
       "envoy.admin.v2alpha.RoutesConfigDump";