doc/userguide: fix typo

Issue: #7540

fixed doc/userguide/performance/hyperscan.rst
fixed doc/userguide/performance/runmodes.rst

diff --git a/doc/userguide/performance/hyperscan.rst b/doc/userguide/performance/hyperscan.rst
index 055fa7f21b753141d917c5d333ba6657cc2b4342..95916332b3402707a1622859d0defcb87bb04dd0 100644 (file)
--- a/doc/userguide/performance/hyperscan.rst
+++ b/doc/userguide/performance/hyperscan.rst
@@ -51,7 +51,7 @@ The steps to build and install hyperscan are:
   cmake --build ./
   sudo cmake --install ./
 
-**Note:** Hyperscan can take a a long time to build/compile.
+**Note:** Hyperscan can take a long time to build/compile.
 
 **Note:** It may be necessary to add /usr/local/lib or
 /usr/local/lib64 to the `ld` search path. Typically this is

diff --git a/doc/userguide/performance/runmodes.rst b/doc/userguide/performance/runmodes.rst
index 4afc5d56ccd22d53166eb3d97ccb9fc2c7bcff23..050a98e7273e0e02a58c51df99e0249c438f7421 100644 (file)
--- a/doc/userguide/performance/runmodes.rst
+++ b/doc/userguide/performance/runmodes.rst
@@ -12,7 +12,7 @@ a queue. Packets will be processed by one thread at a time, but there
 can be multiple packets being processed at a time by the engine (see
 :ref:`suricata-yaml-max-pending-packets`). A thread can have one or
 more thread-modules. If they have more modules, they can only be
-active one a a time.  The way threads, modules and queues are arranged
+active one at a time.  The way threads, modules and queues are arranged
 together is called the "Runmode".
 
 Different runmodes