aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorAlex Auvolat <alex@adnab.me>2023-06-14 11:21:56 +0200
committerAlex Auvolat <alex@adnab.me>2023-06-14 11:21:56 +0200
commit3aadba724d0ed8e57fe98bf5f6b4cb998e0ee093 (patch)
treec52b6a13ed038782c8b1f7d26319c2298e78d1ed
parent5a186be363ca5225a40bb4ecffb97b342e840269 (diff)
downloadgarage-3aadba724d0ed8e57fe98bf5f6b4cb998e0ee093.tar.gz
garage-3aadba724d0ed8e57fe98bf5f6b4cb998e0ee093.zip
doc: english improvement
-rw-r--r--doc/book/cookbook/upgrading.md2
1 files changed, 1 insertions, 1 deletions
diff --git a/doc/book/cookbook/upgrading.md b/doc/book/cookbook/upgrading.md
index 9d60a988..64201994 100644
--- a/doc/book/cookbook/upgrading.md
+++ b/doc/book/cookbook/upgrading.md
@@ -58,7 +58,7 @@ From a high level perspective, a major upgrade looks like this:
### Major upgarades with minimal downtime
-There is only one operation that has to be coordinated cluster-wide: the passage of one version of the internal RPC protocol to the next.
+There is only one operation that has to be coordinated cluster-wide: the switch of one version of the internal RPC protocol to the next.
This means that an upgrade with very limited downtime can simply be performed from one major version to the next by restarting all nodes
simultaneously in the new version.
The downtime will simply be the time required for all nodes to stop and start again, which should be less than a minute.