userguide/runmodes: fix typo

[AlirezaPourchali]

Make sure these boxes are checked accordingly before submitting your Pull Request -- thank you.

Contribution style:

• I have read the contributing guide lines at
  https://docs.suricata.io/en/latest/devguide/contributing/contribution-process.html

Our Contribution agreements:

• I have signed the Open Information Security Foundation contribution agreement at
  https://suricata.io/about/contribution-agreement/ (note: this is only required once)

Changes (if applicable):

• I have updated the User Guide (in doc/userguide/) to reflect the changes made
• I have updated the JSON schema (in etc/schema.json) to reflect all logging changes
  (including schema descriptions)
• I have created a ticket (stacktrace-on-signal: Use kill(getpid(), sig_num) #7383) at
  https://redmine.openinfosecfoundation.org/projects/suricata/issues

Describe changes:

• fixed a typo in the documentation

[AlirezaPourchali]

it's a very small change and nothing much

[github-actions]

NOTE: This PR may contain new authors.

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 83.15%. Comparing base (5d766df) to head (49fda0c).
Report is 4 commits behind head on master.

Additional details and impacted files

@@             Coverage Diff             @@
##           master   #12108       +/-   ##
===========================================
+ Coverage   62.68%   83.15%   +20.47%     
===========================================
  Files         840      909       +69     
  Lines      153669   257883   +104214     
===========================================
+ Hits        96323   214445   +118122     
+ Misses      57346    43438    -13908     

Flag	Coverage Δ
fuzzcorpus	61.00% <ø> (?)
livemode	19.44% <ø> (?)
pcap	44.04% <ø> (?)
suricata-verify	62.70% <ø> (+0.02%)	⬆️
unittests	59.26% <ø> (?)

Flags with carried forward coverage won't be shown. Click here to find out more.

[jufajardini]

Thanks for your contribution :)

Before we can merge it, the merge commit should be squashed with the main one.

We also kindly ask you to use as your GitHub e-mail for the PR author the same e-mail that you used for signing up the Contribution Agreement, please :)

The CI failure looks unrelated to your work.

[AlirezaPourchali]

squashed the commits to one.
fixed the email as well, thanks for pointing that out !
thanks :)

[jufajardini]

squashed the commits to one. fixed the email as well, thanks for pointing that out ! thanks :)

Thanks! I missed two points in my previous comment, sorry (low on coffee today, it seems), both related to the commit message:

• as you've created a ticket, can you please add the ticket number to the commit body? (a commit message example can be seen at https://docs.suricata.io/en/latest/devguide/contributing/code-submission-process.html#commits
• I've updated the ticket's Subject to be more inline with our commit message style, could you follow that for the commit message, too?

[github-actions]

NOTE: This PR may contain new authors.

[AlirezaPourchali]

changed the commit message.

[AlirezaPourchali]

is everything ok to be merged or do i need to do something else?

[jufajardini]

is everything ok to be merged or do i need to do something else?

It looks good to me, thanks :)

I'll approve it, as it's a very small doc update. For larger contributions, though, the workflow would be to submit a new PR for incorporating new feedback, roger? :)

[jufajardini]

As it's something very small, I think it's ok to go without new versions for the incorporated feedback. Can't confirm whether CLA was really signed or not.

[catenacyber]

There is another one :

git grep " a a "
doc/userguide/performance/hyperscan.rst:**Note:** Hyperscan can take a a long time to build/compile.
doc/userguide/performance/runmodes.rst:active one a a time.  The way threads, modules and queues are arranged