diff --git a/src/content/docs/new-relic-solutions/get-started/glossary.mdx b/src/content/docs/new-relic-solutions/get-started/glossary.mdx
index ab7bcc0abe3..652fe2eea29 100644
--- a/src/content/docs/new-relic-solutions/get-started/glossary.mdx
+++ b/src/content/docs/new-relic-solutions/get-started/glossary.mdx
@@ -425,7 +425,7 @@ Whether you're considering New Relic One or you're already using our capabilitie
     id="conditions"
     title="conditions"
   >
-  You use alert conditions to define when and why your team wants to be notified if your entities aren't working the way you want. Conditions are used to set the criteria that needs to be met in order for your team to be notified about lag time, code errors, Apdex scores, high CPU usage, etc. 
+Use alert conditions to define when and why your team will be notified if your entities aren't working the way you want. With conditions, you establish the criteria for notifications about lag time, code errors, Apdex scores, high CPU usage, and more. 
 
   For more information, see [incidents] (/docs/new-relic-solutions/get-started/glossary/#alert-incident).
   </Collapser>