diff --git a/content/en/admin/upgrading.md b/content/en/admin/upgrading.md
index 1ce883b5..296f3e4f 100644
--- a/content/en/admin/upgrading.md
+++ b/content/en/admin/upgrading.md
@@ -10,6 +10,16 @@ menu:
 When a new version of Mastodon comes out, it appears on the [GitHub releases page](https://github.com/mastodon/mastodon/releases). Please mind that running unreleased code from the `main` branch, while possible, is not recommended.
 {{< /hint >}}
 
+### Automatic update verification {#automated_checks}
+
+Since v4.2.0, Mastodon will automatically check for available updates and notify the users of your server that have the `DevOps` permission.
+
+This happens by fetching `https://api.joinmastodon.org/update-check?version=<current_version>` in the background every 30 minutes. `current_version` omits the build metadata (everything after the first `+`, if there is one, in the version string). For instance, if your version is `4.3.0-beta2+my-fork`, Mastodon will query `https://api.joinmastodon.org/update-check?version=4.3.0-beta2`.
+
+You can change which URL Mastodon queries by setting the `UPDATE_CHECK_URL` environment variable. You can also completely disable this behavior by setting this environment variable to an empty string, although we strongly recommend against doing that unless you are keeping up with Mastodon updates in another way, as Mastodon occasionally releases critical security updates that must be applied in a timely fashion.
+
+### Upgrade steps
+
 Mastodon releases correspond to git tags. Before attempting an upgrade, look up the desired release on the [GitHub releases page](https://github.com/mastodon/mastodon/releases). The page will contain a **changelog** describing everything you need to know about what's different, as well as **specific upgrade instructions**.
 
 To begin, switch to the `mastodon` user: