Skip to content

Commit 77e3a15

Browse files
committed
Fix typos
1 parent af2b8ce commit 77e3a15

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

docs/user/bots.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -4630,7 +4630,7 @@ as not usable for IDS.
46304630
**`event_separator`
46314631

46324632
(optional, string): If set to a field name from IntelMQ event, the bot will work in parallel on a few
4633-
events instead of saving all incomming messages to a one. Each unique value from the field will
4633+
events instead of saving all incoming messages to a one. Each unique value from the field will
46344634
use its own MISP Event. This is useful if your feed provides data about multiple entities you would
46354635
like to group, for example IPs of C2 servers from different botnets. For a given value, the bot will
46364636
use the same MISP Event as long as it's allowed by the `interval_event`.
@@ -4643,7 +4643,7 @@ depends of datetimes saved there). If you use `event_separator`, you may want to
46434643
placeholder which will be then replaced with the value of the separator.
46444644

46454645
For example, the following configuration can be used to create MISP Feed with IPs of C2 servers
4646-
of different botnets, having each botnet in a separated MISP Events with an appropiate description.
4646+
of different botnets, having each botnet in a separated MISP Events with an appropriate description.
46474647
Each MISP Event will contain objects with the `source.ip` field only, and the events' info will look
46484648
like *C2 Servers for botnet-1. IntelMQ event 2024-07-09T14:51:10.825123 - 2024-07-10T14:51:10.825123*
46494649

0 commit comments

Comments
 (0)