Terminology completed.

Change-Id: I68b7221762fa4782f61bd073f0c1c1f64373bd81
Signed-off-by: Romain Forlot <romain.forlot@iot.bzh>

3 files changed, 9 insertions, 8 deletions

diff --git a/docs/cover.jpg b/docs/cover.jpg
index 668f253..9e98734 100644
--- a/docs/cover.jpg
+++ b/docs/cover.jpg
diff --git a/docs/cover_small.jpg b/docs/cover_small.jpg
index 216b4bb..c6b1f92 100644
--- a/docs/cover_small.jpg
+++ b/docs/cover_small.jpg
diff --git a/docs/part-1/1-Architecture.md b/docs/part-1/1-Architecture.md
index 065d2ec..9d1e328 100644
--- a/docs/part-1/1-Architecture.md
+++ b/docs/part-1/1-Architecture.md
@@ -37,13 +37,14 @@ There are three main parts with **Signal Composer**:
 
 Here is a little terminology guide to set the vocabulary:
 
-- **sources**
-- **signals**
-- **api**
-- **event**
-- **callbacks**
-- **action**
-- **virtual signals**
-- **raw signals**
+- **api**: a binding API name
+- **action**: a function called at a certain time
+- **callbacks**: a function called at a certain time
+- **event**: the raw event that materialize the signal
+- **sources**: a binding API name
+- **signals**: an event generated by the **Application Framework**
+- **virtual signals**: a signal composed of **raw signals** with value
+ calculated by a **callbacks**
+- **raw signals**: an event generated by a **low level** binding
 
 [GlobalArchitecture]: pictures/Global_Signaling_Architecture.png "Global architecture"