Update RELEASE.md

Co-authored-by: Julian Tölle <[email protected]>

Author: mdbooth

RELEASE.md

@@ -32,10 +32,10 @@ It is recommended to create at least one release candidate when bumping `X` or `
 1. Make sure your repo is clean by git's standards. It is recommended to use a fresh checkout.
 1. When bumping `X` or `Y` (but not Z or the pre-release suffix) in the release version you must create a new release branch called `release-X.Y`.
    > NOTE: `upstream` should be the name of the remote pointing to `github.com/kubernetes-sigs/cluster-api-provider-openstack`
-    - git checkout main
-    - git pull
-    - git checkout -b release-`X`.`Y`
-    - git push --set-upstream `upstream`
+    - `git checkout main`
+    - `git pull`
+    - `git checkout -b release-X.Y`
+    - `git push --set-upstream upstream`
 1. When bumping `X` or `Y` (but not Z or the pre-release suffix) in the release version, ensure you have added a new
    entry to [metadata.yaml](https://github.com/kubernetes-sigs/cluster-api-provider-openstack/blob/main/metadata.yaml)
    as [described in the CAPI book](https://cluster-api.sigs.k8s.io/clusterctl/provider-contract.html#metadata-yaml), and