diff --git a/osrm/doc/interaction_between_cpp_and_lua_in_osrm.md b/osrm/doc/interaction_between_cpp_and_lua_in_osrm.md
index 192b9f8..33d70ae 100644
--- a/osrm/doc/interaction_between_cpp_and_lua_in_osrm.md
+++ b/osrm/doc/interaction_between_cpp_and_lua_in_osrm.md
@@ -15,7 +15,7 @@ Terminologies(e.g. OSM node, OSM way, Segment, etc.) can refer to [Understanding
| `Lua` Functions | Link to OSRM Profiles | Description |
|--------------------|-----------------------|-------------|
|`setup()` |[OSRM profiles - setup](https://github.com/Project-OSRM/osrm-backend/blob/master/docs/profiles.md#setup)|The `setup` function is called once when the profile is loaded and must return a table of configurations.
Note that processing of data is parallelized and several unconnected LUA interpreters will be running at the same time. The `setup` function will be called once for each. Each `LUA` interpreter will have its own set of globals.|
-|`process_node()` |[OSRM profiles - process_node](https://github.com/Project-OSRM/osrm-backend/blob/master/docs/profiles.md#process_nodeprofile-node-result-relations)|Process an OSM node to determine whether this node is a unable-to-pass barrier or can be passed and whether passing it incurs a delay.
More specifically, it will return two booleans:
- `barrier`: indicate a unable-to-pass barrier
- `traffic_lights`: indicate more delay while passing|
+|`process_node()` |[OSRM profiles - process_node](https://github.com/Project-OSRM/osrm-backend/blob/master/docs/profiles.md#process_nodeprofile-node-result-relations)|Process an OSM node to determine whether this node is a unable-to-pass barrier or can be passed and whether passing it incurs a delay.
More specifically, it will return one boolean and one direction enum:
- `barrier`: indicate a unable-to-pass barrier
- `traffic_lights`: indicate more delay while passing|
|`process_way()` |[OSRM profiles - process_way](https://github.com/Project-OSRM/osrm-backend/blob/master/docs/profiles.md#process_wayprofile-way-result-relations)|Given an OSM way, the `process_way` function will either return nothing (meaning we are not going to route over this way at all), or it will set up a result hash.
More specifically,
- return `false`: the whole way can not be passed.
- otherwise: set some attributes in `result` to indicate whether routable and the routable `speed`/`rate` for each direction, e.g. `forward_mode`, `backward_mode`, `forward_speed`, `backward_speed`, `forward_rate`, `backward_rate`, `weight`, `duration`, etc. |
|`process_turn()` |[OSRM profiles - process_turn](https://github.com/Project-OSRM/osrm-backend/blob/master/docs/profiles.md#process_turnprofile-turn)|The `process_turn` function is called for every possible turn in the network. Based on the angle and type of turn you assign the weight and duration of the movement.|
|`process_segment()` |[OSRM profiles - process_segment](https://github.com/Project-OSRM/osrm-backend/blob/master/docs/profiles.md#process_segmentprofile-segment)|The `process_segment` function is called for every segment of OSM ways. A segment is a straight line between two OSM nodes.
As you can see, this is NOT currently used in the `car.lua` profile.|