Skip to content

Commit e3d05d8

Browse files
outoftardisappetrosyan
authored andcommitted
Fix formatting
Signed-off-by: Ekaterina Mekhnetsova <[email protected]>
1 parent fa9d610 commit e3d05d8

File tree

1 file changed

+12
-11
lines changed

1 file changed

+12
-11
lines changed

src/guide/advanced/running-iroha-on-bare-metal.md

+12-11
Original file line numberDiff line numberDiff line change
@@ -16,15 +16,16 @@ error-prone, particularly for exotic systems (Windows).
1616
## Prerequisites
1717

1818
First of all, we should note that we have only built the Iroha client so
19-
far in this tutorial. We also need to build the peer software to run Iroha on
20-
bare metal.
19+
far in this tutorial. We also need to build the peer software to run Iroha
20+
on bare metal.
2121

2222
::: info
2323

24-
Building in `debug` mode retains much more information and optimises the binary to a far lesser extent.
25-
As such, we advise you to build Iroha in `debug` mode for testing: it’s faster and it makes it easier for you to find issues and fix them. However, if
26-
you intend to actually deploy Iroha, you should build it in `--release`
27-
mode.
24+
Building in `debug` mode retains much more information and optimises the
25+
binary to a far lesser extent. As such, we advise you to build Iroha in
26+
`debug` mode for testing: it’s faster and it makes it easier for you to
27+
find issues and fix them. However, if you intend to actually deploy Iroha,
28+
you should build it in `--release` mode.
2829

2930
:::
3031

@@ -40,9 +41,9 @@ mode.
4041
cargo build --bin iroha --release
4142
```
4243

43-
The `release` mode binary takes significantly longer to compile than `debug` mode, but
44-
the result is a smaller and faster binary, suitable for deployment
45-
in the actual blockchains.
44+
The `release` mode binary takes significantly longer to compile than
45+
`debug` mode, but the result is a smaller and faster binary, suitable for
46+
deployment in the actual blockchains.
4647

4748
## Setup
4849

@@ -58,8 +59,8 @@ run all commands from that directory:
5859
cd ~/Git/iroha/configs/peer
5960
```
6061

61-
The third option is to specify the full path to the configuration file in an
62-
environment variable. For simplicity, we shall do the latter:
62+
The third option is to specify the full path to the configuration file in
63+
an environment variable. For simplicity, we shall do the latter:
6364

6465
```bash
6566
cd ~

0 commit comments

Comments
 (0)