docs: Fix broken links

[apps/agl-service-can-low-level.git] / docs / 3-Usage.md

diff --git a/docs/3-Usage.md b/docs/3-Usage.md
index 479dd51..bc38417 100644 (file)
--- a/docs/3-Usage.md
+++ b/docs/3-Usage.md
@@ -99,7 +99,7 @@ The binding reads system configuration file _/etc/dev-mapping.conf_ at start to
 map logical name from signals described in JSON file to linux devices name
 initialized by the system.
 
-Edit file _/etc/dev-mappping.conf_ and add mapping in section `CANbus-mapping`.
+Edit file _/etc/dev-mapping.conf_ and add mapping in section `CANbus-mapping`.
 
 Default binding configuration use a CAN bus named `hs` so you need to map it to
 the real one, here are some examples:
@@ -141,7 +141,7 @@ afm-util run low-can-service@4.0
 ```
 
 You can find instructions to use afm-util tool
-[here](http://docs.iot.bzh/docs/apis_services/en/dev/reference/af-main/afm-daemons.html#using-afm-util),
+[here](http://docs.automotivelinux.org/master/docs/apis_services/en/dev/reference/af-main/1-afm-daemons.html#using-afm-util),
  as well as documentation about Application Framework.
 
 But you can't control nor interact with it because you don't know security
@@ -311,7 +311,7 @@ Examples:
 low-can write { "bus_name": "hs", "frame": { "can_id": 1568, "can_dlc":
 8, "can_data": [ 255,255,255,255,255,255,255,255]} }
 # Write a signal's value.
-low-can write { "signal_name": "engine.speed", "value": 1256}
+low-can write { "signal_name": "engine.speed", "signal_value": 1256}
 ```
 
 To be able to use write capability, you need to add the permission