From 67408fd860ced8304b6117e748fba7b454852e21 Mon Sep 17 00:00:00 2001
From: "fuder.eth" <139509124+vtjl10@users.noreply.github.com>
Date: Sun, 15 Dec 2024 13:52:38 +0100
Subject: [PATCH] Update README.md

---
 docs/movement-node/run/ansible/follower-node/README.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/docs/movement-node/run/ansible/follower-node/README.md b/docs/movement-node/run/ansible/follower-node/README.md
index ab3d48369..fe77fc4d6 100644
--- a/docs/movement-node/run/ansible/follower-node/README.md
+++ b/docs/movement-node/run/ansible/follower-node/README.md
@@ -8,7 +8,7 @@ By running the a Follower Node locally, you will be able to gauge the performanc
 - 2 TB SSD w/ 60K IOPS and 200 MiB/s throughput
 
 ## Running a Movement Node on Follower Node
-You can join any sufficiently upgraded network as a Folloewr Node by running a Movement Node with container tags specified to latest commit hash on this branch, the [`follower`](../../../../../docker/compose/movement-full-node/docker-compose.follower.yml) overlay. 
+You can join any sufficiently upgraded network as a Follower Node by running a Movement Node with container tags specified to latest commit hash on this branch, the [`follower`](../../../../../docker/compose/movement-full-node/docker-compose.follower.yml) overlay. 
 
 **Note**: the scripts provided herein have hardcoded constants for the Movement Testnet. You will need to change these to match the environment you are running on.