From 1bade975d22d23c9bc4b7d2d9619acdadfc7039e Mon Sep 17 00:00:00 2001
From: esafar ~ c2h6 <77629339+ethan0905@users.noreply.github.com>
Date: Thu, 24 Nov 2022 15:02:55 +0100
Subject: [PATCH 01/21] Update README.md

---
 README.md | 11 +++++++++--
 1 file changed, 9 insertions(+), 2 deletions(-)

diff --git a/README.md b/README.md
index 8c432ab..140a6a8 100644
--- a/README.md
+++ b/README.md
@@ -6,13 +6,20 @@
 
 </div>
 
+## Pitch
+We are 4 students from 42 school and we have been experiencing issues with our client payement. We create this projet to solve this with a smart contract store on a blockchain !
+
 ## ❗ Problem
-#### What problem does your project solve?  
+#### What problem does your project solve? 
+
 #### How does it fit into the theme "Building a Decentralized Future"?  
   
 ## ✅ Solution
 #### How did you resolve this issue?  
-→ We decided to solve this issue, by creating an easy to use and decentralized payement protocol service that protect the 2 users during transaction. [...] 
+→ We decided to solve this issue, by creating an easy to use and decentralized payement protocol service that protect the 2 users during transaction. 
+→ For each mission, we create a unique smart contract that is not editable and non replicable.
+→ We store the documents on ipfs
+  
 #### What technologies did you use?  
 TailwindCSS and ReactJS for frontend and backend  
 Starton API for the smart contracts managements  

From a785b7fa12e05d91d005b62beb39c0e9961fe0fd Mon Sep 17 00:00:00 2001
From: esafar ~ c2h6 <77629339+ethan0905@users.noreply.github.com>
Date: Thu, 24 Nov 2022 15:03:10 +0100
Subject: [PATCH 02/21] Update README.md

---
 README.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/README.md b/README.md
index 140a6a8..fc56eb9 100644
--- a/README.md
+++ b/README.md
@@ -32,7 +32,7 @@ Starton API for the smart contracts managements
 1. Clone the repository:  
 `git clone https://github.com/ethan0905/hackathon.git`
  
-2. Run at the root of repository, the following bash commands:
+2. Run at the root of repository, the following bash commands:  
 `docker-compose up --build`
     
 3. Then go to the following url on internet:  

From 8bc011507656a19f4d2c0ae489861630ce047636 Mon Sep 17 00:00:00 2001
From: esafar ~ c2h6 <77629339+ethan0905@users.noreply.github.com>
Date: Thu, 24 Nov 2022 15:03:52 +0100
Subject: [PATCH 03/21] Update README.md

---
 README.md | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/README.md b/README.md
index fc56eb9..db3f153 100644
--- a/README.md
+++ b/README.md
@@ -16,9 +16,9 @@ We are 4 students from 42 school and we have been experiencing issues with our c
   
 ## ✅ Solution
 #### How did you resolve this issue?  
-→ We decided to solve this issue, by creating an easy to use and decentralized payement protocol service that protect the 2 users during transaction. 
-→ For each mission, we create a unique smart contract that is not editable and non replicable.
-→ We store the documents on ipfs
+→ We decided to solve this issue, by creating an easy to use and decentralized payement protocol service that protect the 2 users during transaction.  
+→ For each mission, we create a unique smart contract that is not editable and non replicable.  
+→ We store the documents on ipfs  
   
 #### What technologies did you use?  
 TailwindCSS and ReactJS for frontend and backend  

From dce4849828ebece26a2cbf0d67259badcc44d67b Mon Sep 17 00:00:00 2001
From: esafar ~ c2h6 <77629339+ethan0905@users.noreply.github.com>
Date: Thu, 24 Nov 2022 15:07:23 +0100
Subject: [PATCH 04/21] Update README.md

---
 README.md | 5 +++--
 1 file changed, 3 insertions(+), 2 deletions(-)

diff --git a/README.md b/README.md
index db3f153..d9d3a39 100644
--- a/README.md
+++ b/README.md
@@ -18,11 +18,12 @@ We are 4 students from 42 school and we have been experiencing issues with our c
 #### How did you resolve this issue?  
 → We decided to solve this issue, by creating an easy to use and decentralized payement protocol service that protect the 2 users during transaction.  
 → For each mission, we create a unique smart contract that is not editable and non replicable.  
