Renamed 2 files/pages of notes on running a node

docs/contributing/source/dev-setup-coding-and-contribution-process/index.rst

@@ -5,5 +5,5 @@ Developer Setup, Coding & Contribution Process
    :maxdepth: 2
 
    write-code
-   setup-dev-environment
-   vanshdeep-notes
+   run-node-with-docker-compose
+   run-node-as-processes

docs/contributing/source/dev-setup-coding-and-contribution-process/run-node-as-processes.md

@@ -1,4 +1,4 @@
-# Vanshdeep's Notes on Running a Local Dev Node as Processes
+# Notes on Running a Local Dev Node as Processes
 
 The following doc describes how to run a local node for developing BigchainDB Tendermint version.
 

docs/contributing/source/dev-setup-coding-and-contribution-process/write-code.rst

@@ -95,7 +95,7 @@ We like to test everything, if possible. Unit tests and also integration tests.
 framework to write Python tests. Read all about it.
 
 Most tests are in the ``tests/`` folder. Take a look around.
-
+https://github.com/bigchaindb/bigchaindb/pull/2156
 
 Running a Local Node for Dev and Test
 -------------------------------------
@@ -103,7 +103,7 @@ Running a Local Node for Dev and Test
 This is tricky and personal. Different people do it different ways. We documented some of those on separate pages:
 
 - `Dev node setup and running all tests with Docker Compose <setup-dev-environment.html>`_
-- `Dev node setup and running all tests as processes <vanshdeep-notes.html>`_
+- `Dev node setup and running all tests as processes <run-node-as-processes.html>`_
 - More to come?