diff --git a/r-package/vignettes/detailed_itineraries.Rmd b/r-package/vignettes/detailed_itineraries.Rmd
index 3027dadb..cabbd75f 100644
--- a/r-package/vignettes/detailed_itineraries.Rmd
+++ b/r-package/vignettes/detailed_itineraries.Rmd
@@ -26,7 +26,7 @@ knitr::opts_chunk$set(
 
 **r5r** has some extremely efficient functions to run multimodal routing and accessibility analysis. In general, though, these functions output only the essential information required by most transport planning applications and simulation models. Moreover, the algorithms behind these function return only the optimal route in terms of minimizing travel times and/or monetary costs. Sometimes, though, we would like to do more simple route planning analysis and extract more information for each route. Also, we might be interested in finding not only the fastest route but some other suboptimal route alternatives too.
 
-This is where the `detailed_itineraries()` function comes in. This function outputs for each origin destination pair a detailed route plan with information desegregated by trip segment. This includes information on the transport mode, waiting times, travel times and distances of each trip segment and the trip geometry. Moreover, the `detailed_itineraries()` function can also return results for multiple route alternatives. Let's see how this function works using a reproducible example.
+This is where the `detailed_itineraries()` function comes in. This function outputs for each origin destination pair a detailed route plan with information per leg, meaning a route taken by a single mode such as a walk to the bus stop. In R5's documentation these legs are referred to as 'segments', a word more usually used to describe small sections on the transport network. See the [Transportation chapter in Geocompuation with R]([https://geocompr.robinlovelace.net/transport.html](https://geocompr.robinlovelace.net/transport.html#routes)) for more details on routing engines. Results contain information on the mode, waiting times, travel times and distances for each leg (or 'segment' in R5 documentation) and the trip geometry. Moreover, the `detailed_itineraries()` function can also return results for multiple route alternatives. Let's see how this function works using a reproducible example.
  
 
 **obs.** We only recommend using `detailed_itineraries()` in case you are interested in finding suboptimal alternative routes and/or need the geometry information of the outputs. If you only want to have route information detailed by trip segments, then we would strongly encourage you to use the `expanded_travel_time_matrix()` function. More info here.