doc/configuration: improve emergency-recovery docs

When removing mentions to `prune-flows` a few inconsistencies for how
we write and refer to `emergency-recovery` were left behind, still.

diff --git a/doc/userguide/configuration/suricata-yaml.rst b/doc/userguide/configuration/suricata-yaml.rst
index ce7cd76a852cb1b1b6645df2c9628e4745cee10b..26c1e9e6784774bf446d5353ad9420f788465699 100644 (file)
--- a/doc/userguide/configuration/suricata-yaml.rst
+++ b/doc/userguide/configuration/suricata-yaml.rst
@@ -1071,7 +1071,7 @@ flow-engine goes into the emergency-mode. In this mode, the engine
 will make use of shorter time-outs. It lets flows expire in a more
 aggressive manner so there will be more space for new Flows.
 
-Emergency_recovery defines the percentage of flows that the engine needs to
+``emergency-recovery`` defines the percentage of flows that the engine needs to
 prune before clearing the **emergency mode**. The default ``emergency-recovery``
 value is 30. This is the percentage of prealloc'd flows after which the flow
 -engine will be back to normal (when 30 percent of the 10000 flows are
@@ -1084,7 +1084,7 @@ completed).
 
 ::
 
-  emergency_recovery: 30                  #Percentage of 10000 prealloc'd flows.
+  emergency-recovery: 30                  #Percentage of 10000 prealloc'd flows.
 
 Flow Time-Outs
 ~~~~~~~~~~~~~~