diff --git a/docs/RELEASE.md b/docs/RELEASE.md
index 7e33ba2..c1ed12e 100644
--- a/docs/RELEASE.md
+++ b/docs/RELEASE.md
@@ -17,10 +17,10 @@ git tag
 ```code
 git push origin <tag>
 ```
-- Check workflow `releases.yml` should trigger
-- Once completed, go to repo releases page and edit the newly created release as `pre-release`, so we can do sanity testig before we officicaly release
+- Check that workflow [`releases.yml`](https://github.com/actions/actions-sync/actions/workflows/releases.yml) was triggered
+- Once completed, [go to repo releases page](https://github.com/actions/actions-sync/releases) and edit the newly created release as `pre-release`, so we can do sanity testing before we officially release
 - Recommend to do basic sanity testing (see below) on the new release.
-- Once sanity testing is done, we can edit the releas and mark it as `Latest version` and edit the release notes.
+- Once sanity testing is done, we can edit the release and mark it as `Latest version` and edit the release notes.
 
 ## Basic Sanity testing
 
@@ -35,6 +35,6 @@ git push origin <tag>
 
     - sanity_test_site_admin_token: The PAT generated earlier 
     - sanity_test_ghes_url: The URL to the GHES instance 
-    - sanity_test_releasedatetime: The datetime string for the release to test without the `v` (e.g. `202211070205`)
+    - sanity_test_releasedatetime: The tag datetime string for the release to test without the `v` (e.g. `202211070205`)
 
 1. Manually trigger this workflow: https://github.com/actions/actions-sync/actions/workflows/actions-sync-e2e-test-caller.yml