From 81cca02906a61ab13fa6bf426d96bf898b56440f Mon Sep 17 00:00:00 2001
From: yann300 <yann.levreau@gmail.com>
Date: Wed, 25 Jul 2018 11:40:38 +0200
Subject: [PATCH 1/4] no uppercase

---
 docs/run_tab.md | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/docs/run_tab.md b/docs/run_tab.md
index f13fb6591f..3d11f12882 100644
--- a/docs/run_tab.md
+++ b/docs/run_tab.md
@@ -63,8 +63,8 @@ shows it in a pending mode. When transaction is mined the number of
 pending transactions is updated and the transaction is added to the log
 (see ../terminal)
 
-USING ABI
----------
+Using the ABI
+------------
 
 Using `Deploy` or `At Address` is a classic use case of Remix. It is
 possible though to interact with a contract by using its ABI. The ABI is
@@ -76,7 +76,7 @@ next to `At Address`, put the Address of the contract you want to
 interact with. Click on `At Address`, a new "connection" with the
 contract will popup below.
 
-USING THE RECORDER
+Using the Recorder
 ------------------
 
 The Recorder allows to save a bunch of transactions in a JSON file and

From 2a3e99b3048a33b25491c60712481d27ac9ff7c1 Mon Sep 17 00:00:00 2001
From: yann300 <yann.levreau@gmail.com>
Date: Wed, 25 Jul 2018 11:40:48 +0200
Subject: [PATCH 2/4] add contract metadata docs

---
 docs/contract_metadata.md | 26 ++++++++++++++++++++++++++
 docs/index.rst            |  1 +
 2 files changed, 27 insertions(+)
 create mode 100644 docs/contract_metadata.md

diff --git a/docs/contract_metadata.md b/docs/contract_metadata.md
new file mode 100644
index 0000000000..196bb1e870
--- /dev/null
+++ b/docs/contract_metadata.md
@@ -0,0 +1,26 @@
+Contract Metadata
+=================
+
+As compilation succeed Remix create a JSON file for each compiled contract.
+These JSON files contains several metadata
+
+Library Deployment
+------------------
+
+By default Remix automatically deploy needed libraries.
+
+`linkReferences` contains a map representing libraries which depend on the current contract. 
+Values are addresses of libraries used for linking the contract.
+
+`autoDeployLib` defines if the libraries should be auto deployed by Remix or if the contract should be linked with libraries described in `linkReferences`
+
+```
+{
+	"linkReferences": {
+		"browser/Untitled.sol": {
+			"lib": "0x8c1ed7e19abaa9f23c476da86dc1577f1ef401f5"
+		}
+	},
+	"autoDeployLib": false
+}
+```
diff --git a/docs/index.rst b/docs/index.rst
index 10e3b25db9..6f9d760a30 100644
--- a/docs/index.rst
+++ b/docs/index.rst
@@ -43,6 +43,7 @@ Userful links:
 
    run_tab
    udapp
+   contract_metadata
 
 .. toctree::
    :maxdepth: 2

From e9eba1a394d5cc7d6bc72f791998209020025b63 Mon Sep 17 00:00:00 2001
From: yann300 <yann.levreau@gmail.com>
Date: Fri, 27 Jul 2018 14:11:31 +0200
Subject: [PATCH 3/4] Update contract_metadata.md

---
 docs/contract_metadata.md | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/docs/contract_metadata.md b/docs/contract_metadata.md
index 196bb1e870..763c5deee1 100644
--- a/docs/contract_metadata.md
+++ b/docs/contract_metadata.md
@@ -1,5 +1,5 @@
-Contract Metadata
-=================
+Build Artifact
+==============
 
 As compilation succeed Remix create a JSON file for each compiled contract.
 These JSON files contains several metadata

From 8e89385d05e78ef0195853627c54e383a72da111 Mon Sep 17 00:00:00 2001
From: yann300 <yann.levreau@gmail.com>
Date: Fri, 27 Jul 2018 15:29:24 +0200
Subject: [PATCH 4/4] Update contract_metadata.md

---
 docs/contract_metadata.md | 53 +++++++++++++++++++++++++++++++++++----
 1 file changed, 48 insertions(+), 5 deletions(-)

diff --git a/docs/contract_metadata.md b/docs/contract_metadata.md
index 763c5deee1..4806e30cd3 100644
--- a/docs/contract_metadata.md
+++ b/docs/contract_metadata.md
@@ -14,13 +14,56 @@ Values are addresses of libraries used for linking the contract.
 
 `autoDeployLib` defines if the libraries should be auto deployed by Remix or if the contract should be linked with libraries described in `linkReferences`
 
+Note that Remix will resolve addresses corresponding to the current network.
+By default, a configuration key follow the form: `<network_name>:<networkd_id>`, but it is also possible
+to define `<network_name>` or `<network_id>` as keys.
+
 ```
 {
-	"linkReferences": {
-		"browser/Untitled.sol": {
-			"lib": "0x8c1ed7e19abaa9f23c476da86dc1577f1ef401f5"
-		}
+	"VM:-": {
+		"linkReferences": {
+			"browser/Untitled.sol": {
+				"lib": "<address>",
+				"lib2": "<address>"
+			}
+		},
+		"autoDeployLib": true
+	},
+	"main:1": {
+		"linkReferences": {
+			"browser/Untitled.sol": {
+				"lib": "<address>",
+				"lib2": "<address>"
+			}
+		},
+		"autoDeployLib": true
+	},
+	"ropsten:3": {
+		"linkReferences": {
+			"browser/Untitled.sol": {
+				"lib": "<address>",
+				"lib2": "<address>"
+			}
+		},
+		"autoDeployLib": true
+	},
+	"rinkeby:4": {
+		"linkReferences": {
+			"browser/Untitled.sol": {
+				"lib": "<address>",
+				"lib2": "<address>"
+			}
+		},
+		"autoDeployLib": true
 	},
-	"autoDeployLib": false
+	"kovan:42": {
+		"linkReferences": {
+			"browser/Untitled.sol": {
+				"lib": "<address>",
+				"lib2": "<address>"
+			}
+		},
+		"autoDeployLib": true
+	}
 }
 ```