docs: correct the HTTP request_timeout documentation

api/envoy/config/filter/network/http_connection_manager/v2/http_connection_manager.proto

@@ -336,7 +336,7 @@ message HttpConnectionManager {
   // timeout, although per-route idle timeout overrides will continue to apply.
   google.protobuf.Duration stream_idle_timeout = 24;
 
-  // A timeout for idle requests managed by the connection manager.
+  // The amount of time that Envoy will wait for the entire request to be received.
   // The timer is activated when the request is initiated, and is disarmed when the last byte of the
   // request is sent upstream (i.e. all decoding filters have processed the request), OR when the
   // response is initiated. If not specified or set to 0, this timeout is disabled.

api/envoy/extensions/filters/network/http_connection_manager/v3/http_connection_manager.proto

@@ -326,7 +326,7 @@ message HttpConnectionManager {
   // timeout, although per-route idle timeout overrides will continue to apply.
   google.protobuf.Duration stream_idle_timeout = 24;
 
-  // A timeout for idle requests managed by the connection manager.
+  // The amount of time that Envoy will wait for the entire request to be received.
   // The timer is activated when the request is initiated, and is disarmed when the last byte of the
   // request is sent upstream (i.e. all decoding filters have processed the request), OR when the
   // response is initiated. If not specified or set to 0, this timeout is disabled.

docs/root/faq/configuration/timeouts.rst

@@ -41,7 +41,7 @@ context request/stream is interchangeable.
 * The HTTP connection manager :ref:`request_timeout
   <envoy_api_field_config.filter.network.http_connection_manager.v2.HttpConnectionManager.request_timeout>`
   is the amount of time the connection manager will allow for the *entire request stream* to be
-  received by the client.
+  received from the client.
 
   .. attention::