diff --git a/docs/proxy/description.md b/docs/proxy/description.md
index db12c53c8b186a60e141ba3f89aa7e8730650f8a..7a7caae185d250b647e7730b1369bcdb80070109 100644
--- a/docs/proxy/description.md
+++ b/docs/proxy/description.md
@@ -1,17 +1,17 @@
 !!! warning ""
     :construction: Section under Construction :construction:
 
-This section of documentation refers to the Enedis Oauth protocol working hand in hand with our custom proxy and the cozy-stack.
-To fully understand its whereabouts, you should also look at the [enedis konnector](./konnectors/enedis.md) documentation.
+This section of documentation refers to the Oauth protocols working hand in hand with our custom proxy and the cozy-stack.
+To fully understand its whereabouts, you should also look at the [enedis konnector](../konnectors/enedis.md) and [grdf konnector](../konnectors/grdf.md) documentation.
 
 !!! info "proxy code source"
     Feel free to check the proxy [code](https://forge.grandlyon.com/pocs/cozy/cozy-oauth-proxy) at all time when reading this documentation.
 
 ## Oauth Dance
 
-In order to access customer data from Ecolyo, one must first obtain customer authorization. This authorization is materialized by an access token and it must be obtained by the Authorization API exposed by Enedis.
+In order for Ecolyo to access customer data, one must first obtain customer authorization. This authorization is materialized by an access token and it must be obtained by the APIs exposed by each energy providers.
 
-The API is implemented on Oauth 2.0 protocol, it requires authentication from the customer along with its given consent.
+These APIs implement Oauth 2.0 protocol, it requires authentication from the customer along with its given consent.
 
 ### Enedis Data Connect
 
@@ -30,7 +30,7 @@ Regarding Enedis, two endpoints are exposed:
   </colgroup>
   <thead>
     <tr class="header">
-      <th>Name</th>
+      <th>Paramater</th>
       <th>Description</th>
     </tr>
   </thead>
@@ -66,7 +66,7 @@ Regarding Enedis, two endpoints are exposed:
   </colgroup>
   <thead>
     <tr class="header">
-      <th>Name</th>
+      <th>Paramater</th>
       <th>Description</th>
     </tr>
   </thead>
@@ -106,6 +106,8 @@ On success, response will contain **access_token** or **refresh_token**, **usage
 
 ### Grdf Adict
 
+#### /access_token
+
 ### Cozy Oauth Protocol
 
 !!! info "cozy oauth flow documentation" 
@@ -113,10 +115,10 @@ On success, response will contain **access_token** or **refresh_token**, **usage
 
 #### Couchdb
 
-It is necessary to add in a couchdb database all informations needed for the konnector authentication to work properly.
+The couchdb database must hold all informations needed for the konnector authentication to work properly.
 
 Auth informations are stored in the **secrets/io-cozy-account_types** database.
-You can create manually the document by entering these parameters:
+You can create manually the document by entering these parameters for each konnector:
 
 <table>
   <colgroup>
@@ -186,13 +188,13 @@ Exemple:
 
 #### Result
 
-With that in mind, the proxy is now the one calling the auth and token endpoints. It's also the proxy that is registered as redirect_uri.
+With that in mind, the proxy is now the one calling the auth and token provider endpoints. The instance name will be contained in redirect_uri, the stack will insert this parameters by itself in the /auth call.
 
 3 endpoints are created in the proxy:
 
-- One for the auth (called by the cozy-stack)
-- One for the token (also called by the cozy-stack)
-- One for the redirect_uri (called by the service provider)
+- One for the auth
+- One for the token
+- One for the redirect
 
 #### Proxy flow
 
@@ -210,11 +212,17 @@ It is composed of three endpoints as seen above. The first endpoint to be called
 
 #### auth
 
-Originally called from a cozy-stack trying to setup its konnector. The proxy gets this informations from the query:
+Originally called from a cozy-stack trying to setup its konnector. The proxy gets these informations from the query:
 
-- clientId
+- client_id
+- duration
+- redirect_uri (auto inserted by the cozy-stack, except if you specify **skip_redirect_uri:true** in the couchdb)
+- response_type
 - state (as it was conceived by the cozy-stack)
-- redirect_uri (**will be used later to trace back the stack**)
+
+![auth_params](enedis-auth-params.png)
+
+The state will be merged with the instance name, then decomposed again when reaching /redirect. This way the proxy is able to keep track of the cozy instance originally calling.
 
 With all these informations, the proxy can contact the provider **/auth** endpoint to start the oauth dance.
 
@@ -240,6 +248,9 @@ Split the customed state that was modified in the **/auth** process. From this s
 
 Finally redirect all these parameters in a query to the cozy-stack (the cozy-stack which is still waiting for an answer from its /auth call).
 
+!!! warning "state / instance"
+    The state must be recovered without the instance name, otherwise the cozy-stack won't recognized it and the handshake will fail.
+
 #### token
 
 Gathering from query or parameters all params.
diff --git a/docs/proxy/enedis-auth-params.png b/docs/proxy/enedis-auth-params.png
new file mode 100644
index 0000000000000000000000000000000000000000..829d96e5eb9e0daac815eec8b1d68acb39120c76
Binary files /dev/null and b/docs/proxy/enedis-auth-params.png differ