diff --git a/docs/blog/posts/stable-release-announcement.md b/docs/blog/posts/stable-release-announcement.md
index 8421abb9fc..701758d732 100644
--- a/docs/blog/posts/stable-release-announcement.md
+++ b/docs/blog/posts/stable-release-announcement.md
@@ -2,7 +2,7 @@
 date: 2024-03-10
 authors: [agardnerIT]
 description: >
-  In this blog post, the release candidate for Keptn v2 is announced.
+  This blog post announces the release candidate for Keptn v2.
 comments: true
 ---
 
@@ -37,21 +37,24 @@ Keptn v2-rc will bring the following new features:
 - Non-Blocking Tasks
 - A new “promotion” stage
 
-### Non-Blocking Tests
+### Non-blocking tasks and evaluations
 
 Keptn offers the ability to perform arbitrary tasks and SLO evaluations both before a deployment and after a deployment.
-By design, any pre-deployment task or SLO evaluation which fails will block the deployment.
+By design, any pre-deployment task or SLO evaluation that fails will block the deployment.
 Often, this is the behaviour you want – if a downstream dependency is unavailable or unhealthy,
 you probably don’t want to complete the deployment.
 However, for new Keptn users, this behaviour can appear drastic and cause deployments to be
 “pending” without an obvious cause.
-In Keptn v2 this blocking behaviour for pre tasks and evaluations is now configurable.
+In Keptn v2 this blocking behaviour for pre tasks and evaluations can be temporarily disabled for the cluster
+until you are sure that your tasks and evaluations
+are performing appropriately.
 When creating the KeptnConfig resource, set `spec.blockDeployment: [true|false]`.
 The default behaviour is for Keptn to block deployments (i.e. `spec.blockDeployment: true`)
 
 ### The Promotion Stage
 
-Keptn v2 introduces a new “promotion” stage.
+Keptn v2 introduces a new “promotion” stage
+to support multi-stage application delivery.
 Keptn is commonly used alongside [GitOps practices](https://opengitops.dev/) and thus,
 users want to have a dedicated way to promote an application to the next stage in my environment.
 The new stage is disabled by default and can be controlled via the Helm flag:
@@ -59,11 +62,13 @@ The new stage is disabled by default and can be controlled via the Helm flag:
 The upcoming stable release will be shipped with this feature enabled out of the box.
 
 Further information can be found in
-[the official documentation](https://keptn.sh/stable/docs/guides/multi-stage-application-delivery/).
+The
+[Multi-stage application delvery](https://keptn.sh/stable/docs/guides/multi-stage-application-delivery/)
+guide.
 
 ## Try it out
 
-Now, you will see a true end-to-end picture of everything in the logical operation,
+Now, you can see a true end-to-end picture of everything in the logical operation,
 potentially from “PR merged” all the way to “deployment complete”.
 [Download Keptn v2 RC1 Now!](https://artifacthub.io/packages/helm/lifecycle-toolkit/keptn)