From cde902ec1686891218f7952b6ce8f15f1c499ba4 Mon Sep 17 00:00:00 2001
From: Sammie downing <48104650+homelessbirds@users.noreply.github.com>
Date: Thu, 12 May 2022 15:45:53 -0600
Subject: [PATCH] Update
 src/content/docs/new-relic-solutions/get-started/glossary.mdx

Co-authored-by: mmfred <58010132+mmfred@users.noreply.github.com>
---
 src/content/docs/new-relic-solutions/get-started/glossary.mdx | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

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 b8a278d1345..67156ee01fb 100644
--- a/src/content/docs/new-relic-solutions/get-started/glossary.mdx
+++ b/src/content/docs/new-relic-solutions/get-started/glossary.mdx
@@ -576,7 +576,7 @@ Use alert conditions to define when and why your team will be notified if your e
     id="event"
     title="event"
   >
-   In the software industry, events can be thought of as simply “things that occur in a system.” For example, a server setting being changed would be an event. Another example: a website user clicking a mouse.
+   In the software industry, events can be thought of as simply “things that occur in a system.” For example, changing a server setting is an event. Another example: a website user clicking a mouse.
 
     Some events will generate a stored record, and that record is typically also called an event. 
   To learn how New Relic uses events, see [New Relic data types](https://docs.newrelic.com/docs/data-apis/understand-data/new-relic-data-types/#event-data).