added timeout flag to TCP messages in docs

Signed-off-by: bota <[email protected]>

Author: SergiuBota1

docs/book/v1/commands.md

@@ -19,12 +19,12 @@ To run the commands via CLI, use the following syntax:
 
 To use commands using TCP messages the following messages can be used:
 
-`echo "failed --start=yyyy-mm-dd --end=yyyy-mm-dd --limit=days" | socat - TCP:host:port`
+`echo "failed --start=yyyy-mm-dd --end=yyyy-mm-dd --limit=days" | socat -t1 - TCP:host:port`
 
-`echo "processed --start=yyyy-mm-dd --end=yyyy-mm-dd --limit=days" | socat - TCP:host:port`
+`echo "processed --start=yyyy-mm-dd --end=yyyy-mm-dd --limit=days" | socat -t1 - TCP:host:port`
 
 In both cases the flags are optional. Keep in mind if both `start` and `end` are set, `limit` will not be applied, it's only used when one of `start` or `end` is missing.
 
 In order to be able to test the `processed` command, by default when processing the "control" message, it is logged as successfully processed with `"levelName":"info"` simulating that the message was processed successfully. To use it run the following message:
 
-`echo "control" | socat - TCP:host:port`
+`echo "control" | socat -t1 - TCP:host:port`