From 3a2da813e9463f34f1131954abcb42f11485fbad Mon Sep 17 00:00:00 2001
From: omahs <73983677+omahs@users.noreply.github.com>
Date: Mon, 12 Jun 2023 17:05:35 +0200
Subject: [PATCH] Fix: typo

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

diff --git a/docs/practices/protocol_upgrade.md b/docs/practices/protocol_upgrade.md
index 618a1804b88..aab4857dec8 100644
--- a/docs/practices/protocol_upgrade.md
+++ b/docs/practices/protocol_upgrade.md
@@ -42,7 +42,7 @@ For mainnet releases, the release on github typically happens on a Monday or Tue
 typically happens a week later and the protocol version upgrade happens 1-2 epochs after the voting. This 
 gives the node maintainers enough time to upgrade their neard nodes. The node maintainers can upgrade
 their nodes at any time between the release and the voting but it is recommended to upgrade soon after the
-release. This is to accomodate for any database migrations or miscellaneous delays. 
+release. This is to accommodate for any database migrations or miscellaneous delays. 
 
 Starting a neard node with protocol version voting in the future in a network that is already operating 
 at that protocol version is supported as well. This is useful in the scenario where there is a mainnet