diff --git a/README.md b/README.md
index c2219214655d2749b9f9f33ae1e7215d5f283dea..7b9a105149c29b9ae7abec10d03a5d98437e1c9c 100644
--- a/README.md
+++ b/README.md
@@ -1,30 +1,31 @@
 SSH and GPG public keys for Tétras Libre collaborators
 
-# List GPG key : 
+# GPG
+gpg is use for pass
 
-`gpg --list-keys`
+## Creating gpg key
+`gpg --generate-key`
+follow diaglog
 
-# Edit confidence a key : 
-
-`gpg --edit-key <keyName>`
-
-# Change confidence :
-
-`trust`
+## Add key of Tétras Libre collaborators
+To import gpg key, use `gpg --import key.asc`. To import all key, go on GPG folder and use `gpg --import *`
 
+After that, you need to edit confidence of key. For this, use `gpg --edit-key <keyName>` and use `trust` command in gpp (gpg>trust)
 Answer the response to add the confidence `5 - ultimate`. Use `quit` to leave.
 
-# Check manually if key is valid for pass 
 
-- Clone pass repository 
-- `gpg -d /path/to/key/in/pass/key.gpg.
+# Pass
+## Check manually if key is valid for pass
+
+- Clone pass repository
+- `gpg -d /path/to/key/in/pass/key.gpg.``
 
-If the result is "No secret key", check in the pass repository if everything is ok : 
+If the result is "No secret key", check in the pass repository if everything is ok :
 - Last version of the repo (in case of force push)
-- Use QTPass or cli to add concerned key 
+- Use QTPass or cli to add concerned key
 
-# Add new key on pass
+## Add new key on pass
 
-- Pull the repo 
-- Add the new public GPG in your gpg `gpg --import publickey.asc`
-- Check if Pass(QTPass) is set to encrypt passwords with the new key in addition of the existing 
+- Pull the repo
+- Add the new public GPG in your gpg
+- Check if Pass(QTPass) is set to encrypt passwords with the new key in addition of the existing