doc/napatech: formatting fixes

diff --git a/doc/userguide/capture-hardware/napatech.rst b/doc/userguide/capture-hardware/napatech.rst
index e9c38f9a36bd2342bdf1a0676b120b5e5b222f99..bf3a27fcb3113f85c7e09d5c914274b92adb744f 100644 (file)
--- a/doc/userguide/capture-hardware/napatech.rst
+++ b/doc/userguide/capture-hardware/napatech.rst
@@ -209,19 +209,20 @@ Now you are ready to start Suricata::
 
        $ suricata -c /usr/local/etc/suricata/suricata.yaml --napatech --runmode workers
 
-
-------------------------------------
 Counters
+--------
 
 For each stream that is being processed the following counters will be output in stats.log:
-    nt<streamid>.pkts - The number of packets recieved by the stream.
-    nt<streamid>.bytes - The total bytes received by the stream.
-    nt<streamid>.drop - The number of packets that were dropped from this stream due to
-                        buffer overflow conditions.
+
+-  nt<streamid>.pkts - The number of packets recieved by the stream.
+
+-  nt<streamid>.bytes - The total bytes received by the stream.
+
+-  nt<streamid>.drop - The number of packets that were dropped from this stream due to buffer overflow conditions.
 
 If hba is enabled the following counter will also be provided:
-    nt<streamid>.hba_drop - the number of packets dropped because the host buffer allowance
-                            high-water mark was reached.
+
+-  nt<streamid>.hba_drop - the number of packets dropped because the host buffer allowance high-water mark was reached.
 
 In addition to counters host buffer utilization is tracked and logged.  This is also useful for
 debugging.  Log messages are output for both Host and On-Board buffers when reach 25, 50, 75