diff --git a/docs/DISTRIBUTION.md b/docs/DISTRIBUTION.md
index 6e38d30..1dd8839 100644
--- a/docs/DISTRIBUTION.md
+++ b/docs/DISTRIBUTION.md
@@ -60,15 +60,24 @@ new release `v0.1.0`. Done.
 
 ## 5. Add the app in Obtainium (on the phone)
 
-Obtainium supports Gitea/Forgejo release sources. Add app → paste:
+Obtainium reads **straight from the repo site** via its native Gitea/Forgejo **Releases**
+source — no separate web server needed. Add app → paste:
 
 ```
 https://git.mowden.top/hank/BigBrainParking
 ```
 
-Pick the **Gitea** (or **Forgejo**) source type if prompted, and Obtainium will track
-releases and offer each new signed APK. Install ntfy + set it as your UnifiedPush
-distributor for push later.
+Pick the **Gitea** (or **Forgejo**) source type if prompted, and Obtainium tracks releases
+and offers each new signed APK. The repo being public means Obtainium needs no token.
+Install ntfy + set it as your UnifiedPush distributor for push later.
+
+### Releases vs. Packages
+
+Use **Releases**, not the **Packages** tab. Gitea/Forgejo *Packages* is a general artifact
+registry (npm, maven, container, generic) — Obtainium has no package-registry source, so it
+won't see APKs there. (You *can* upload an APK to the generic registry and point Obtainium at
+a "Direct APK link," but then Obtainium can't detect new versions automatically. Releases —
+where CI attaches the versioned APK — is the right mechanism.)
 
 ### Fallback if your Obtainium build lacks Gitea support