docs(release-process): update versions to reflect current/anticipated release

Signed-off-by: Vaughn Dice <vaughn.dice@fermyon.com>

Author: vdice

docs/content/release-process.md

@@ -8,16 +8,16 @@ url = "https://github.com/fermyon/spin/blob/main/docs/content/release-process.md
 To cut a release of Spin, you will need to do the following:
 
 1. Create a pull request that changes the version number for your new version
-   (e.g. `0.3.0` becomes `0.3.1`)
+   (e.g. `0.5.0` becomes `0.5.1`)
    - Bump the version in Spin's `Cargo.toml`
    - Bump the version in the Rust SDK as well (`sdk/rust/Cargo.toml`)
    - Check the docs for hard-coded version strings
 1. Merge the PR created in #1 (Such PRs are still required to get approvals, so
    make sure you get signoff on the PR)
 1. Before proceeding, verify that the merge commit on `main` intended to be
    tagged is green, i.e. CI is successful
-1. Create a new tag with a `v` and then the version number (`v0.3.1`)
-1. The Go SDK tag `sdk/go/v0.3.1` and template tag `spin/templates/v0.3` will be created in `release` [action](https://github.com/fermyon/spin/actions/workflows/release.yaml).
+1. Create a new tag with a `v` and then the version number (`v0.5.1`)
+1. The Go SDK tag `sdk/go/v0.5.1` and template tag `spin/templates/v0.5` will be created in `release` [action](https://github.com/fermyon/spin/actions/workflows/release.yaml).
 1. When the `release`
    [action](https://github.com/fermyon/spin/actions/workflows/release.yaml)
    completes, binary artifacts and checksums will be automatically uploaded.