Skip to content

Commit

Permalink
Fix: typo
Browse files Browse the repository at this point in the history
  • Loading branch information
@omahs @VanBarbascu
omahs authored and VanBarbascu committed Nov 2, 2023
1 parent e60192e commit 3a2da81
Showing 1 changed file with 1 addition and 1 deletion.
2 changes: 1 addition & 1 deletion docs/practices/protocol_upgrade.md
View file
Original file line number Diff line number Diff line change
Expand Up @@ -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
Expand Down

0 comments on commit 3a2da81

Please sign in to comment.