diff --git a/Docs/Content/telemetry/fluentd.md b/Docs/Content/telemetry/fluentd.md
index d370413a34..b9d27e8cef 100644
--- a/Docs/Content/telemetry/fluentd.md
+++ b/Docs/Content/telemetry/fluentd.md
@@ -109,7 +109,7 @@ An example of full configuration file is shown below:
 </match>
 ```
 
-**If you're self hosting OneUptime**: If you're self hosting OneUptime you can replace the `endpoint_url` with the URL of your OneUptime instance. `http(s)://<YOUR_HOST>/fluentd/logs`
+**If you're self hosting OneUptime**: If you're self hosting OneUptime you can replace the `endpoint_url` with the URL of your OneUptime instance. `http(s)://YOUR_ONEUPTIME_HOST/fluentd/logs`
 
 ## Usage
 
diff --git a/Docs/Content/telemetry/open-telemetry.md b/Docs/Content/telemetry/open-telemetry.md
index c8aa7031fa..ea068f1d9c 100644
--- a/Docs/Content/telemetry/open-telemetry.md
+++ b/Docs/Content/telemetry/open-telemetry.md
@@ -55,7 +55,10 @@ export OTEL_EXPORTER_OTLP_ENDPOINT=https://otlp.oneuptime.com
 export OTEL_SERVICE_NAME=my-service
 ```
 
-If you're self-hosting oneuptime, this can be changed to your self hosted OpenTelemetry collector endpoint (eg: `http(s)://<your-oneuptime-host>/otlp`)
+
+**Self Hosted OneUptime**
+
+If you're self-hosting oneuptime, this can be changed to your self hosted OpenTelemetry collector endpoint (eg: `http(s)://YOUR-ONEUPTIME-HOST/otlp`)
 
 Once you run your application, you should see the logs in the OneUptime telemetry service page. Please contact support@oneuptime.com if you need any help.