More new info

src/pages/en/developers/apis/1-routing-api/itinerary-planning/index.md

@@ -35,16 +35,16 @@ See the following examples on how to decode and use polylines:
 **Note:** For more details about the query type **plan** and its parameters you can use the **Documentation Explorer** provided in GraphiQL.
 
 Itinerary planning can be tuned by multiple arguments of the **plan** query.
-* Time arguments (e.g. `minTransferTime`, `bikeSwitchTime`) are taken into account literally when planning the itinerary
-  * For example, if `minTransferTime` is set to 2 minutes, it is not possible to continue the journey by another vehicle within two minutes after disembarking one vehicle
+* Time arguments are taken into account literally when planning the itinerary
+  * For example, if `preferences: {street: { transit: {transfer: {slack: "2m"}}}` is set to 2 minutes, it is not possible to continue the journey by another vehicle within two minutes after disembarking one vehicle
   * Values of time arguments are included in the returned duration of an itinerary
-    * For example, if there is a 15 minute bicycling leg and `bikeSwitchTime` is set to 1 minute, the returned duration of the bicycling leg will be 17 minutes
-* Cost arguments (e.g. `walkBoardCost`) on the other hand are not hard limits, but preferences
-  * For example, if `walkBoardCost` is set to 2 minutes, it is possible to continue the journey immediately after disembarking from one vehicle, but up to 2 minutes longer itineraries are preferred if they have one transfer less and up to 4 minutes longer itineraries are preferred if they have two transfers less, etc.
+    * For example, if there is a 15 minute  leg and `slack` is set to 1 minute, the returned duration of the leg will be 17 minutes
+* Cost arguments on the other hand are not hard limits, but preferences
+  * For example, if `preferences: {street: {walk: {boardCost: 120}}}` is set to 2 minutes, it is possible to continue the journey immediately after disembarking from one vehicle, but up to 2 minutes longer itineraries are preferred if they have one transfer less and up to 4 minutes longer itineraries are preferred if they have two transfers less, etc.
   * Cost is not included in the returned duration of an itinerary
-    * For example, if there is a 15 minute bicycling leg and `bikeSwitchCost` is set to 1 minute, the returned duration of the bicycling leg will be 15 minutes
-* Multiplier arguments (e.g. `walkReluctance`, `modeWeight`) are used to multiply costs of an leg
-  * For example, if `walkReluctance` is set to 3.0, the cost of each walking section will be multiplied by 3 and thus itineraries with less walking are preferred
+    * For example, if there is a 15 minute walking leg and `boardCost` is set to 1 minute, the returned duration of the walking leg will be 15 minutes
+* Multiplier arguments (e.g. `preferences: {street: {walk: {reluctance: 3}}}`) are used to multiply costs of an leg
+  * For example, if `reluctance` is set to 3.0, the cost of each walking section will be multiplied by 3 and thus itineraries with less walking are preferred
 
 ### Plan an itinerary from location (60.168992,24.932366) to (60.175294,24.684855)