update release process

Author: puckpuck

CONTRIBUTING.md

@@ -296,13 +296,16 @@ Maintainers can create a new release when desired by following these steps.
    notes.
 3. After images for the new release are built and published, create a new Pull
    Request that updates the `CHANGELOG.md` with the new version leaving the
-   `Unreleased` section for the next release.
+   `Unreleased` section for the next release. Merge the Pull Request.
 4. Create a new Pull Request to update the deployment of the demo in the
    [OpenTelemetry Helm
-   Charts](https://github.com/open-telemetry/opentelemetry-helm-charts) repo.
+   Charts](https://github.com/open-telemetry/opentelemetry-helm-charts) repo. Merge the Pull Request.
 5. After the Helm chart is released, create a new Pull Request which updates the
-   Demo's Kubernetes manifest by running `make generate-kubernetes-manifests`
-   and committing the changes.
+   Demo's Kubernetes manifest by running `make generate-kubernetes-manifests`.
+   Merge the Pull Request.
+6. Create a new Tag for the _new_ version with a suffix of `-k8s`. This tag
+   will be used to deploy the new version of the demo to Kubernetes using the 
+   supplied manifests.
 
 [docs]: https://opentelemetry.io/docs/demo/
 

README.md

@@ -73,7 +73,7 @@ keeping it up to date for you.
 
 To get involved with the project see our [CONTRIBUTING](CONTRIBUTING.md)
 documentation. Our [SIG Calls](CONTRIBUTING.md#join-a-sig-call) are every other
-Monday at 8:30 AM PST and anyone is welcome.
+Wednesday at 8:30 AM PST and anyone is welcome.
 
 ## Project leadership