From 7618353e176f92c3e45f5b4c7af719a35da1946e Mon Sep 17 00:00:00 2001 From: Mathieu Martin Date: Wed, 20 Mar 2019 10:47:51 -0400 Subject: [PATCH] Fix asciidoc rendering after #347 + #389 :eyeroll: --- docs/field-details.asciidoc | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/field-details.asciidoc b/docs/field-details.asciidoc index ae8b0162f..15d1b216c 100644 --- a/docs/field-details.asciidoc +++ b/docs/field-details.asciidoc @@ -145,7 +145,7 @@ example: `6.0.0-rc2` === Client Fields A client is defined as the initiator of a network connection for events regarding sessions, connections, or bidirectional flow records. -For TCP events, the client is the initiator of the TCP connection that sends the SYN packet(s). For other protocols, the client is generally the initiator or requestor in the network transaction. Some systems use the term "originator" to refer the client in TCP connections. The client fields describe details about the system acting as the client in the network event. Client fields are usually populated in conjunction with server fields. Client fields are generally not populated for packet-level events. +For TCP events, the client is the initiator of the TCP connection that sends the SYN packet(s). For other protocols, the client is generally the initiator or requestor in the network transaction. Some systems use the term "originator" to refer the client in TCP connections. The client fields describe details about the system acting as the client in the network event. Client fields are usually populated in conjunction with server fields. Client fields are generally not populated for packet-level events. Client / server representations can add semantic context to an exchange, which is helpful to visualize the data in certain situations. If your context falls in that category, you should still ensure that source and destination are filled appropriately. ==== Client Field Details