From e8799c574256bd4dc055ec5922d18dce5384709f Mon Sep 17 00:00:00 2001 From: Sammie downing <48104650+homelessbirds@users.noreply.github.com> Date: Thu, 12 May 2022 18:43:56 -0600 Subject: [PATCH 1/2] 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 06f3a14e101..14db5e136e5 100644 --- a/src/content/docs/new-relic-solutions/get-started/glossary.mdx +++ b/src/content/docs/new-relic-solutions/get-started/glossary.mdx @@ -601,7 +601,7 @@ Use alert conditions to define when and why your team will be notified if your e id="facet" title="facet" > - A facet helps your team compare information that has many variables. you can query New Relic data in NRQL and use facets to segment the displayed data. For example if you want to know where your CPU data is being used, you could segment your CPU data by the hostname facet: + A facet helps your team compare information that has many variables. You can query New Relic data in NRQL and use facets to segment the displayed data. For example, if you want to know where your CPU data is being used, you can segment your CPU data by the hostname facet: ```SELECT average(cpuPercent) FROM SystemSample FACET hostname``` From a04ae682bf354ea881dd8d9298c44ae9a0bef540 Mon Sep 17 00:00:00 2001 From: Sammie downing <48104650+homelessbirds@users.noreply.github.com> Date: Thu, 12 May 2022 18:44:06 -0600 Subject: [PATCH 2/2] 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 14db5e136e5..bf7b2097056 100644 --- a/src/content/docs/new-relic-solutions/get-started/glossary.mdx +++ b/src/content/docs/new-relic-solutions/get-started/glossary.mdx @@ -544,7 +544,7 @@ Use alert conditions to define when and why your team will be notified if your e id="distributed_tracing_and_trace_groups" title="distributed_tracing_and_trace_groups" > - Distributed tracing is a method of monitoring requests as they flow through various cloud environments. Distributed tracing tracks a request by tagging it with a unique identifier. This allows your team to have a real- time understanding of the interactions taking place within your entities. + Distributed tracing is a method of monitoring requests as they flow through various cloud environments. Distributed tracing tracks a request by tagging it with a unique identifier. This allows your team to have a real-time understanding of the interactions taking place within your entities.