Man pages: Update pipe input documentation.

Make sure the -i <pipe> documentation is consistent and correct.

Change-Id: I9019effb658f914ac754e4ae893eafbe7c4b4da1
Reviewed-on: https://code.wireshark.org/review/30675
Reviewed-by: Gerald Combs <gerald@wireshark.org>

1 files changed, 5 insertions, 4 deletions

diff --git a/doc/wireshark.pod.template b/doc/wireshark.pod.template
index 7cee21502f..556775b225 100644
--- a/doc/wireshark.pod.template
+++ b/doc/wireshark.pod.template
@@ -416,12 +416,13 @@ non-loopback interfaces, and choosing the first loopback interface if
 there are no non-loopback interfaces.  If there are no interfaces at all,
 B<Wireshark> reports an error and doesn't start the capture.
 
-Pipe names should be either the name of a FIFO (named pipe) or ``-'' to
+Pipe names should be either the name of a FIFO (named pipe) or "-" to
 read data from the standard input.  On Windows systems, pipe names must be
-of the form ``\\pipe\.\B<pipename>''.  Data read from pipes must be in
-standard pcap format.
+of the form "\\pipe\.\B<pipename>".  Data read from pipes must be in
+standard pcapng or pcap format. Pcapng data must have the same
+endianness as the capturing host.
 
-This option can occur multiple times.  When capturing from multiple
+This option can occur multiple times. When capturing from multiple
 interfaces, the capture file will be saved in pcapng format.
 
 =item -I