Apply suggestions from code review

Co-authored-by: Tim Bannister <[email protected]>

content/en/blog/_posts/2022-12-12-kubernetes-release-artifact-signing.md

@@ -20,8 +20,8 @@ process for related projects (for example for those in [kubernetes-sigs][k-sigs]
 
 [k-sigs]: https://github.com/kubernetes-sigs
 
-We already sign all officially released container images from Kubernetes v1.24,
-which was still an _alpha_ feature until v1.25. Now in v1.26, we added all
+We already signed all officially released container images (from Kubernetes v1.24 onwards).
+Image signing was alpha for v1.24 and v1.25. For v1.26, we've added all
 **binary artifacts** to the signing process as well! This means that now all
 [client, server and source tarballs][tarballs], [binary artifacts][binaries],
 [Software Bills of Material (SBOMs)][sboms] as well as the [build
@@ -107,17 +107,19 @@ All of the mentioned steps as well as how to verify container images are
 outlined in the official documentation about how to [Verify Signed Kubernetes
 Artifacts][docs]. In one of the next upcoming Kubernetes releases we will
 working making the global story more mature by ensuring that truly all
-Kubernetes artifacts are signed. Beside that, we consider to use Kubernetes
+Kubernetes artifacts are signed. Beside that, we are considering using Kubernetes
 owned infrastructure for the signing (root trust) and verification (transparency
 log) process.
 
 [docs]: /docs/tasks/administer-cluster/verify-signed-artifacts
 
+## Getting involved
+
 If you're interested in contributing to SIG Release, then consider applying for
 the upcoming v1.27 shadowing program (watch for the announcement on
 [k-dev][k-dev]) or join our [weekly meeting][meeting] to say _hi_.
 
-We're looking forward to shipping more of those awesome features in future
+We're looking forward to making even more of those awesome changes for future
 Kubernetes releases. For example, we're working on the [SLSA Level 3 Compliance
 in the Kubernetes Release Process][slsa] or the [Renaming of the kubernetes/kubernetes
 default branch name to `main`][kkmain].
@@ -136,6 +138,6 @@ the [#sig-release][slack] Slack channel.
 [k-dev]: https://groups.google.com/a/kubernetes.io/g/dev
 [meeting]: http://bit.ly/k8s-sig-release-meeting
 
-#### Additional resources
+## Additional resources
 
 - [Signing Release Artifacts Enhancement Proposal](https://github.com/kubernetes/enhancements/issues/3031)