summary refs log tree commit diff
path: root/docs/upgrade.md
diff options
context:
space:
mode:
authorRichard van der Hoff <1389908+richvdh@users.noreply.github.com>2024-03-14 13:54:01 +0000
committerGitHub <noreply@github.com>2024-03-14 13:54:01 +0000
commitacc2f00ecaab073abd8bc386d0b4f0d8b30606ef (patch)
treef7194fff65664ef3627cd58d8551de3e33b94e4b /docs/upgrade.md
parentAdd query to update local cache of a remote user's device list to docs (#16892) (diff)
downloadsynapse-acc2f00ecaab073abd8bc386d0b4f0d8b30606ef.tar.xz
upgrade.md: fix grammatical errors (#16965)
comma splice
"rollback" is a noun
Diffstat (limited to 'docs/upgrade.md')
-rw-r--r--docs/upgrade.md6
1 files changed, 3 insertions, 3 deletions
diff --git a/docs/upgrade.md b/docs/upgrade.md
index 640fed3ae3..e7247676d1 100644
--- a/docs/upgrade.md
+++ b/docs/upgrade.md
@@ -88,11 +88,11 @@ process, for example:
     dpkg -i matrix-synapse-py3_1.3.0+stretch1_amd64.deb
     ```
 
-Generally Synapse database schemas are compatible across multiple versions, once
-a version of Synapse is deployed you may not be able to rollback automatically.
+Generally Synapse database schemas are compatible across multiple versions, but once
+a version of Synapse is deployed you may not be able to roll back automatically.
 The following table gives the version ranges and the earliest version they can
 be rolled back to. E.g. Synapse versions v1.58.0 through v1.61.1 can be rolled
-back safely to v1.57.0, but starting with v1.62.0 it is only safe to rollback to
+back safely to v1.57.0, but starting with v1.62.0 it is only safe to roll back to
 v1.61.0.
 
 <!-- REPLACE_WITH_SCHEMA_VERSIONS -->