-→ We store the documents on ipfs  
+→ We store the documents on decentralised database (IPFS).  
   
 #### What technologies did you use?  
 TailwindCSS and ReactJS for frontend and backend  
-Starton API for the smart contracts managements  
+Starton API for the smart contracts managements
+IPFS for the decentralised datastorage  
   
 #### What was your biggest technical challenge and how does your solution solve it?
 ?

From 8a6ccc72ccf9c624f75fb20add6246eae66ae3d0 Mon Sep 17 00:00:00 2001
From: esafar ~ c2h6 <77629339+ethan0905@users.noreply.github.com>
Date: Thu, 24 Nov 2022 15:26:21 +0100
Subject: [PATCH 05/21] Update README.md

---
 README.md | 24 ++++++++++++++++++++----
 1 file changed, 20 insertions(+), 4 deletions(-)

diff --git a/README.md b/README.md
index d9d3a39..9c8e02a 100644
--- a/README.md
+++ b/README.md
@@ -6,19 +6,27 @@
 
 </div>
 
-## Pitch
+## 🤏 Pitch
 We are 4 students from 42 school and we have been experiencing issues with our client payement. We create this projet to solve this with a smart contract store on a blockchain !
 
 ## ❗ Problem
 #### What problem does your project solve? 
-
+- Contract distortion
+- Deadline for payement not respected
+- Wrong amount
+  
 #### How does it fit into the theme "Building a Decentralized Future"?  
+The solution is independant, self governing.  
+We never gonna interact with the contract.
+
   
 ## ✅ Solution
 #### How did you resolve this issue?  
 → We decided to solve this issue, by creating an easy to use and decentralized payement protocol service that protect the 2 users during transaction.  
 → For each mission, we create a unique smart contract that is not editable and non replicable.  
-→ We store the documents on decentralised database (IPFS).  
+→ We store the documents on decentralised database (IPFS).
+  
+We create a trust environment for every users.  
   
 #### What technologies did you use?  
 TailwindCSS and ReactJS for frontend and backend  
@@ -47,7 +55,12 @@ IPFS for the decentralised datastorage
  - Smartcontract
  - npm install react-ipfs-uploader
  - npm install ipfs -g (for ipfs)
-  
+
+## Business model
+
+pas besoin de bcp de personnes (peu couteux)
+ajout differents type de contracts -> toucher une plus grande audience 
+
 ## 🧭 Roadmap
 
 - [x] Docker installation
@@ -61,5 +74,8 @@ IPFS for the decentralised datastorage
 - [ ] Form:
     - [ ] Interaction with Smart contract at {address} on {network}
 
+## Development perspective
+Create a DAO, 
+
 ## ⚠️ License
 Distributed under the MIT License. See `LICENSE.txt` for more information.  

From eedff36fa852f044283b5080ee20f9319465e2e7 Mon Sep 17 00:00:00 2001
From: esafar ~ c2h6 <77629339+ethan0905@users.noreply.github.com>
Date: Thu, 24 Nov 2022 15:28:25 +0100
Subject: [PATCH 06/21] Update README.md

---
 README.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/README.md b/README.md
index 9c8e02a..bbb71d2 100644
--- a/README.md
+++ b/README.md
@@ -22,7 +22,7 @@ We never gonna interact with the contract.
   
 ## ✅ Solution
 #### How did you resolve this issue?  
-→ We decided to solve this issue, by creating an easy to use and decentralized payement protocol service that protect the 2 users during transaction.  
+→ We decided to solve this issue, by creating an easy to use and decentralized payement protocol service that protect the 2 users during transaction (service-for-money).  
 → For each mission, we create a unique smart contract that is not editable and non replicable.  
 → We store the documents on decentralised database (IPFS).
   

From c5386cf227609385d9290f546925456936b5eed5 Mon Sep 17 00:00:00 2001
From: esafar ~ c2h6 <77629339+ethan0905@users.noreply.github.com>
Date: Thu, 24 Nov 2022 15:33:47 +0100
Subject: [PATCH 07/21] Update README.md

---
 README.md | 10 ++++++----
 1 file changed, 6 insertions(+), 4 deletions(-)

diff --git a/README.md b/README.md
index bbb71d2..935b0ab 100644
--- a/README.md
+++ b/README.md
@@ -18,7 +18,6 @@ We are 4 students from 42 school and we have been experiencing issues with our c
 #### How does it fit into the theme "Building a Decentralized Future"?  
 The solution is independant, self governing.  
 We never gonna interact with the contract.
