release notes: fix some 3.2 references

Fix some 3.2 references which were previously missed

Author: hardys

asciidoc/edge-book/releasenotes.adoc

@@ -383,7 +383,7 @@ registry.suse.com/edge/3.3/release-manifest:3.3.0
 [#tech-previews]
 = Technology Previews
 
-Unless otherwise stated, these apply to the 3.2.0 release and all subsequent z-stream versions.
+Unless otherwise stated, these apply to the 3.3.0 release and all subsequent z-stream versions.
 
 * Akri is a Technology Preview offering and is not subject to the standard scope of support.
 * IPv6 and dual-stack downstream deployments are a Technology Preview offering and are not subject to the standard scope of support.
@@ -404,8 +404,8 @@ Verify the container image hash, for example using `crane`:
 
 [,bash]
 ----
-> crane digest registry.suse.com/edge/3.2/baremetal-operator:0.8.0
-sha256:d85c1bcd286dec81a3806a8fb8b66c0e0741797f23174f5f6f41281b1e27c52f
+> crane digest registry.suse.com/edge/3.3/baremetal-operator:0.9.1 --platform linux/amd64
+sha256:02c5590cd51b1a1ea02f9908f2184ef4fbc856eb0197e804a7d57566d9278ddd
 ----
 
 NOTE: For multi-arch images it is also necessary to specify a platform when obtaining the digest, e.g `--platform linux/amd64` or `--platform linux/arm64`. Failure to do this will result in an error in the following step (`Error: no matching attestations`).
@@ -414,9 +414,9 @@ Verify with `cosign`:
 
 [,bash]
 ----
-> cosign verify-attestation --type spdxjson --key key.pem registry.suse.com/edge/3.2/baremetal-operator@sha256:d85c1bcd286dec81a3806a8fb8b66c0e0741797f23174f5f6f41281b1e27c52f > /dev/null
+> cosign verify-attestation --type spdxjson --key key.pem registry.suse.com/edge/3.3/baremetal-operator@sha256:02c5590cd51b1a1ea02f9908f2184ef4fbc856eb0197e804a7d57566d9278ddd > /dev/null
 #
-Verification for registry.suse.com/edge/3.2/baremetal-operator@sha256:d85c1bcd286dec81a3806a8fb8b66c0e0741797f23174f5f6f41281b1e27c52f --
+Verification for registry.suse.com/edge/3.3/baremetal-operator@sha256:02c5590cd51b1a1ea02f9908f2184ef4fbc856eb0197e804a7d57566d9278ddd --
 The following checks were performed on each of these signatures:
   - The cosign claims were validated
   - The claims were present in the transparency log