tellor-io · krasi-georgiev · Dec 2, 2020 · Dec 2, 2020 · Dec 2, 2020 · Dec 2, 2020
diff --git a/docs/miner.md → docs/01_miner.md b/docs/miner.md → docs/01_miner.md
diff --git a/docs/the-guide.md → docs/02_the-guide.md b/docs/the-guide.md → docs/02_the-guide.md
diff --git a/docs/configuation.md → docs/03_configuation.md b/docs/configuation.md → docs/03_configuation.md
diff --git a/docs/contributing.md → docs/04_contributing.md b/docs/contributing.md → docs/04_contributing.md
@@ -29,7 +29,7 @@ method before making a change.
 The following section explains various suggestions and procedures to note during development.
 
 ### First Steps
-* Familiarizing yourself with our [coding style guidelines.](coding-style-guide.md).
+* Familiarizing yourself with our [coding style guidelines.](05_coding-style-guide.md).
 * Familiarizing yourself with the [Makefile](../Makefile) commands, for example, `build`, `format`, `test`, `lint`.
 `make help` will print all available commands with some description.
 
@@ -59,7 +59,7 @@ $ <Iterate your development>
 $ git push fork <your_PR_branch>
 ```
 
-1. If your change affects users (adds,removes or changes a feature) add the item to the [CHANGELOG](CHANGELOG.md).
+1. If your change affects users (adds,removes or changes a feature) add the item to the [CHANGELOG](08_CHANGELOG.md).
 1. Add e2e tests for new features and changes to functionality. Add unit tests for key components of the packages.
 1. A PR will me merged once the PR has been approved by at least one developer with write access.
 1. If you feel like your PR is waiting too long for a review, feel free to ping in the [Discord](https://discord.gg/n7drGjh) channel for a review!

diff --git a/docs/coding-style-guide.md → docs/05_coding-style-guide.md b/docs/coding-style-guide.md → docs/05_coding-style-guide.md
diff --git a/docs/miner-reference.md → docs/06_miner-reference.md b/docs/miner-reference.md → docs/06_miner-reference.md
diff --git a/docs/release-process.md → docs/07_release-process.md b/docs/release-process.md → docs/07_release-process.md
@@ -42,11 +42,11 @@ later follow-up.
 
 # Cutting a release
 
-## Update `CHANGELOG.md`
+## Update `08_CHANGELOG.md`
 Do this in a PR against `master` as this gives others the opportunity to chime in on the release and the changelog changes.
 
 Note:
-> that `CHANGELOG.md` should only document changes relevant to users of the project, including external API changes, performance improvements, and new features. Do not document changes of internal interfaces, code refactorings and clean-ups, changes to the build process, etc. People interested in these are asked to refer to the git history.
+> that `08_CHANGELOG.md` should only document changes relevant to users of the project, including external API changes, performance improvements, and new features. Do not document changes of internal interfaces, code refactorings and clean-ups, changes to the build process, etc. People interested in these are asked to refer to the git history.
 
 ## Draft the new release
 On `master` tag the current commit as a new release via the following commands:

diff --git a/docs/CHANGELOG.md → docs/08_CHANGELOG.md b/docs/CHANGELOG.md → docs/08_CHANGELOG.md
diff --git a/docs/disclaimer.md → docs/09_disclaimer.md b/docs/disclaimer.md → docs/09_disclaimer.md
diff --git a/docs/README.md b/docs/README.md
@@ -36,11 +36,11 @@ A list of all PSR's(pre specified requests) and the expected data can be found [
 
 
 ## Instructions for deployment
- - [Telliot Instructions](the-guide.md)
+ - [Telliot Instructions](02_the-guide.md)
 
 ## Contributing and building from source
 Contributions are very welcome!<br/>
-See our [contributing.md](contributing.md) for more information.
+See our [04_contributing.md](04_contributing.md) for more information.
 
 ## Run with Docker
 Available tags: https://hub.docker.com/u/tellor