-
   
 ## ✅ Solution
 #### How did you resolve this issue?  
@@ -58,8 +57,10 @@ IPFS for the decentralised datastorage
 
 ## Business model
 
-pas besoin de bcp de personnes (peu couteux)
-ajout differents type de contracts -> toucher une plus grande audience 
+For each contract, we take a pourcentage of the total amount (6%)  
+
+pas besoin de bcp de personnes (peu couteux)  
+ajout differents type de contracts -> toucher une plus grande audience  
 
 ## 🧭 Roadmap
 
@@ -75,7 +76,8 @@ ajout differents type de contracts -> toucher une plus grande audience
     - [ ] Interaction with Smart contract at {address} on {network}
 
 ## Development perspective
-Create a DAO, 
+Create a DAO,  
+Create our coin, the more user is holding, the less the additionnal fees gonna be 
 
 ## ⚠️ License
 Distributed under the MIT License. See `LICENSE.txt` for more information.  

From 9fe1e258ecd39e99b7bd4a7b5fcabf28b8684f87 Mon Sep 17 00:00:00 2001
From: esafar ~ c2h6 <77629339+ethan0905@users.noreply.github.com>
Date: Thu, 24 Nov 2022 15:37:49 +0100
Subject: [PATCH 08/21] Update README.md

---
 README.md | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/README.md b/README.md
index 935b0ab..526d5dd 100644
--- a/README.md
+++ b/README.md
@@ -11,9 +11,9 @@ We are 4 students from 42 school and we have been experiencing issues with our c
 
 ## ❗ Problem
 #### What problem does your project solve? 
-- Contract distortion
-- Deadline for payement not respected
-- Wrong amount
+1. Contract falsification  
+2. Deadline for payement not respected  
+3. Terms of contract not respected  
   
 #### How does it fit into the theme "Building a Decentralized Future"?  
 The solution is independant, self governing.  

From 10eba84e2ef6ace521d5f41bae4f58ab9129fb59 Mon Sep 17 00:00:00 2001
From: esafar ~ c2h6 <77629339+ethan0905@users.noreply.github.com>
Date: Thu, 24 Nov 2022 15:46:29 +0100
Subject: [PATCH 09/21] Update README.md

---
 README.md | 12 +++++++-----
 1 file changed, 7 insertions(+), 5 deletions(-)

diff --git a/README.md b/README.md
index 526d5dd..56daacb 100644
--- a/README.md
+++ b/README.md
@@ -17,17 +17,19 @@ We are 4 students from 42 school and we have been experiencing issues with our c
   
 #### How does it fit into the theme "Building a Decentralized Future"?  
 The solution is independant, self governing.  
-We never gonna interact with the contract.
-  
+    
 ## ✅ Solution
 #### How did you resolve this issue?  
 → We decided to solve this issue, by creating an easy to use and decentralized payement protocol service that protect the 2 users during transaction (service-for-money).  
-→ For each mission, we create a unique smart contract that is not editable and non replicable.  
+→ For each mission, we create a unique smart contract that is not editable and not replicable.  
 → We store the documents on decentralised database (IPFS).
   
-We create a trust environment for every users.  
+We create a climate of trust for every users (Open Trust Framework Model).  
   
-#### What technologies did you use?  
+#### What technologies did you use?
+Escalidraw for project diagram  
+Figma to design and prototype the website  
+Trello to manage the project development  
 TailwindCSS and ReactJS for frontend and backend  
 Starton API for the smart contracts managements
 IPFS for the decentralised datastorage  

From 37c03eede8939223fca940024245b547bc8e070e Mon Sep 17 00:00:00 2001
From: esafar ~ c2h6 <77629339+ethan0905@users.noreply.github.com>
Date: Thu, 24 Nov 2022 15:57:08 +0100
Subject: [PATCH 10/21] Update README.md

---
 README.md | 3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)

diff --git a/README.md b/README.md
index 56daacb..cddce7e 100644
--- a/README.md
+++ b/README.md
@@ -35,7 +35,8 @@ Starton API for the smart contracts managements
 IPFS for the decentralised datastorage  
   
 #### What was your biggest technical challenge and how does your solution solve it?
-?
+We never worked on Web3 before, so the biggest technical challenge was to give user the ability to write his own smart contract without knowledge.  
+Our solution solve it by creating a form interface to write directly into our smart contract.  
 
 ## ⚙️ How to run the project ? 
   

