fix: typo

Signed-off-by: Kang Liu <[email protected]>
jaegertracing · Dec 3, 2024 · fea3738 · fea3738
1 parent 3dbd3ef
commit fea3738
Show file tree

Hide file tree

Showing 2 changed files with 2 additions and 2 deletions.
diff --git a/content/docs/2.0/sampling.md b/content/docs/2.0/sampling.md
@@ -24,7 +24,7 @@ Jaeger supports tail based sampling via a [tail sampling processor](https://gith
 
 Remote sampling is a form of head-based sampling where the configuration for the sampling strategy is retrieved by the SDKs from the Jaeger backend. It allows consolidating the sampling policies in one central location and simplifying the management of the SDKs running in large scale production systems.
 
-Jaeger's `remove_sampling` extension supports [Jaeger's remote sampling protocol][remote-sampling-api] that defines sampling strategies as distinct sampling rates for each service and endpoint. The strategies can be generated by Jaeger in two different ways: [periodically loaded from a file](#file-based-sampling-configuration) or [dynamically calculated based on traffic](#adaptive-sampling).
+Jaeger's `remote_sampling` extension supports [Jaeger's remote sampling protocol][remote-sampling-api] that defines sampling strategies as distinct sampling rates for each service and endpoint. The strategies can be generated by Jaeger in two different ways: [periodically loaded from a file](#file-based-sampling-configuration) or [dynamically calculated based on traffic](#adaptive-sampling).
 
 These are two basic types of head samplers that are used by the remote sampling: 
 

diff --git a/content/docs/next-release-v2/sampling.md b/content/docs/next-release-v2/sampling.md
@@ -24,7 +24,7 @@ Jaeger supports tail based sampling via a [tail sampling processor](https://gith
 
 Remote sampling is a form of head-based sampling where the configuration for the sampling strategy is retrieved by the SDKs from the Jaeger backend. It allows consolidating the sampling policies in one central location and simplifying the management of the SDKs running in large scale production systems.
 
-Jaeger's `remove_sampling` extension supports [Jaeger's remote sampling protocol][remote-sampling-api] that defines sampling strategies as distinct sampling rates for each service and endpoint. The strategies can be generated by Jaeger in two different ways: [periodically loaded from a file](#file-based-sampling-configuration) or [dynamically calculated based on traffic](#adaptive-sampling).
+Jaeger's `remote_sampling` extension supports [Jaeger's remote sampling protocol][remote-sampling-api] that defines sampling strategies as distinct sampling rates for each service and endpoint. The strategies can be generated by Jaeger in two different ways: [periodically loaded from a file](#file-based-sampling-configuration) or [dynamically calculated based on traffic](#adaptive-sampling).
 
 These are two basic types of head samplers that are used by the remote sampling: