From a34f6092d5051166ee50dbd16f4c6ebc0b4d3edb Mon Sep 17 00:00:00 2001 From: Manik Rana Date: Tue, 17 Dec 2024 22:46:01 +0530 Subject: [PATCH] fix: wording Co-authored-by: Arthur Silva Sens Signed-off-by: Manik Rana --- ...2024-12-14_update-created-timestamps-for-openmetrics-text.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/proposals/2024-12-14_update-created-timestamps-for-openmetrics-text.md b/proposals/2024-12-14_update-created-timestamps-for-openmetrics-text.md index 20c9015..a09c7ff 100644 --- a/proposals/2024-12-14_update-created-timestamps-for-openmetrics-text.md +++ b/proposals/2024-12-14_update-created-timestamps-for-openmetrics-text.md @@ -26,7 +26,7 @@ Created Timestamps (CTs) were proposed in the summer of 2023 with support for th These characterisitics, specifically the final one means that the parser must search or "peek" ahead to find the `_created` line for a given metric with the same label set and thus, requires additional CPU/memory resources when it can be saved. -This search operation can be specifically taxing when the CT line, if it exists, is the very last line in a large MetricFamily such as that of a histogram with many buckets. +This search operation can be particularly taxing when the CT line, if it exists, is the very last line in a large MetricFamily, such as a histogram with many buckets. ### Pitfalls of the current solution