From 56dd657bb4a3e2801e069567c3114c0745f055db Mon Sep 17 00:00:00 2001 From: Eric Beahan Date: Wed, 10 Feb 2021 14:09:50 -0600 Subject: [PATCH] grammar corrections --- docs/field-values-usage.asciidoc | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/field-values-usage.asciidoc b/docs/field-values-usage.asciidoc index ec6982ec91..88905ba3bc 100644 --- a/docs/field-values-usage.asciidoc +++ b/docs/field-values-usage.asciidoc @@ -57,7 +57,7 @@ This event from a firewall describes a successfully blocked network connection: <1> Classifying as an `event`. <2> `event.category` categorizes this event as `network` activity. -<3> The event was both an attempted network `connection` which was `denied`. +<3> The event was both an attempted network `connection` and was `denied`. <4> The blocking of this connection is expected. The outcome is a `success` from the perspective of the firewall emitting the event. <5> The firewall classifies this denied connection as `dropped`, and this value is captured in `event.action`. @@ -172,4 +172,4 @@ An intrusion detection system (IDS) attempts to block a connection but fails. Th <1> The IDS emitted this event when a detection rule generated an alert. The `event.kind` is set to `alert`. <2> With the event emitted from a network IDS device, the event is categorized both as `network` and `intrusion_detection`. <3> The alert event is a `connection` that was `denied` by the IDS' configuration. -<4> The IDS experience an issue when attempting to deny the connection. Since the action taken by the IDS failed, the outcome is set as `failure`. +<4> The IDS experienced an issue when attempting to deny the connection. Since the action taken by the IDS failed, the outcome is set as `failure`.