diff --git a/docs/COPY_TO_WAHOO.md b/docs/COPY_TO_WAHOO.md
index 377f936f..13d2b680 100644
--- a/docs/COPY_TO_WAHOO.md
+++ b/docs/COPY_TO_WAHOO.md
@@ -49,6 +49,7 @@ According to [the Wahoo documentation](https://support.wahoofitness.com/hc/en-us
 
 ## Copy device theme
 Device themes are described [here](TAGS_ON_MAP_AND_DEVICE.md#Device-Theme)
+
 In this repo, device themes are stored in folder `device_themes`. There are initial versions and adjusted versions. Both can be further changed to your requirements!
 
 The following table shows the file per device and the location where the device theme needs to be copied to.
diff --git a/docs/TAGS_ON_MAP_AND_DEVICE.md b/docs/TAGS_ON_MAP_AND_DEVICE.md
index 4f822781..c9ce748a 100644
--- a/docs/TAGS_ON_MAP_AND_DEVICE.md
+++ b/docs/TAGS_ON_MAP_AND_DEVICE.md
@@ -48,7 +48,7 @@ There are two types of rendering methods: VTM and non-VTM rendering. This table
 
 You can enable the VTM rendering method on Wahoo devices other than BOLTv2 by creating a empty file on the device with the name "cfg_BHomeActivity_VtmMaps" in the root folder.
 
-The theme is named `mapsforge-bolt.xml` or `mapsforge-roam.xml` for non-VTM rendering and `vtm-elemnt.xml` for VTM-rendering. It's content is more or less equal to the `tag-wahoo.xml` files.
+The device theme is named `mapsforge-bolt.xml` or `mapsforge-roam.xml` for non-VTM rendering and `vtm-elemnt.xml` for VTM-rendering. It's content is more or less equal to the `tag-wahoo.xml` files.
 
 ## Attribute "zoom-min"
 Each entry in the theme has a "zoom-min" attribute, which defines from which zoom level onwards the element will be shown. If zoom-min is set to 13, the OSM-tag will be displayed in zoom level 500m, 200m and 100m.