docs(event): Fix wording and link for event propagation

Signed-off-by: Loïc Saint-Roch <[email protected]>
nunchistudio · Feb 13, 2024 · eea6ba1 · eea6ba1
1 parent 72e91a6
commit eea6ba1
Show file tree

Hide file tree

Showing 3 changed files with 3 additions and 3 deletions.
diff --git a/README.md b/README.md
@@ -17,7 +17,7 @@ helix acts as a library you can import in your code. Implementations:
 helix was developed with the following use cases in mind:
 
 - Consistent and high-performance (micro) services;
-- Effortless end-to-end observability and event tracking across services.
+- Effortless end-to-end observability and event propagation across services.
 
 ## Goals
 

diff --git a/documentation/index.md b/documentation/index.md
@@ -19,7 +19,7 @@ helix acts as a library you can import in your code. Implementations:
 helix was developed with the following use cases in mind:
 
 - Consistent and high-performance (micro) services;
-- Effortless end-to-end observability and event tracking across services.
+- Effortless end-to-end observability and event propagation across services.
 
 ## Goals
 

diff --git a/documentation/opentelemetry.md b/documentation/opentelemetry.md
@@ -28,7 +28,7 @@ helix relies on the following required environment variables:
 
 ### Traces
 
-When possible, it's strongly advised to leverage [Event propagation](/helix/event)
+When possible, it's strongly advised to leverage [Event propagation](/helix/event-propagation)
 within distributed tracing.
 
 {% tab name="Go" %}