diff --git a/website/src/lib/docs/en/gpx.mdx b/website/src/lib/docs/en/gpx.mdx
index 89707ab92..866b80123 100644
--- a/website/src/lib/docs/en/gpx.mdx
+++ b/website/src/lib/docs/en/gpx.mdx
@@ -3,6 +3,7 @@ title: GPX file format
 ---
 
 <script>
+    import DocsNote from '$lib/components/docs/DocsNote.svelte';
     import { Waypoints, Route, MapPin } from '@lucide/svelte';
 </script>
 
@@ -30,8 +31,17 @@ However, the hierarchy described above allows for more advanced use cases, such
 
 ### <Route size="16" class="inline-block" style="margin-bottom: 2px" /> Routes
 
-A **route** is a single continuous path described by a sequence of **route points**, which are the places to go through, like the anchor points of the [routing tool](./toolbar/routing).
-Like a track, it can have a **name**, a **description**, and **appearance properties**.
+A **route** is a single continuous path made of a sequence of **route points**.
+These are mandatory checkpoints, which correspond to the anchor points of the [routing tool](./toolbar/routing).
+The points in between are only a suggested path connecting the route points.
+Like a track, a route can have a **name**, a **description**, and **appearance properties**.
+
+<DocsNote>
+
+Nowadays, most apps and GPS devices work perfectly well with tracks, even for navigation.
+However, some of them only work with routes: in that case, you can [convert](./menu/edit) your tracks to routes, or [create](./menu/file) a route file from the start.
+
+</DocsNote>
 
 ### <MapPin size="16" class="inline-block" style="margin-bottom: 2px" /> Points of interest