diff --git a/README.md b/README.md
index c50f27b5..888de3c9 100644
--- a/README.md
+++ b/README.md
@@ -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
 
diff --git a/docs/orchestrator.md b/docs/orchestrator.md
index 6a9fdd48..fde97a0d 100644
--- a/docs/orchestrator.md
+++ b/docs/orchestrator.md
@@ -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