trafgen: man: Highlight packet functions section

Make the each packet functions section name to be bold.

Signed-off-by: Vadim Kochan <vadim4j@gmail.com>
Signed-off-by: Tobias Klauser <tklauser@distanz.ch>

1 files changed, 8 insertions, 6 deletions

diff --git a/trafgen.8 b/trafgen.8
index a8e1edb..62716bb 100644
--- a/trafgen.8
+++ b/trafgen.8
@@ -243,7 +243,7 @@ this when running this with trafgen in combination with \-V):
 There are a couple of helper functions in trafgen's language to make life easier
 to write configurations:
 .PP
-i) Fill with garbage functions:
+.B i) Fill with garbage functions:
 .PP
    byte fill function:      fill(<content>, <times>): fill(0xca, 128)
    compile-time random:     rnd(<times>): rnd(128), rnd()
@@ -253,7 +253,7 @@ i) Fill with garbage functions:
    runtime counter (1byte): dinc(<min-val>, <max-val>, <increment>)
                             ddec(<min-val>, <max-val>, <decrement>)
 .PP
-ii) Checksum helper functions (packet offsets start with 0):
+.B ii) Checksum helper functions (packet offsets start with 0):
 .PP
    IP/ICMP checksum:        csumip/csumicmp(<off-from>, <off-to>)
    UDP checksum:            csumudp(<off-iphdr>, <off-udpdr>)
@@ -261,7 +261,7 @@ ii) Checksum helper functions (packet offsets start with 0):
    UDP checksum (IPv6):     csumudp6(<off-ip6hdr>, <off-udpdr>)
    TCP checksum (IPv6):     csumtcp6(<off-ip6hdr>, <off-tcphdr>)
 .PP
-iii) Multibyte functions, compile-time expression evaluation:
+.B iii) Multibyte functions, compile-time expression evaluation:
 .PP
    const8(<content>), c8(<content>), const16(<content>), c16(<content>),
    const32(<content>), c32(<content>), const64(<content>), c64(<content>)
@@ -271,14 +271,16 @@ configuration, e.g. const16(0xaa) will result in ''00 aa''. Within c*()
 functions, it is possible to do some arithmetics: -,+,*,/,%,&,|,<<,>>,^
 E.g. const16((((1<<8)+0x32)|0b110)*2) will be evaluated to ''02 6c''.
 .PP
-iv) Protocol header functions:
+.B iv) Protocol header functions:
+.in +4
 The protocol header functions allow to fill protocol header fields by
 using following generic syntax:
-.in +8
 .sp
+.in +4
 <proto>(<field>=<value>,<field2>=<value2>,...,<field3>,...)
+.in -4
 .sp
-.in -8
+.in -4
 .in +4
 If a field is not specified, then a default value will be used (usually 0).
 Protocol fields might be set in any order. However, the offset of the fields in