diff --git a/docs/nx-cloud/reference/release-notes.md b/docs/nx-cloud/reference/release-notes.md
index ce6c2f08d9..4d2eeaa988 100644
--- a/docs/nx-cloud/reference/release-notes.md
+++ b/docs/nx-cloud/reference/release-notes.md
@@ -6,7 +6,7 @@
 
 A few months ago, we introduced a new feature to our managed SASS NxCloud product: easy membership management via GitHub. If you create a new workspace on [https://cloud.nx.app/](https://cloud.nx.app/) right now you will be guided through how to connect it to your GitHub repository. Now everyone that has access to your GitHub repository will also get access to your NxCloud workspace. If anyone loses access to GitHub (maybe they leave the company), they will also lose access to NxCloud. This makes membership management easy and straightforward, as you don't have to manually invite users anymore. Of course, setting up this connection also gives you NxCloud run status updates directly on your PRs - a feature we've had for a long time.
 
-This feature has now been release for on-prem set-ups as well. To benefit from it, you'll need to create your own Github App with permissions to access your repository. Your on-prem NxCloud instance will then use this app to pull membership info from Github and check users permissions. You can find [the full setup instructions here](/ci/recipes/enterprise/on-premise/custom-github-app).
+This feature has now been release for on-prem set-ups as well. To benefit from it, you'll need to create your own Github App with permissions to access your repository. Your on-prem NxCloud instance will then use this app to pull membership info from Github and check user permissions. You can find [the full setup instructions here](/ci/recipes/enterprise/on-premise/custom-github-app).
 
 ##### DTE v2 enabled by default
 
@@ -17,9 +17,9 @@ After testing the improved task distribution algorithm (DTE v2) for the past few
 If you are using Nx Agents, this release will contain a breaking change to the workflow controller.
 Before upgrading to this version, you'll need to follow the new [Agents Guide](https://github.com/nrwl/nx-cloud-helm/blob/main/AGENTS-GUIDE.md) and deploy an instance of Valkey that your controller can connect to.
 
-The reason we need Valkey is that the workflow controller now persistently stores information about your workflows for up to 8 hours, and these changes will be persisted regardless of the availability of the workflow controller pod, making your in-progress workflows lot more resilient to rolling kubernetes updates, and will fix some previous issues with agent statuses not syncing to the UI.
+The reason we need Valkey is that the workflow controller now persistently stores information about your workflows for up to 8 hours, and these changes will be persisted regardless of the availability of the workflow controller pod, making your in-progress workflows more resilient to rolling kubernetes updates, and will fix some previous issues with agent statuses not syncing to the UI.
 
-If you are not using Nx Agents, this does not affect you and you do not need to make any changes to your set-up.
+If you are not using Nx Agents, this does not affect you and you can upgrade to this version straight away.
 
 ##### UI improvements