From ec461eb4a42758f2d43d3ea8b7d8af98fcb01ec3 Mon Sep 17 00:00:00 2001
From: Josh Stein <46639943+jcstein@users.noreply.github.com>
Date: Thu, 14 Dec 2023 12:25:54 -0500
Subject: [PATCH 1/3] fix: update typo

---
 docs/bootstrapper.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/docs/bootstrapper.md b/docs/bootstrapper.md
index 8a97c7d2..a814e971 100644
--- a/docs/bootstrapper.md
+++ b/docs/bootstrapper.md
@@ -20,7 +20,7 @@ Before starting the bootstrapper, we will need to init the store:
 blobstream bootstrapper init
 ```
 
-By default, the store will be created un `~/.bootstrapper`. However,
+By default, the store will be created in `~/.bootstrapper`. However,
 if you want to specify a custom location, you can use the `--home` flag.
 Or, you can use the following environment variable:
 

From 8cf29b5799940f8ac4180ec501da65cac3609de0 Mon Sep 17 00:00:00 2001
From: Josh Stein <46639943+jcstein@users.noreply.github.com>
Date: Thu, 14 Dec 2023 15:28:36 -0500
Subject: [PATCH 2/3] chore: match docs 1332

---
 docs/orchestrator.md | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/docs/orchestrator.md b/docs/orchestrator.md
index ca61b599..e6986c58 100644
--- a/docs/orchestrator.md
+++ b/docs/orchestrator.md
@@ -155,7 +155,7 @@ To start the orchestrator in the default home directory, run the following:
 blobstream orchestrator start --evm.account 0x966e6f22781EF6a6A82BBB4DB3df8E225DfD9488
 ```
 
-> **_NOTE:_** The above command assumes that the necessary configuration is specified in the  `<orchestrator_home>/config/config.toml` file.
+> **_NOTE:_** The above command assumes that the necessary configuration is specified in the `<orchestrator_home>/config/config.toml` file.
 
 Then, you will be prompted to enter your EVM key passphrase so that the orchestrator can use it to sign attestations. Make sure that it's the EVM address that was provided when creating the validator. If not, then the orchestrator will not sign, and you will keep seeing a "validator not part of valset" warning message. If you see such message, first verify that your validator is part of the active validator set. If so, then probably the EVM address provided to the orchestrator is not the right one, and you should check which EVM address is registered to your validator. Check the [Register EVM Address](#register-evm-address) section for more information.
 
@@ -166,7 +166,7 @@ If you no longer have access to your EVM address, you could always edit your val
 #### `transport: authentication handshake failed`
 
 ```text
-rpc error: code = Unavailable desc = connection error: desc = "transport: authentication handshake failed: tls: first record does not look like a TLS handshake" 
+rpc error: code = Unavailable desc = connection error: desc = "transport: authentication handshake failed: tls: first record does not look like a TLS handshake"
 ```
 
 Seeing this error means that the orchestrator/relayer is trying to connect to a gRPC endpoint that is not secure. To bypass this, use the `--grpc.insecure` flag. However, we recommend using secure gRPC connections.

From eb7f7ba82c0899bd2d04b7693e897762145297e2 Mon Sep 17 00:00:00 2001
From: Josh Stein <46639943+jcstein@users.noreply.github.com>
Date: Thu, 14 Dec 2023 15:29:04 -0500
Subject: [PATCH 3/3] chore: match changes in docs 1332

---
 docs/relayer.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/docs/relayer.md b/docs/relayer.md
index aaeac28d..f71df695 100644
--- a/docs/relayer.md
+++ b/docs/relayer.md
@@ -118,6 +118,6 @@ To start the relayer using the default home directory, run the following:
 /bin/blobstream relayer start --evm.account=0x35a1F8CE94187E4b043f4D57548EF2348Ed556c8
 ```
 
-> **_NOTE:_** The above command assumes that the necessary configuration is specified in the  `<relayer_home>/config/config.toml` file.
+> **_NOTE:_** The above command assumes that the necessary configuration is specified in the `<relayer_home>/config/config.toml` file.
 
 Then, you will be prompted to enter your EVM key passphrase for the EVM address passed using the `--evm.account` flag, so that the relayer can use it to send transactions to the target Blobstream smart contract. Make sure that it's funded.