From d0f8fbdc27300a101b8d614763ff046b79f4b07e Mon Sep 17 00:00:00 2001
From: erikjohnston <erikjohnston@users.noreply.github.com>
Date: Tue, 2 Apr 2024 17:46:21 +0000
Subject: deploy: ca27b516656223150d218bdd838df302fedf838c

---
 latest/upgrade.html | 8 ++++----
 1 file changed, 4 insertions(+), 4 deletions(-)

(limited to 'latest/upgrade.html')

diff --git a/latest/upgrade.html b/latest/upgrade.html
index c8151df8e2..afb890b7b6 100644
--- a/latest/upgrade.html
+++ b/latest/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>
@@ -266,7 +266,7 @@ v1.61.0.</p>
 <tr><td>v1.83.0 – v1.84.1</td><td>v1.77.0</td></tr>
 <tr><td>v1.85.0 – v1.91.2</td><td>v1.83.0</td></tr>
 <tr><td>v1.92.0 – v1.97.0</td><td>v1.90.0</td></tr>
-<tr><td>v1.98.0 – v1.103.0</td><td>v1.96.0</td></tr>
+<tr><td>v1.98.0 – v1.104.0</td><td>v1.96.0</td></tr>
 </tbody></table>
 <h2 id="upgrading-from-a-very-old-version"><a class="header" href="#upgrading-from-a-very-old-version">Upgrading from a very old version</a></h2>
 <p>You need to read all of the upgrade notes for each version between your current
-- 
cgit 1.5.1