route: Clarify the `most_specific_header_mutations_wins` (#31658)

Signed-off-by: tyxia <tyxia@google.com>

Mirrored from https://github.com/envoyproxy/envoy @ 78814130c7427236bf222824f03d813be00f9694

envoy/config/route/v3/route.proto

@@ -82,14 +82,11 @@ message RouteConfiguration {
     (validate.rules).repeated = {items {string {well_known_regex: HTTP_HEADER_NAME strict: false}}}
   ];
 
-  // By default, headers that should be added/removed are evaluated from most to least specific:
+  // Headers mutations at all levels are evaluated, if specified. By default, the order is from most
-  //
+  // specific (i.e. route entry level) to least specific (i.e. route configuration level). Later header
-  // * route level
+  // mutations may override earlier mutations.
-  // * virtual host level
+  // This order can be reversed by setting this field to true. In other words, most specific level mutation
-  // * connection manager level
+  // is evaluated last.
-  //
-  // To allow setting overrides at the route or virtual host level, this order can be reversed
-  // by setting this option to true. Defaults to false.
   //
   bool most_specific_header_mutations_wins = 10;