diff --git a/.github/workflows/release-please.yml b/.github/workflows/release-please.yml
index 798d7d8..1cfad36 100644
--- a/.github/workflows/release-please.yml
+++ b/.github/workflows/release-please.yml
@@ -35,9 +35,9 @@ jobs:
       - id: release
         uses: googleapis/release-please-action@v4
         with:
-          # A token from a user (secret RELEASE_PLEASE_TOKEN) makes the release PR
+          # A token from a user (secret PAT) makes the release PR
           # trigger the normal checks; the default GITHUB_TOKEN does not.
-          token: ${{ secrets.RELEASE_PLEASE_TOKEN || secrets.GITHUB_TOKEN }}
+          token: ${{ secrets.PAT || secrets.GITHUB_TOKEN }}
           config-file: release-please-config.json
           manifest-file: .release-please-manifest.json
 
diff --git a/docs/releasing.md b/docs/releasing.md
index 33bf02c..81b9672 100644
--- a/docs/releasing.md
+++ b/docs/releasing.md
@@ -29,12 +29,12 @@ with the default `GITHUB_TOKEN` does not trigger other workflows, so a separate
 
 A release PR created with the default `GITHUB_TOKEN` does not run the `test`
 workflow, so required checks on `main` could never pass. The workflow therefore
-uses the repository secret `RELEASE_PLEASE_TOKEN` when it exists and falls back
+uses the repository secret `PAT` when it exists and falls back
 to `GITHUB_TOKEN` otherwise. Create a fine-grained personal access token (of a
 user who may push to the repository) with access to this repository only and
 the permissions **Contents: read and write**, **Pull requests: read and write**
 and **Issues: read and write**, give it an expiry, and store it as the secret
-`RELEASE_PLEASE_TOKEN` (Settings > Secrets and variables > Actions). Put the
+`PAT` (Settings > Secrets and variables > Actions). Put the
 expiry date in your calendar: when the token expires the release PR silently
 stops getting its checks.