diff --git a/doc/admin/index.rst b/doc/admin/index.rst
index 67598bd307..f60d61b703 100644
--- a/doc/admin/index.rst
+++ b/doc/admin/index.rst
@@ -9,6 +9,7 @@ This documentation is for everyone who wants to install pretix on a server.
    :maxdepth: 2
 
    installation/index
+   updates
    config
    maintainance
    scaling
diff --git a/doc/admin/installation/docker_smallscale.rst b/doc/admin/installation/docker_smallscale.rst
index 3458ca0d48..6fe0250900 100644
--- a/doc/admin/installation/docker_smallscale.rst
+++ b/doc/admin/installation/docker_smallscale.rst
@@ -256,6 +256,8 @@ create an event and start selling tickets!
 
 You should probably read :ref:`maintainance` next.
 
+.. _`docker_updates`:
+
 Updates
 -------
 
@@ -271,6 +273,8 @@ Restarting the service can take a few seconds, especially if the update requires
 Replace ``stable`` above with a specific version number like ``1.0`` or with ``latest`` for the development
 version, if you want to.
 
+Make sure to also read :ref:`update_notes` and the release notes of the version you are updating to.
+
 .. _`docker_plugininstall`:
 
 Install a plugin
diff --git a/doc/admin/installation/manual_smallscale.rst b/doc/admin/installation/manual_smallscale.rst
index d2f5c1184c..c4331fac0d 100644
--- a/doc/admin/installation/manual_smallscale.rst
+++ b/doc/admin/installation/manual_smallscale.rst
@@ -280,6 +280,8 @@ create an event and start selling tickets!
 
 You should probably read :ref:`maintainance` next.
 
+.. _`manual_updates`:
+
 Updates
 -------
 
@@ -294,6 +296,7 @@ To upgrade to a new pretix release, pull the latest code changes and run the fol
     (venv)$ python -m pretix updatestyles
     # systemctl restart pretix-web pretix-worker
 
+Make sure to also read :ref:`update_notes` and the release notes of the version you are updating to.
 
 .. _`manual_plugininstall`:
 
diff --git a/doc/admin/maintainance.rst b/doc/admin/maintainance.rst
index dff57e3085..b692f564f2 100644
--- a/doc/admin/maintainance.rst
+++ b/doc/admin/maintainance.rst
@@ -9,6 +9,8 @@ If you host your own pretix instance, you also need to care about the availabili
 of your service and the safety of your data yourself. This page gives you some
 information that you might need to do so properly.
 
+.. _`backups`:
+
 Backups
 -------
 
diff --git a/doc/spelling_wordlist.txt b/doc/spelling_wordlist.txt
index 1eba34fad5..1edaa40763 100644
--- a/doc/spelling_wordlist.txt
+++ b/doc/spelling_wordlist.txt
@@ -17,6 +17,7 @@ bic
 BIC
 boolean
 booleans
+bugfix
 cancelled
 casted
 Ceph
@@ -77,6 +78,7 @@ mixin
 mixins
 multi
 multidomain
+multiplicator
 namespace
 namespaced
 namespaces
diff --git a/src/pretix/base/models/orders.py b/src/pretix/base/models/orders.py
index 09cdca1ed9..599affa3da 100644
--- a/src/pretix/base/models/orders.py
+++ b/src/pretix/base/models/orders.py
@@ -2392,7 +2392,7 @@ class Transaction(models.Model):
     the "other side" of the relationship, i.e. how much of the financial obligation has been met so far.
 
     However, while ``OrderPayment`` and ``OrderRefund`` objects are "final" and no longer change once they reached their
-    final state, ``Order``, ``OrderPosition`` and ``OrderFee`` are highly mutable and can chane at any time, e.g. if
+    final state, ``Order``, ``OrderPosition`` and ``OrderFee`` are highly mutable and can change at any time, e.g. if
     the customer moves their booking to a different day or a discount is applied retroactively.
 
     Therefore those models can be used to answer the question "how many tickets of type X have been sold for my event