summary refs log tree commit diff
path: root/develop/upgrade.html
diff options
context:
space:
mode:
authorerikjohnston <erikjohnston@users.noreply.github.com>2024-03-14 13:55:46 +0000
committererikjohnston <erikjohnston@users.noreply.github.com>2024-03-14 13:55:46 +0000
commit85932e2c09eb8675f6e32d93f9c08dd97c42d225 (patch)
tree5a7214132e6a14e59c54fa6c96cbda8b7548518c /develop/upgrade.html
parentdeploy: 1c1b0bfa778e32bf740469b0a86be55102bc01b4 (diff)
downloadsynapse-85932e2c09eb8675f6e32d93f9c08dd97c42d225.tar.xz
deploy: acc2f00ecaab073abd8bc386d0b4f0d8b30606ef
Diffstat (limited to 'develop/upgrade.html')
-rw-r--r--develop/upgrade.html6
1 files changed, 3 insertions, 3 deletions
diff --git a/develop/upgrade.html b/develop/upgrade.html
index e86e58a293..55facd9bf2 100644
--- a/develop/upgrade.html
+++ b/develop/upgrade.html
@@ -244,11 +244,11 @@ dpkg -i matrix-synapse-py3_1.3.0+stretch1_amd64.deb
 </code></pre>
 </li>
 </ul>
-<p>Generally Synapse database schemas are compatible across multiple versions, once
-a version of Synapse is deployed you may not be able to rollback automatically.
+<p>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.</p>
 <table><thead><tr><th>Versions</th><th>Compatible version</th></tr></thead><tbody>
 <tr><td>v1.0.0 – v1.2.1</td><td>v1.0.0</td></tr>