diff --git a/documentation/api/guides/deploy.md b/documentation/api/guides/deploy.md
index 89ec213f3eb..c255f1466b2 100644
--- a/documentation/api/guides/deploy.md
+++ b/documentation/api/guides/deploy.md
@@ -30,7 +30,9 @@ For more information on how deployments work, please see the [general deployment
 1. Review and Approve the automatically-generated changelog pull request in the
    repository.
 1. In the event of errors or problems, repeat the deployment process using the
-   latest stable version of the application. You can find this tag in the
-   [changelogs](/changelogs/index).
+   latest stable version of the application. You can find the release version
+   number in the [changelogs](/changelogs/index), and then the tag to pass to
+   the action is the version number prefixed with "rel-", for example
+   "rel-2023.07.03.17.52.00".
 1. If anything else goes wrong or service is disrupted, consider this a
    Production Incident and notify the team.
diff --git a/documentation/catalog/guides/deploy.md b/documentation/catalog/guides/deploy.md
index 822c92b36ed..d14106f10d9 100644
--- a/documentation/catalog/guides/deploy.md
+++ b/documentation/catalog/guides/deploy.md
@@ -30,7 +30,9 @@
 1. Push up a PR to the infrastructure repository with the Terraform changes you
    pushed (the version bump for the relevant module).
 1. In the event of errors or problems, repeat the deployment process using the
-   latest stable version of the application. You can find this tag in the
-   [changelogs](/changelogs/index).
+   latest stable version of the application. You can find the release version
+   number in the [changelogs](/changelogs/index), and then the tag to pass to
+   the action is the version number prefixed with "rel-", for example
+   "rel-2023.07.03.17.52.00".
 1. If anything else goes wrong or service is disrupted, consider this a
    Production Incident and notify the team.
diff --git a/documentation/frontend/guides/deploy.md b/documentation/frontend/guides/deploy.md
index 9aa433cbd98..ba1a1c50786 100644
--- a/documentation/frontend/guides/deploy.md
+++ b/documentation/frontend/guides/deploy.md
@@ -29,5 +29,7 @@ For more information on how deployments work, please see the [general deployment
 1. Review and Approve the automatically-generated changelog pull request in the
    repository.
 1. In the event of errors or problems, repeat the deployment process using the
-   latest stable version of the application. You can find this tag in the
-   [changelogs](/changelogs/index).
+   latest stable version of the application. You can find the release version
+   number in the [changelogs](/changelogs/index), and then the tag to pass to
+   the action is the version number prefixed with "rel-", for example
+   "rel-2023.07.03.17.52.00".
diff --git a/documentation/ingestion_server/guides/deploy.md b/documentation/ingestion_server/guides/deploy.md
index 22410661ffd..fc783fe22f4 100644
--- a/documentation/ingestion_server/guides/deploy.md
+++ b/documentation/ingestion_server/guides/deploy.md
@@ -34,7 +34,9 @@
    pushed (the version bump for the relevant module). Be sure to restore the
    value of `data_refresh_cleared` back to `false`.
 1. In the event of errors or problems, repeat the deployment process using the
-   latest stable version of the application. You can find this tag in the
-   [changelogs](/changelogs/index).
+   latest stable version of the application. You can find the release version
+   number in the [changelogs](/changelogs/index), and then the tag to pass to
+   the action is the version number prefixed with "rel-", for example
+   "rel-2023.07.03.17.52.00".
 1. If anything else goes wrong or service is disrupted, consider this a
    Production Incident and notify the team.