diff --git a/src/content/docs/logs/ui-data/obfuscation-ui.mdx b/src/content/docs/logs/ui-data/obfuscation-ui.mdx
index c37b51ee15b..9ee3f447431 100644
--- a/src/content/docs/logs/ui-data/obfuscation-ui.mdx
+++ b/src/content/docs/logs/ui-data/obfuscation-ui.mdx
@@ -308,7 +308,7 @@ To obfuscate your logs:
 
 ## CPU limits [#cpu-limits]
 
-Obfuscation has per-minute CPU limits. If your account hits your resource limits, logs won't be obfuscated as expected. To easily check your CPU limits, go to your [system **Limits** page](/docs/data-apis/manage-data/view-system-limits/#limits-ui) in the New Relic **Data management** UI.
+Obfuscation has per-minute CPU limits. If your account hits your resource limits, logs won't be obfuscated as expected. To check your CPU limits, go to your [system **Limits** page](/docs/data-apis/manage-data/view-system-limits/#limits-ui) in the New Relic **Data management** UI.
 
 You can also use the **Health** tab in the **Logs Obfuscation** UI to evaluate how well your obfuscation rules are working, which are being skipped, and whether they need any fine-tuning. Obfuscation rules are CPU intensive, so these charts can help you decide which rules are most impacted by any resource limitations.