diff --git a/USERGUIDE.md b/USERGUIDE.md
index f20aa431..fe6790b5 100644
--- a/USERGUIDE.md
+++ b/USERGUIDE.md
@@ -34,7 +34,7 @@ Connectors are the client to the different messaging servers: MQTT brokers, Kafk
 The `Default Http Connector` is a special case of a connector:
 1. It has not to be created as the connector will be created automatically at startup of the backend for every tenant.
 1. The endpoint for the `Default Http Connector` can be accessed at the url `https://<YOUR_CUMULOCITY_TENANT>/service/dynamic-mapping-service/httpConnector/<MAPPING_TOPIC>`
-1. The sub path following `.../dynamic-mapping-service/httpConnector/` is used as `<MAPPING_TOPIC>`, e.g. a json payload send to `https://<YOUR_CUMULOCITY_TENANT>/service/dynamic-mapping-service/httpConnector/temp/berlin_01` will be resolved to a mapping with mapping topic: `/temp/berlin_01`
+1. The sub path following `.../dynamic-mapping-service/httpConnector/` is used as `<MAPPING_TOPIC>`, e.g. a json payload send to `https://<YOUR_CUMULOCITY_TENANT>/service/dynamic-mapping-service/httpConnector/temp/berlin_01` will be resolved to a mapping with mapping topic: `temp/berlin_01`
 
 The configurations of connectors are persisted as tenant options in the Cumulocity Tenant and can be managed using the following UI.\
 The table of configured connectors to different brokers can be: