Skip to content
This repository has been archived by the owner on Apr 15, 2024. It is now read-only.

Commit

Permalink
docs: markdownlint
Browse files Browse the repository at this point in the history
  • Loading branch information
rach-id committed Nov 25, 2023
1 parent b6ce9fc commit 91bed0a
Show file tree
Hide file tree
Showing 2 changed files with 2 additions and 2 deletions.
2 changes: 1 addition & 1 deletion README.md
Original file line number Diff line number Diff line change
Expand Up @@ -8,7 +8,7 @@ For a high-level overview of how Blobstream works, check [here](https://github.c

## Install

1. [Install Go](https://go.dev/doc/install) 1.21
1. [Install Go](https://go.dev/doc/install) 1.21
2. Clone this repo
3. Install the Blobstream CLI

Expand Down
2 changes: 1 addition & 1 deletion docs/orchestrator.md
Original file line number Diff line number Diff line change
Expand Up @@ -250,7 +250,7 @@ If, for some reason, the private key, corresponding to the EVM account that was
If the validator still has access to the previous running orchestrator, it would be safer to keep it running in a separate process, and initializing a new orchestrator in a new home directory, and running it using the new EVM address. Then, once the new orchestrator starts signing, the old one can be stopped.
Running a second orchestrator in the same machine would require using different P2P listening ports, i.e. changing the `listen-addr` value in the `<orchestrator_home>/config/config.toml` file and using different ports between the two instances.
Running a second orchestrator in the same machine would require using different P2P listening ports, i.e. changing the `listen-addr` value in the `<orchestrator_home>/config/config.toml` file and using different ports between the two instances.
#### Systemd service
Expand Down

0 comments on commit 91bed0a

Please sign in to comment.