clarify static route config in configdump (#10434)

Signed-off-by: Rama Chavali <rama.rao@salesforce.com>

Mirrored from https://github.com/envoyproxy/envoy @ fd25c0bbada005102ba74804af4012419a6369a6

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.

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";