diff --git a/docs/manage-risk/prioritize-issues-for-fixing/ignore-issues/consistent-ignores-for-snyk-code/README.md b/docs/manage-risk/prioritize-issues-for-fixing/ignore-issues/consistent-ignores-for-snyk-code/README.md
index 789e5d5dd7d9..5a018b68e21c 100644
--- a/docs/manage-risk/prioritize-issues-for-fixing/ignore-issues/consistent-ignores-for-snyk-code/README.md
+++ b/docs/manage-risk/prioritize-issues-for-fixing/ignore-issues/consistent-ignores-for-snyk-code/README.md
@@ -59,7 +59,7 @@ Project retests typically occur on a nightly or weekly basis, but you can also r
 
 1. Log in to the Snyk Web UI and navigate to your Group and Organization.
 2. Open a Project and find an issue card.
-3. Select **Ignore across repository** on an issue card to create an ignore.
+3. Select **Ignore** on an issue card to create an ignore.
 4. Fill in the ignore information and confirm its creation. The issue will be updated and moved from **Open** to **Ignored**.\
    \
    If anyone loads the page before a retest, an indicator will appear and encourage retesting to capture policy or ignore changes.
diff --git a/docs/manage-risk/prioritize-issues-for-fixing/ignore-issues/consistent-ignores-for-snyk-code/convert-project-scoped-ignores-to-asset-scoped-ignores.md b/docs/manage-risk/prioritize-issues-for-fixing/ignore-issues/consistent-ignores-for-snyk-code/convert-project-scoped-ignores-to-asset-scoped-ignores.md
index 2d3f124c4478..0192a62575e3 100644
--- a/docs/manage-risk/prioritize-issues-for-fixing/ignore-issues/consistent-ignores-for-snyk-code/convert-project-scoped-ignores-to-asset-scoped-ignores.md
+++ b/docs/manage-risk/prioritize-issues-for-fixing/ignore-issues/consistent-ignores-for-snyk-code/convert-project-scoped-ignores-to-asset-scoped-ignores.md
@@ -10,7 +10,7 @@ Conversion provides you with control over which ignores Snyk converts. For examp
 
 The following scenario assumes that you have ignored issues in your Snyk Code Project prior to enabling Snyk Code Consistent Ignores.
 
-If you have enabled the **Snyk Code Consistent Ignores** feature and have not performed a rescan since, in order for the **Ignore across repository** button to be active, it is possible that you need to [retest the Project](../../../../scan-with-snyk/snyk-code/manage-code-vulnerabilities/#retesting-code-repository). In most cases, the **Ignore across repository** button is active, and this step is not necessary.
+If the **Ignore** button is inactive after you enable the **Snyk Code Consistent Ignores** feature, retest the Project.
 
 ## Convert individual ignore
 
@@ -18,7 +18,7 @@ In the Snyk Web UI, navigate to a Project and open an issue card that contains a
 
 A warning states that the ignore was created through the legacy system and is not consistent across the repository. All issues ignored before enabling the feature appear with this warning, so you can determine what ignore metadata must be converted and used as the source of truth.
 
-To convert an issue from a Project-scoped to an asset-scoped ignore, click **Ignore across repository**.
+To convert an issue from a Project-scoped to an asset-scoped ignore, click **Ignore**.
 
 ## How Snyk handles metadata