Spaces separate bytes; they don't have to surround them.

I.e., you don't need a trailing blank, at least not with the current
version (and there shouldn't be a requirement for such an extra trailing
blank).

Change-Id: Ia2b732c74fc6020acc01a2c0c52ed3567d36d762
Reviewed-on: https://code.wireshark.org/review/6575
Reviewed-by: Guy Harris <guy@alum.mit.edu>

1 files changed, 7 insertions, 6 deletions

diff --git a/doc/text2pcap.pod b/doc/text2pcap.pod
index 6da2334d2a..cd38b6f9d6 100644
--- a/doc/text2pcap.pod
+++ b/doc/text2pcap.pod
@@ -35,12 +35,13 @@ multiple packets.  B<text2pcap> is also capable of generating dummy
 Ethernet, IP and UDP, TCP, or SCTP headers, in order to build fully
 processable packet dumps from hexdumps of application-level data only.
 
-B<Text2pcap> understands a hexdump of the form generated by I<od -Ax -tx1 -v>.
-In other words, each byte is individually displayed and
-surrounded with a space. Each line begins with an offset describing
-the position in the file. The offset is a hex number (can also be
-octal or decimal - see B<-o>), of more than two hex digits.
-Here is a sample dump that B<text2pcap> can recognize:
+B<Text2pcap> understands a hexdump of the form generated by I<od -Ax
+-tx1 -v>.  In other words, each byte is individually displayed, with
+spaces separating the bytes from each other.  Each line begins with an
+offset describing the position in the file, with a space separating it
+from the following bytes.  The offset is a hex number (can also be octal
+or decimal - see B<-o>), of more than two hex digits.  Here is a sample
+dump that B<text2pcap> can recognize:
 
     000000 00 0e b6 00 00 02 00 0e b6 00 00 01 08 00 45 00
     000010 00 28 00 00 00 00 ff 01 37 d1 c0 00 02 01 c0 00