diff --git a/docs/administration/CLI_tasks/frontend.md b/docs/administration/CLI_tasks/frontend.md
index 064534384..404d016ed 100644
--- a/docs/administration/CLI_tasks/frontend.md
+++ b/docs/administration/CLI_tasks/frontend.md
@@ -81,16 +81,16 @@ Careful: This folder will be completely replaced on installation.
 === "OTP"
 
     ```sh
-    ./bin/pleroma_ctl frontend install admin-fe --ref develop
+    ./bin/pleroma_ctl frontend install admin-fe --ref stable
     ```
 
 === "From Source"
 
     ```sh
-    mix pleroma.frontend install admin-fe --ref develop
+    mix pleroma.frontend install admin-fe --ref stable
     ```
 
-Builds come from the package registry: `https://git.pleroma.social/api/packages/pleroma/generic/admin-fe-builds/${ref}/latest.zip`. At the moment only `develop` is published. A `stable` branch or a release tag works as `--ref` once a build for it is published.
+Builds come from the package registry: `https://git.pleroma.social/api/packages/pleroma/generic/admin-fe-builds/${ref}/latest.zip`. `stable` and `develop` are published; `stable` is the better choice for production. A release tag works as `--ref` once a build for it is published.
 
 ## Example installation for an unknown frontend
 
diff --git a/docs/administration/frontends-management.md b/docs/administration/frontends-management.md
index 9b8bf2caf..9a3bec37d 100644
--- a/docs/administration/frontends-management.md
+++ b/docs/administration/frontends-management.md
@@ -56,7 +56,7 @@ Due to aforementioned bug, preferred way of installing frontends in AdminFE is b
 ![screenshot of admin-fe with instructions on how to install a frontend](../assets/way_to_install_frontends.png)
 and filling in the fields. Unfortunately AdminFE does not provide the raw data necessary for you to fill those fields, so your best bet is to see what backend returns in browser's devtools or refer to the [source code](https://git.pleroma.social/pleroma/pleroma/-/blob/develop/config/config.exs?ref_type=heads#L742-791). For the most part, only **Name**, **Ref** (i.e. version) and **Build URL** fields are required, although some frontends might also require **Build Directory** to work. 
 
-Pleroma-FE and Admin-FE builds come from the package registry, not from GitLab job artifacts. For Admin-FE, set **Name** to `admin-fe`, **Ref** to `develop` and **Build URL** to `https://git.pleroma.social/api/packages/pleroma/generic/admin-fe-builds/${ref}/latest.zip`. Only refs with a published build can be installed; at the moment that is `develop`.
+Pleroma-FE and Admin-FE builds come from the package registry, not from GitLab job artifacts. For Admin-FE, set **Name** to `admin-fe`, **Ref** to `stable` (or `develop`) and **Build URL** to `https://git.pleroma.social/api/packages/pleroma/generic/admin-fe-builds/${ref}/latest.zip`. Only refs with a published build can be installed: `stable`, `develop`, and release tags once they are published.
 
 ### Selecting default frontend