From d0666be616a8f27d7ea3b72277122eae8230a69e Mon Sep 17 00:00:00 2001
From: esafar ~ c2h6 <77629339+ethan0905@users.noreply.github.com>
Date: Thu, 24 Nov 2022 15:58:03 +0100
Subject: [PATCH 11/21] Update README.md

---
 README.md | 3 +--
 1 file changed, 1 insertion(+), 2 deletions(-)

diff --git a/README.md b/README.md
index cddce7e..4897e71 100644
--- a/README.md
+++ b/README.md
@@ -36,12 +36,11 @@ IPFS for the decentralised datastorage
   
 #### What was your biggest technical challenge and how does your solution solve it?
 We never worked on Web3 before, so the biggest technical challenge was to give user the ability to write his own smart contract without knowledge.  
-Our solution solve it by creating a form interface to write directly into our smart contract.  
+Our solution solve it by creating a form interface that write directly into our smart contract.  
 
 ## ⚙️ How to run the project ? 
   
 1. Clone the repository:  
-`git clone https://github.com/ethan0905/hackathon.git`
  
 2. Run at the root of repository, the following bash commands:  
 `docker-compose up --build`

From 6a3c3495b060d49b436bd98ebd0812a8117b279d Mon Sep 17 00:00:00 2001
From: esafar ~ c2h6 <77629339+ethan0905@users.noreply.github.com>
Date: Thu, 24 Nov 2022 15:58:52 +0100
Subject: [PATCH 12/21] Update README.md

---
 README.md | 5 +++--
 1 file changed, 3 insertions(+), 2 deletions(-)

diff --git a/README.md b/README.md
index 4897e71..da53999 100644
--- a/README.md
+++ b/README.md
@@ -41,10 +41,11 @@ Our solution solve it by creating a form interface that write directly into our
 ## ⚙️ How to run the project ? 
   
 1. Clone the repository:  
- 
+`https://github.com/ethan0905/hackathon_merge.git`  
+  
 2. Run at the root of repository, the following bash commands:  
 `docker-compose up --build`
-    
+  
 3. Then go to the following url on internet:  
 `localhost:3000`  
   

From 5d6b8b9649240a4ca8c0c724c1e7ec1bf4d6cba9 Mon Sep 17 00:00:00 2001
From: esafar ~ c2h6 <77629339+ethan0905@users.noreply.github.com>
Date: Thu, 24 Nov 2022 15:59:20 +0100
Subject: [PATCH 13/21] Update README.md

---
 README.md | 9 ---------
 1 file changed, 9 deletions(-)

diff --git a/README.md b/README.md
index da53999..f14cd0b 100644
--- a/README.md
+++ b/README.md
@@ -49,15 +49,6 @@ Our solution solve it by creating a form interface that write directly into our
 3. Then go to the following url on internet:  
 `localhost:3000`  
   
-## Process
-
- - Docker
- - Metamask connection
- - Figma
- - Smartcontract
- - npm install react-ipfs-uploader
- - npm install ipfs -g (for ipfs)
-
 ## Business model
 
 For each contract, we take a pourcentage of the total amount (6%)  

From 511f35813d94f5202ae5ceb91252900825dc1b28 Mon Sep 17 00:00:00 2001
From: esafar ~ c2h6 <77629339+ethan0905@users.noreply.github.com>
Date: Thu, 24 Nov 2022 16:01:50 +0100
Subject: [PATCH 14/21] Update README.md

---
 README.md | 18 +++++++++---------
 1 file changed, 9 insertions(+), 9 deletions(-)

diff --git a/README.md b/README.md
index f14cd0b..1199970 100644
--- a/README.md
+++ b/README.md
@@ -20,19 +20,19 @@ The solution is independant, self governing.
     
 ## ✅ Solution
 #### How did you resolve this issue?  
-→ We decided to solve this issue, by creating an easy to use and decentralized payement protocol service that protect the 2 users during transaction (service-for-money).  
-→ For each mission, we create a unique smart contract that is not editable and not replicable.  
-→ We store the documents on decentralised database (IPFS).
+1. We decided to solve this issue, by creating an easy to use and decentralized payement protocol service that protect the 2 users during transaction (service-for-money).  
+2. For each mission, we create a unique smart contract that is not editable and not replicable.  
+3. We store the documents on decentralised database (IPFS).
   
 We create a climate of trust for every users (Open Trust Framework Model).  
   
 #### What technologies did you use?
-Escalidraw for project diagram  
-Figma to design and prototype the website  
-Trello to manage the project development  
-TailwindCSS and ReactJS for frontend and backend  
-Starton API for the smart contracts managements
-IPFS for the decentralised datastorage  
+- Escalidraw for project diagram  
+- Figma to design and prototype the website  
+- Trello to manage the project development  
+- TailwindCSS and ReactJS for frontend and backend  
+- Starton API for the smart contracts managements
+- IPFS for the decentralised datastorage  
   
 #### What was your biggest technical challenge and how does your solution solve it?
 We never worked on Web3 before, so the biggest technical challenge was to give user the ability to write his own smart contract without knowledge.  

From 8b97c974ece97515bb6725d2c423f83c2300cf53 Mon Sep 17 00:00:00 2001
From: esafar ~ c2h6 <77629339+ethan0905@users.noreply.github.com>
Date: Thu, 24 Nov 2022 16:03:37 +0100
Subject: [PATCH 15/21] Update README.md

---
 README.md | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/README.md b/README.md
index 1199970..3e2ad2c 100644
--- a/README.md
+++ b/README.md
@@ -49,7 +49,7 @@ Our solution solve it by creating a form interface that write directly into our
 3. Then go to the following url on internet:  
 `localhost:3000`  
   
-## Business model
+## 📈 Business model
 
 For each contract, we take a pourcentage of the total amount (6%)  
 
@@ -69,7 +69,7 @@ ajout differents type de contracts -> toucher une plus grande audience
 - [ ] Form:
     - [ ] Interaction with Smart contract at {address} on {network}
 
-## Development perspective
+## 🖥️ Development perspective
 Create a DAO,  
 Create our coin, the more user is holding, the less the additionnal fees gonna be 
 

From d105681a15231ff0a88ca16cf41414a520d9bd17 Mon Sep 17 00:00:00 2001
From: esafar ~ c2h6 <77629339+ethan0905@users.noreply.github.com>
Date: Thu, 24 Nov 2022 16:08:51 +0100
Subject: [PATCH 16/21] Update README.md

---
 README.md | 5 +++--
 1 file changed, 3 insertions(+), 2 deletions(-)

diff --git a/README.md b/README.md
index 3e2ad2c..22830a7 100644
--- a/README.md
+++ b/README.md
@@ -7,8 +7,9 @@
 </div>
 
 ## 🤏 Pitch
-We are 4 students from 42 school and we have been experiencing issues with our client payement. We create this projet to solve this with a smart contract store on a blockchain !
-
+We are 4 students from 42 school and we have been experiencing issues with our client payement (deadline, terms of contract, ...).  
+We thought that using blockchain technology to solve this problem was an interesting idea.  
+  
 ## ❗ Problem
 #### What problem does your project solve? 
 1. Contract falsification  

From 6e530f3a253218a29ef2a3d44754f1fc6d2a55ca Mon Sep 17 00:00:00 2001
From: esafar ~ c2h6 <77629339+ethan0905@users.noreply.github.com>
Date: Thu, 24 Nov 2022 16:10:43 +0100
Subject: [PATCH 17/21] Update README.md

---
 README.md | 18 +++++++++++++++++-
 1 file changed, 17 insertions(+), 1 deletion(-)

diff --git a/README.md b/README.md
index 22830a7..8a514c7 100644
--- a/README.md
+++ b/README.md
@@ -9,7 +9,23 @@
 ## 🤏 Pitch
 We are 4 students from 42 school and we have been experiencing issues with our client payement (deadline, terms of contract, ...).  
 We thought that using blockchain technology to solve this problem was an interesting idea.  
