diff --git a/docs/package-release.md b/docs/package-release.md
index c00118e..52cee67 100644
--- a/docs/package-release.md
+++ b/docs/package-release.md
@@ -2,7 +2,7 @@
 
 `issue-core` publishes as the `issue-core` Python package. The Railiance
 application deployment path expects the `0.2.x` series to be available from the
-Coulomb Gitea PyPI registry.
+Coulomb Forgejo PyPI registry (`forgejo.coulomb.social`).
 
 ## Local Release
 
@@ -17,7 +17,7 @@ Publish to the Coulomb organization registry:
 ```bash
 TWINE_USERNAME=<gitea-user> \
 TWINE_PASSWORD=<package-token> \
-make publish-gitea
+make publish-forgejo
 ```
 
 The package endpoint is:
@@ -35,15 +35,15 @@ https://forgejo.coulomb.social/api/packages/coulomb/pypi/simple/
 Do not commit tokenized package index URLs. CI and local Docker builds should
 inject registry credentials through environment variables or BuildKit secrets.
 
-## Gitea Actions Release
+## Forgejo Actions Release
 
-The `.gitea/workflows/publish-python-package.yml` workflow publishes on tags
-matching `v*`. Configure these repository secrets before cutting a release:
+The `.forgejo/workflows/publish-python-package.yml` workflow publishes on tags
+matching `v*` or `workflow_dispatch`. Configure org secrets:
 
-- `GITEA_PACKAGE_USER`
-- `GITEA_PACKAGE_TOKEN`
+- `FORGEJO_PYPI_USER`
+- `FORGEJO_PYPI_TOKEN`
 
-Release `0.2.0` with:
+Release with:
 
 ```bash
 git tag v0.2.0