Update release.md (#324)

* update release process

* update release notes

* fix spelling

docs/source/release_notes.rst

@@ -20,6 +20,7 @@ Future Release
         * Add in-line tabs and copy-paste functionality to docs (:pr:`293`)
         * Update nbconvert to version 6.4.5 to fix docs build issue (:pr:`305`)
         * Update slack invite link to new (:pr:`316`)
+        * Update ``release.md`` with correct process (:pr:`324`)
     * Testing Changes
         * Add woodwork to ``test-requirements.txt`` (:pr:`296`)
         * Upgrade black version to 22.3.0 to fix linting issue (:pr:`309`)

release.md

@@ -1,10 +1,10 @@
 # Release Process
 ## Prerequisites
-The environment variables `PYPI_USERNAME` and `PYPI_PASSWORD` must be already set in the repository as secrets. To add these variables, go to Secrets in the Settings of the repostiory.
+The environment variables `PYPI_USERNAME` and `PYPI_PASSWORD` must be already set in the repository as secrets. To add these variables, go to Secrets in the Settings of the repository.
 
 ## Create Release Branch
 1. Branch off of main and name the branch the release version number (e.g. v0.1.2)
-2. Bump verison number in `setup.py`, and `composeml/__init__.py`.
+2. Bump version number in ``composeml/version.py`, and `composeml/tests/test_version.py`.
 
 ## Create Release PR
 A release PR should have the version number as the title and the changelog updates as the PR body text. The contributors line is not necessary.