-  
+ 
+## Sommaire
+
+ - [❗ Problem](#❗ Problem)
+ - [Comment fonctionne GIT](#comment-fonctionne-git)
+ - [Sécurité](#sécurité)
+ - [Inscription GitLab](#inscription)
+ - [Créer un projet](#créer-un-projet)
+ - [Fourcher (forker) un projet](#fourcher-forker-un-projet)
+ - [Gestion des fichiers](#gestion-des-fichiers)
+ - [Demandes de fusion](#demandes-de-fusion)
+ - [Le format Markdown](#am%C3%A9liorer-ses-textes-avec-le-format-markdown)
+ - [Gestion des issues](#les-issues)
+ - [FAQ](#faq)
+ - [Liens](#liens)
+ - [Glossaire](#glossaire)
+ 
 ## ❗ Problem
 #### What problem does your project solve? 
 1. Contract falsification  

From ca90144ac344f1f48929d6b6aa24df33fd43c17b Mon Sep 17 00:00:00 2001
From: esafar ~ c2h6 <77629339+ethan0905@users.noreply.github.com>
Date: Thu, 24 Nov 2022 16:11:06 +0100
Subject: [PATCH 18/21] Update README.md

---
 README.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/README.md b/README.md
index 8a514c7..157ff3d 100644
--- a/README.md
+++ b/README.md
@@ -12,7 +12,7 @@ We thought that using blockchain technology to solve this problem was an interes
  
 ## Sommaire
 
- - [❗ Problem](#❗ Problem)
+ - [❗ Problem](#Problem)
  - [Comment fonctionne GIT](#comment-fonctionne-git)
  - [Sécurité](#sécurité)
  - [Inscription GitLab](#inscription)

From 68ddf85777731d3f89032b689e74dec3712b6993 Mon Sep 17 00:00:00 2001
From: esafar ~ c2h6 <77629339+ethan0905@users.noreply.github.com>
Date: Thu, 24 Nov 2022 16:12:00 +0100
Subject: [PATCH 19/21] Update README.md

---
 README.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/README.md b/README.md
index 157ff3d..a8c1777 100644
--- a/README.md
+++ b/README.md
@@ -12,7 +12,7 @@ We thought that using blockchain technology to solve this problem was an interes
  
 ## Sommaire
 
- - [❗ Problem](#Problem)
+ - [❗ Problem](#-problem)
  - [Comment fonctionne GIT](#comment-fonctionne-git)
  - [Sécurité](#sécurité)
  - [Inscription GitLab](#inscription)

From d376cae88c83e422ecabeffe8dbcdbb28bb145e7 Mon Sep 17 00:00:00 2001
From: esafar ~ c2h6 <77629339+ethan0905@users.noreply.github.com>
Date: Thu, 24 Nov 2022 16:16:52 +0100
Subject: [PATCH 20/21] Update README.md

---
 README.md | 20 +++++++-------------
 1 file changed, 7 insertions(+), 13 deletions(-)

diff --git a/README.md b/README.md
index a8c1777..2e71666 100644
--- a/README.md
+++ b/README.md
@@ -13,19 +13,13 @@ We thought that using blockchain technology to solve this problem was an interes
 ## Sommaire
 
  - [❗ Problem](#-problem)
- - [Comment fonctionne GIT](#comment-fonctionne-git)
- - [Sécurité](#sécurité)
- - [Inscription GitLab](#inscription)
- - [Créer un projet](#créer-un-projet)
- - [Fourcher (forker) un projet](#fourcher-forker-un-projet)
- - [Gestion des fichiers](#gestion-des-fichiers)
- - [Demandes de fusion](#demandes-de-fusion)
- - [Le format Markdown](#am%C3%A9liorer-ses-textes-avec-le-format-markdown)
- - [Gestion des issues](#les-issues)
- - [FAQ](#faq)
- - [Liens](#liens)
- - [Glossaire](#glossaire)
- 
+ - [✅ Solution](#-solution)
+ - [⚙️ How to run the project ?](#%EF%B8%8F-how-to-run-the-project-)
+ - [📈 Business model](#-business-model)
+ - [🧭 Roadmap](#-roadmap)
+ - [🖥️ Development perspective](#%EF%B8%8F-development-perspective)
+ - [⚠️ License](#%EF%B8%8F-license)
+  
 ## ❗ Problem
 #### What problem does your project solve? 
 1. Contract falsification  

From 526c50c84fa400fc1bbbc18ba05bd0bc7379d7ca Mon Sep 17 00:00:00 2001
From: esafar ~ c2h6 <77629339+ethan0905@users.noreply.github.com>
Date: Thu, 24 Nov 2022 16:19:38 +0100
Subject: [PATCH 21/21] Update README.md

---
 README.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/README.md b/README.md
index 2e71666..ae459ff 100644
--- a/README.md
+++ b/README.md
@@ -10,7 +10,7 @@
 We are 4 students from 42 school and we have been experiencing issues with our client payement (deadline, terms of contract, ...).  
 We thought that using blockchain technology to solve this problem was an interesting idea.  
  
-## Sommaire
+## 📔 Summary
 
  - [❗ Problem](#-problem)
  - [✅ Solution](#-solution)