From b9af6bf86fb5c9fd56956540f0a965ca27febed5 Mon Sep 17 00:00:00 2001 From: Renato Monteiro <45536168+monteiro-renato@users.noreply.github.com> Date: Wed, 11 Sep 2024 12:08:17 +0200 Subject: [PATCH] Fix wording in index.md (#5173) Co-authored-by: opentelemetrybot <107717825+opentelemetrybot@users.noreply.github.com> Co-authored-by: Tiffany Hrabusa <30397949+tiffany76@users.noreply.github.com> --- content/en/docs/concepts/sampling/index.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/content/en/docs/concepts/sampling/index.md b/content/en/docs/concepts/sampling/index.md index dd688b1887c1..535b0c0c4f0f 100644 --- a/content/en/docs/concepts/sampling/index.md +++ b/content/en/docs/concepts/sampling/index.md @@ -62,8 +62,8 @@ Consider sampling if you meet any of the following criteria: beyond errors and latency. - You can describe some common rules that determine if data should be sampled or dropped. -- You have a tell your services apart, so that high- and low-volume services are - sampled differently. +- You have a way to tell your services apart, so that high- and low-volume + services are sampled differently. - You have the ability to route unsampled data (for "just in case" scenarios) to low-cost storage systems.