diff --git a/README.md b/README.md
index ff54e93..64bd076 100644
--- a/README.md
+++ b/README.md
@@ -127,8 +127,8 @@ Releases are automated via GitHub Actions. To cut a new release:
 
 1. Bump `PROJECTS_PORTFOLIO_VERSION` and the plugin header `Version:` in `projects-portfolio.php`.
 2. Commit and push to `main`.
-3. Tag the release commit: `git tag -a v1.1.0 -m "v1.1.0 — short summary"`.
-4. Push the tag: `git push origin v1.1.0`.
+3. Tag the release commit: `git tag -a v1.1.1 -m "v1.1.1 — short summary"`.
+4. Push the tag: `git push origin v1.1.1`.
 
 The `.github/workflows/release.yml` workflow runs and:
 
@@ -140,16 +140,7 @@ Dev-only paths (`composer.json`, `composer.lock`, `vendor/`, `tests/`, `plans/`,
 
 ## How to Zip the Plugin for GitHub Releases
 
-When attaching the plugin to a GitHub release:
-
-1. Zip **only the contents of the plugin folder**, not the parent folder.
-2. Ensure `projects-portfolio.php` and `/includes`, `/admin`, `/templates`, `/assets` are at the root level of the ZIP.
-3. Name the ZIP clearly (e.g. `projects-portfolio-1.0.0.zip`).
-4. Go to your GitHub repo → **Releases** → **New Release**.
-5. Tag the release with the version number (e.g., `1.0.0`).
-6. Upload your correctly structured ZIP as a release asset.
-
-Your users will be redirected to this file when they use the `/download/` endpoint.
+This is now automated. See [Building a Release](#building-a-release) above — pushing a `v*` tag triggers `.github/workflows/release.yml` which builds and publishes the zip.
 
 ## REST API Endpoints