doc: stylistic and grammar fixes

diff --git a/doc/userguide/configuration/suricata-yaml.rst b/doc/userguide/configuration/suricata-yaml.rst
index 0bccf90713bbfa655c781ba414e94e3e2e4d7fb8..fe3e7e59f186f27028fefdb285beb26d64f77a58 100644 (file)
--- 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 50399a051d2871a046124a40a3d5dff6ef3938b6..f30b5b364b8d78932d81855bf027bdbb8629f376 100644 (file)
--- 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