This is an automated email from the ASF dual-hosted git repository.

pcongiusti pushed a commit to branch main
in repository https://gitbox.apache.org/repos/asf/camel-website.git

commit 364a43fae2046bad576b63e851e12c2749c7b179
Author: Mert Öztürk <[email protected]>
AuthorDate: Sat Mar 25 13:09:51 2023 +0100

    minor update
---
 content/blog/2023/03/camel-k-telemetry/index.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/content/blog/2023/03/camel-k-telemetry/index.md 
b/content/blog/2023/03/camel-k-telemetry/index.md
index 6c482ddf..9546bd0c 100644
--- a/content/blog/2023/03/camel-k-telemetry/index.md
+++ b/content/blog/2023/03/camel-k-telemetry/index.md
@@ -309,7 +309,7 @@ We are also using inventory.local and order.local host in 
ingress for the rest s
 
 As you can see we did not provide the OTLP API endpoint as Camel K 
automatically discovered the **Jaeger** OTLP API endpoint. For any other 
Distributed Tracing tool you will have to declare it through `-t 
telemetry.endpoint=xxxx`. The `telemetry` trait is expecting an [OTLP trace 
endpoint](https://opentelemetry.io/docs/concepts/sdk-configuration/otlp-exporter-configuration/#otel_exporter_otlp_traces_endpoint).
 
-Now that everything is up let's make some traces !
+Now that everything is up let's make some traces!
 
 ## Generate some integration traces
 

Reply via email to