From d9a03f8365d398a0db1b35cfdb3e423a3278115c Mon Sep 17 00:00:00 2001 From: brian lewis Date: Sat, 25 Nov 2017 16:09:30 -0800 Subject: [PATCH] Refer to Lua scripting language by its correct name --- docs/profiles.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/profiles.md b/docs/profiles.md index 7d8d24008..0458bcb74 100644 --- a/docs/profiles.md +++ b/docs/profiles.md @@ -17,8 +17,8 @@ It's important to understand that profiles are used when preprocessing the OSM d This means that after modifying a profile **you will need to extract, contract and reload the data again** and to see changes in the routing results. See [Processing Flow](https://github.com/Project-OSRM/osrm-backend/wiki/Processing-Flow) for more. -## Profiles are written in LUA -Profiles are not just configuration files. They are scripts written in the [LUA scripting language](http://www.lua.org). The reason for this is that OpenStreetMap data is complex, and it's not possible to simply define tag mappings. LUA scripting offers a powerful way to handle all the possible tag combinations found in OpenStreetMap nodes and ways. +## Profiles are written in Lua +Profiles are not just configuration files. They are scripts written in the [Lua scripting language](http://www.lua.org). The reason for this is that OpenStreetMap data is complex, and it's not possible to simply define tag mappings. Lua scripting offers a powerful way to handle all the possible tag combinations found in OpenStreetMap nodes and ways. ## Basic structure of profiles A profile will process every node and way in the OSM input data to determine what ways are routable in which direction, at what speed, etc.