1 test failed but should be minor issue

docs/root/source/contributing/cross-project-policies/code-of-conduct.md

@@ -1,6 +1,6 @@
 <!---
 Copyright © 2020 Interplanetary Database Association e.V.,
-Planetmint and IPDB software contributors.
+BigchainDB and IPDB software contributors.
 SPDX-License-Identifier: (Apache-2.0 AND CC-BY-4.0)
 Code is Apache-2.0 and docs are CC-BY-4.0
 --->

docs/root/source/contributing/cross-project-policies/python-style-guide.md

@@ -1,6 +1,6 @@
 <!---
 Copyright © 2020 Interplanetary Database Association e.V.,
-Planetmint and IPDB software contributors.
+BigchainDB and IPDB software contributors.
 SPDX-License-Identifier: (Apache-2.0 AND CC-BY-4.0)
 Code is Apache-2.0 and docs are CC-BY-4.0
 --->
@@ -13,7 +13,7 @@ This guide starts out with our general Python coding style guidelines and ends w
 
 Our starting point is [PEP8](https://www.python.org/dev/peps/pep-0008/), the standard "Style Guide for Python Code." Many Python IDEs will check your code against PEP8. (Note that PEP8 isn't frozen; it actually changes over time, but slowly.)
 
-Planetmint uses Python 3.5+, so you can ignore all PEP8 guidelines specific to Python 2.
+BigchainDB uses Python 3.5+, so you can ignore all PEP8 guidelines specific to Python 2.
 
 We use [pre-commit](http://pre-commit.com/) to check some of the rules below before every commit but not everything is realized yet.
 The hooks we use can be found in the [.pre-commit-config.yaml](https://github.com/bigchaindb/bigchaindb/blob/master/.pre-commit-config.yaml) file.
@@ -30,7 +30,7 @@ PEP8 says some things about docstrings, but not what to put in them or how to st
 
 PEP8 has some [maximum line length guidelines](https://www.python.org/dev/peps/pep-0008/#id17), starting with "Limit all lines to a maximum of 79 characters" but "for flowing long blocks of text with fewer structural restrictions (docstrings or comments), the line length should be limited to 72 characters."
 
-We discussed this at length, and it seems that the consensus is: _try_ to keep line lengths less than 79/72 characters, unless you have a special situation where longer lines would improve readability. (The basic reason is that 79/72 works for everyone, and Planetmint is an open source project.) As a hard limit, keep all lines less than 119 characters (which is the width of GitHub code review).
+We discussed this at length, and it seems that the consensus is: _try_ to keep line lengths less than 79/72 characters, unless you have a special situation where longer lines would improve readability. (The basic reason is that 79/72 works for everyone, and BigchainDB is an open source project.) As a hard limit, keep all lines less than 119 characters (which is the width of GitHub code review).
 
 ### Single or Double Quotes?
 

docs/root/source/contributing/cross-project-policies/release-process.md

@@ -1,6 +1,6 @@
 <!---
 Copyright © 2020 Interplanetary Database Association e.V.,
-Planetmint and IPDB software contributors.
+BigchainDB and IPDB software contributors.
 SPDX-License-Identifier: (Apache-2.0 AND CC-BY-4.0)
 Code is Apache-2.0 and docs are CC-BY-4.0
 --->
@@ -9,7 +9,7 @@ Code is Apache-2.0 and docs are CC-BY-4.0
 
 ## Notes
 
-Planetmint follows
+BigchainDB follows
 [the Python form of Semantic Versioning](https://packaging.python.org/tutorials/distributing-packages/#choosing-a-versioning-scheme)
 (i.e. MAJOR.MINOR.PATCH),
 which is almost identical
@@ -46,7 +46,7 @@ The following steps are what we do to release a new version of _BigchainDB Serve
    - In `bigchaindb/version.py`:
      - update `__version__` to e.g. `0.9.0` (with no `.dev` on the end)
      - update `__short_version__` to e.g. `0.9` (with no `.dev` on the end)
-   - In the docs about installing Planetmint (and Tendermint), and in the associated scripts, recommend/install a version of Tendermint that _actually works_ with the soon-to-be-released version of Planetmint. You can find all such references by doing a search for the previously-recommended version number, such as `0.31.5`.
+   - In the docs about installing BigchainDB (and Tendermint), and in the associated scripts, recommend/install a version of Tendermint that _actually works_ with the soon-to-be-released version of BigchainDB. You can find all such references by doing a search for the previously-recommended version number, such as `0.31.5`.
    - In `setup.py`, _maybe_ update the development status item in the `classifiers` list. For example, one allowed value is `"Development Status :: 5 - Production/Stable"`. The [allowed values are listed at pypi.python.org](https://pypi.python.org/pypi?%3Aaction=list_classifiers).
 
 2. **Wait for all the tests to pass!**
@@ -65,7 +65,7 @@ The following steps are what we do to release a new version of _BigchainDB Serve
    ```text
    sudo chown -R $(whoami):$(whoami) .
    ```
-10. [Log in to readthedocs.org](https://readthedocs.org/accounts/login/) and go to the **Planetmint Server** project, then:
+10. [Log in to readthedocs.org](https://readthedocs.org/accounts/login/) and go to the **BigchainDB Server** project, then:
    - Click on "Builds", select "latest" from the drop-down menu, then click the "Build Version:" button.
    - Wait for the build of "latest" to finish. This can take a few minutes.
    - Go to Admin --> Advanced Settings
@@ -98,4 +98,4 @@ The following steps are what we do to release a new version of _BigchainDB Serve
    - If the release is an Alpha, Beta or Release Candidate release,
      then click on the "Trigger" button for that tag as well.
 
-Congratulations, you have released a new version of Planetmint Server!
+Congratulations, you have released a new version of BigchainDB Server!