Skip to content
Snippets Groups Projects
Commit b4939e2c authored by Hernando Castano's avatar Hernando Castano Committed by Bastian Köcher
Browse files

Fix some nits (#988)


* This is art, not bash

* Remove unused HEALTH build argument

Co-authored-by: default avatarTomasz Drwięga <tomasz@parity.io>
parent 0261d1e3
Branches
No related merge requests found
......@@ -31,7 +31,7 @@ rustup target add wasm32-unknown-unknown --toolchain nightly
Once this is configured you can build and test the repo as follows:
```bash
```
git clone https://github.com/paritytech/parity-bridges-common.git
cd parity-bridges-common
cargo build --all
......@@ -49,7 +49,7 @@ and external processes called relayers. A bridge chain is one that is able to fo
of a foreign chain independently. For example, consider the case below where we want to bridge two
Substrate based chains.
```bash
```
+---------------+ +---------------+
| | | |
| Rialto | | Millau |
......@@ -77,7 +77,7 @@ Here's an overview of how the project is laid out. The main bits are the `node`,
"blockchain", the `modules` which are used to build the blockchain's logic (a.k.a the runtime) and
the `relays` which are used to pass messages between chains.
```bash
```
├── bin // Node and Runtime for the various Substrate chains
│ └── ...
├── deployments // Useful tools for deploying test networks
......
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment