update release.md

Author: gsheni

RELEASE.md

@@ -6,23 +6,21 @@ The process of releasing a new version involves several steps:
 
 2. [Linting and tests](#linting-and-tests)
 
-3. [Documentation](#documentation)
+3. [Make a release candidate](#make-a-release-candidate)
 
-4. [Make a release candidate](#make-a-release-candidate)
+4. [Integration with SDV](#integration-with-sdv)
 
-5. [Integration with SDV](#integration-with-sdv)
+5. [Milestone](#milestone)
 
-6. [Milestone](#milestone)
+6. [Update HISTORY](#update-history)
 
-7. [Update HISTORY](#update-history)
-
-8. [Check the release](#check-the-release)
+7. [Check the release](#check-the-release)
 
 8. [Update stable branch and bump version](#update-stable-branch-and-bump-version)
 
-10. [Create the Release on GitHub](#create-the-release-on-github)
+9. [Create the Release on GitHub](#create-the-release-on-github)
 
-11. [Close milestone and create new milestone](#close-milestone-and-create-new-milestone)
+10. [Close milestone and create new milestone](#close-milestone-and-create-new-milestone)
 
 ## Install Copulas from source
 
@@ -58,22 +56,6 @@ All checks passed!
 
 The execution has finished with no errors, 0 test skipped and 7820 warnings.
 
-## Documentation
-
-The documentation must be up to date and generated with:
-
-```bash
-make view-docs
-```
-
-Read the documentation to ensure all the changes are reflected in the documentation.
-
-Alternatively, you can simply generate the documentation using the command:
-
-```bash
-make docs
-```
-
 ## Make a release candidate
 
 1. On the Copulas GitHub page, navigate to the [Actions][actions] tab.
@@ -83,7 +65,7 @@ make docs
   - You should see X.Y.ZdevN PRE-RELEASE
 
 [actions]: https://github.com/sdv-dev/Copulas/actions
-[copulas-pypi]: https://pypi.org/project/copulas/#history
+[copulas-pypi]: https://pypi.org/project/Copulas/#history
 
 ## Integration with SDV
 
@@ -115,7 +97,7 @@ git push --set-upstream origin test-copulas-X.Y.Z
 
 ## Milestone
 
-It's important check that the GitHub and milestone issues are up to date with the release.
+It's important to check that the GitHub and milestone issues are up to date with the release.
 
 You neet to check that:
 
@@ -125,7 +107,7 @@ You neet to check that:
   be released anyway, move them to the next milestone.
 - All the issues in the milestone are assigned to at least one person.
 - All the pull requests closed since the latest release are associated to an issue. If necessary, create issues
-  and assign them to the milestone. Also assigne the person who opened the issue to them.
+  and assign them to the milestone. Also assign the person who opened the issue to them.
 
 ## Update HISTORY
 Run the [Release Prep](https://github.com/sdv-dev/Copulas/actions/workflows/prepare_release.yml) workflow. This workflow will create a pull request with updates to HISTORY.md
@@ -172,24 +154,21 @@ Depending on the type of release, run one of the following:
 * `make release-major`: This will release the next major version. Use this to if the changes modify the user API in a backwards incompatible way after the major version 1 has been released.
 
 Running one of these will **push commits directly** to `main`.
-At the end, you should see the 2 commits on `main` on (from oldest to newest):
+At the end, you should see the 3 commits on `main` on (from oldest to newest):
 - `make release-tag: Merge branch 'main' into stable`
 - `Bump version: X.Y.Z.devN → X.Y.Z`
+- `Bump version: X.Y.Z -> X.Y.A.dev0`
 
 ## Create the Release on GitHub
 
 After the update to HISTORY.md is merged into `main` and the version is bumped, it is time to [create the release GitHub](https://github.com/sdv-dev/Copulas/releases/new).
 - Create a new tag with the version number with a v prefix (e.g. v0.3.1)
-- The target should be the `main` branch
+- The target should be the `stable` branch
 - Release title is the same as the tag (e.g. v0.3.1)
 - This is not a pre-release (`Set as a pre-release` should be unchecked)
 
-Click `Publish release`, which will kickoff the release workflow and automatically upload the package to public PyPI.
-
-The release workflow will create a pull request and auto-merge it into `main` that bumps to the next development release. You should see 1 commit on main on:
-- `Bump version: X.Y.Z → X.Y.Z.dev0`
+Click `Publish release`, which will kickoff the release workflow and automatically upload the package to [public PyPI](https://pypi.org/project/copulas/).
 
 ## Close milestone and create new milestone
 
 Finaly, **close the milestone** and, if it does not exist, **create the next milestone**.
-