From: Lukas Sismis Date: Fri, 4 Apr 2025 10:25:38 +0000 (+0200) Subject: doc: stylistic and grammar fixes X-Git-Tag: suricata-8.0.0-beta1~47 X-Git-Url: http://git.ipfire.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=fbed416e2649e7ced839f0ab7b046089b591b188;p=thirdparty%2Fsuricata.git doc: stylistic and grammar fixes --- diff --git a/doc/userguide/configuration/suricata-yaml.rst b/doc/userguide/configuration/suricata-yaml.rst index 0bccf90713..fe3e7e59f1 100644 --- a/doc/userguide/configuration/suricata-yaml.rst +++ b/doc/userguide/configuration/suricata-yaml.rst @@ -1851,7 +1851,7 @@ port independent. # - full: keep tracking and inspection as normal. Unmodified content # keyword signatures are inspected as well. # - # For best performance, select 'bypass'. + # For the best performance, select 'bypass'. # #encryption-handling: track-only diff --git a/doc/userguide/performance/ignoring-traffic.rst b/doc/userguide/performance/ignoring-traffic.rst index 50399a051d..f30b5b364b 100644 --- a/doc/userguide/performance/ignoring-traffic.rst +++ b/doc/userguide/performance/ignoring-traffic.rst @@ -4,7 +4,7 @@ Ignoring Traffic In some cases there are reasons to ignore certain traffic. Certain hosts may be trusted, or perhaps a backup stream should be ignored. -capture filters (BPF) +Capture Filters (BPF) --------------------- Through BPFs the capture methods pcap, af-packet, netmap and pf_ring can be @@ -70,7 +70,7 @@ Example:: suppress gen_id 0, sig_id 0, track by_src, ip 1.2.3.4 -encrypted traffic +Encrypted Traffic ----------------- The TLS and SSH app layer parsers have the ability to stop processing @@ -84,7 +84,7 @@ is done. .. _bypass: -bypassing traffic +Bypassing Traffic ----------------- Aside from using the ``bypass`` keyword in rules, there are three other ways