review fix

Author: bstrzele

Diff for: docs/metrics.md

@@ -242,7 +242,7 @@ For [MediaPipe Graphs](./mediapipe.md) execution there are 6 generic metrics whi
 | gauge      | ovms_current_graphs | Number of graphs currently in-process. For unary communication it is equal to number of currently processing requests (each request initializes separate MediaPipe graph). For streaming communication it is equal to number of active client connections. Each connection is able to reuse the graph and decide when to delete it when the connection is closed. |
 | counter      | ovms_graph_error | Counts errors in MediaPipe graph execution phase. For example V3 LLM text generation fails in LLMCalculator due to missing prompt - calculator returns an error and graph cancels. |
 | histogram      | ovms_graph_processing_time_us | Tracks duration of successfully started mediapipe graphs in us. It can represent pipeline processing time for unary calls or the session length for streamed requests. |
-| histogram      | ovms_graph_request_latency_us | Time between MediaPipe graph packet creation (request receival) and result packet generation (full or partial response). Incoming packet timestamp is used as a source of truth for receival time, therefore using manual timestamping (via client) is highly discouraged. Model server automatically stamps the packets in case there is no manual timestamping. |
+| histogram      | ovms_graph_request_latency_us | Difference between MediaPipe packet timestamps at the time of creation (request receival) and when the packet generation has concluded (full or partial response). Server automatically timestamps the incoming  packets and is used as a source of truth for receival time, unless client opts-in to manual timestamping (NOTE: manual timestamping causes the metric results to become invalid). |
 
 Exposing custom metrics in calculator implementations (MediaPipe graph nodes) is not supported yet.