Update DEVELOPMENT.md (#56)

Polishing the DEVELOPMENT.md documentation for accuracy and clarity

Author: apmatthews

DEVELOPMENT.md

@@ -19,7 +19,7 @@ We use the [feature branch workflow](https://www.atlassian.com/git/tutorials/com
 
 We use [Changesets](https://github.com/changesets/changesets) to automate versioning and releasing. When you are ready to release, the first step is to create the new version.
 
-1. Go to pull requests and view the "Version Action" PR.
+1. Go to pull requests and view the automated "Version Image" PR.
 2. Review the PR:
     - [ ] Changelog entries were created.
     - [ ] Version number in package.json was bumped.
@@ -28,15 +28,11 @@ We use [Changesets](https://github.com/changesets/changesets) to automate versio
 
 Merging the versioning PR will run a workflow that creates or updates all necessary tags. It will also create a new release in GitHub.
 
-## Managing the Dockerfile & Docker Image
+## Updating the Docker Image
 
 The `Dockerfile` is hosted as a Docker image on DockerHub: [wpengine/sitedeploy](https://hub.docker.com/r/wpengine/site-deploy).
 
-The Docker image is used in both [wpengine/github-action-wpe-site-deploy](https://github.com/wpengine/github-action-wpe-site-deploy) GitHub Action and the [azunigawpe/wpe-bb-deploy](https://bitbucket.org/azunigawpe/wpe-bb-deploy/src/main/) BitBucket Pipeline. Any customizations to the image should consider the effect on both services.
-
-Any other customizations that are uniquely required can be added to the Dockerfile in the project itself.
-
-## Updating the Docker Image
+The Docker image is used in both [wpengine/github-action-wpe-site-deploy](https://github.com/wpengine/github-action-wpe-site-deploy) GitHub Action and the [wpengine/wpe-site-deploy]([https://bitbucket.org/azunigawpe/wpe-bb-deploy/src/main/](https://bitbucket.org/wpengine/wpe-site-deploy/src/main/)) Bitbucket Pipe. Any customizations to the image should consider the effect on both services.
 
 ### Automatic Builds
 
@@ -47,28 +43,25 @@ Docker images are built and pushed automatically:
 | Push to `main` | `latest` | Docker Hub Autobuild |
 | New version release | `latest`, `vX`, `vX.Y`, `vX.Y.Z` | Docker Hub Autobuild |
 | Monthly schedule (1st of month) | `latest`, `vX`, `vX.Y`, `vX.Y.Z` | GitHub Actions |
+| Manual trigger | `latest`, `vX`, `vX.Y`, `vX.Y.Z` | GitHub Actions |
 
-The scheduled monthly rebuild ensures security patches are applied even when there are no new releases. This workflow uses `no-cache` to pull fresh base image layers.
+The scheduled monthly rebuild ensures security patches are applied even when there are no new releases. Both the scheduled and manually triggered workflows use `no-cache` to pull fresh base image layers.
 
 ### Base Image Maintenance
 
 The Dockerfile uses Alpine Linux as its base image. The base image follows this update pattern:
 
 - **Dependabot** monitors for new Alpine versions and creates PRs automatically
-- **Scheduled rebuilds** pick up security patches from `apk upgrade` monthly
 - Alpine releases new versions every 6 months (roughly June and December)
+- **Scheduled rebuilds** pick up security patches from `apk upgrade` monthly
 
 When Dependabot opens a PR for a new Alpine version:
 
-1. Review the [Alpine release notes](https://alpinelinux.org/releases/) for breaking changes
+1. Review the [Alpine release notes](https://alpinelinux.org/releases/) for breaking changes and ensure tests are passing.
 2. Add a changeset to the PR (`npx changeset`) so a proper release is created when merged
 3. Merge the PR to trigger a new versioned release
 
-### Docker Hub
-
-Images are published to DockerHub: [wpengine/site-deploy](https://hub.docker.com/r/wpengine/site-deploy)
-
-## Manually updating the Docker Image
+## Building and versioning locally
 
 You can also build and version this image using make targets when necessary.
 
@@ -78,6 +71,3 @@ make version     # Builds the image and creates version tags
 make list-images # Shows all tagged versions of the image
 make clean       # Deletes all tagged versions of the image
 ```
-
-To push a custom version of the image to DockerHub:
-`docker push wpengine/site-deploy:{tagName}`