More AsciiDoc → Asciidoctor updates.

Switch from AsciiDoc's smart quotes markup to the quotes themselves. Use
double curly quotes in place of singles.

Switch from XML entities to their direct equivalents where we can.
Switch from hex entities to decimal entities where we can't or it's not
convenient. (Asciidoctor PDF doesn't yet handle hex entities).

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

1 files changed, 13 insertions, 13 deletions

diff --git a/docbook/wsug_src/WSUG_app_tools.asciidoc b/docbook/wsug_src/WSUG_app_tools.asciidoc
index 0511383eca..23cf5425e6 100644
--- a/docbook/wsug_src/WSUG_app_tools.asciidoc
+++ b/docbook/wsug_src/WSUG_app_tools.asciidoc
@@ -14,7 +14,7 @@
 Along with the main application, Wireshark comes with an array of
 command line tools which can be helpful for specialized tasks. Some of
 these tools will be described in this chapter. You can find more
-information about all of Wireshark's command line tools on
+information about all of Wireshark’s command line tools on
 link:{wireshark-man-page-url}[the web site].
 
 [[AppToolstshark]]
@@ -35,9 +35,9 @@ include::tshark-h.txt[]
 
 [[AppToolstcpdump]]
 
-=== __tcpdump__: Capturing with ``tcpdump'' for viewing with Wireshark
+=== __tcpdump__: Capturing with “tcpdump” for viewing with Wireshark
 
-It's often more useful to capture packets using `tcpdump` rather than
+It’s often more useful to capture packets using `tcpdump` rather than
 `wireshark`. For example, you might want to do a remote capture and either don't
 have GUI access or don't have Wireshark installed on the remote machine.
 
@@ -59,10 +59,10 @@ tcpdump`) or link:{tcpdump-man-page-url}[the online version].
 
 [[AppToolsdumpcap]]
 
-=== __dumpcap__: Capturing with ``dumpcap'' for viewing with Wireshark
+=== __dumpcap__: Capturing with “dumpcap” for viewing with Wireshark
 
 Dumpcap is a network traffic dump tool. It captures packet data from a live
-network and writes the packets to a file. Dumpcap's native capture file format
+network and writes the packets to a file. Dumpcap’s native capture file format
 is pcapng, which is also the format used by Wireshark.
 
 Without any options set it will use the pcap library to capture traffic
@@ -149,13 +149,13 @@ Mergecap is a program that combines multiple saved capture files into a single
 output file specified by the `-w` argument. Mergecap knows how to read libpcap
 capture files, including those of tcpdump. In addition, Mergecap can read
 capture files from snoop (including Shomiti) and atmsnoop, LanAlyzer, Sniffer
-(compressed or uncompressed), Microsoft Network Monitor, AIX's iptrace, NetXray,
-Sniffer Pro, RADCOM's WAN/LAN analyzer, Lucent/Ascend router debug output,
-HP-UX's nettl, and the dump output from Toshiba's ISDN routers. There is no need
+(compressed or uncompressed), Microsoft Network Monitor, AIX’s iptrace, NetXray,
+Sniffer Pro, RADCOM’s WAN/LAN analyzer, Lucent/Ascend router debug output,
+HP-UX’s nettl, and the dump output from Toshiba’s ISDN routers. There is no need
 to tell Mergecap what type of file you are reading; it will determine the file
 type by itself. Mergecap is also capable of reading any of these file formats if
 they are compressed using `gzip`. Mergecap recognizes this directly from the
-file; the ``.gz'' extension is not required for this purpose.
+file; the “.gz” extension is not required for this purpose.
 
 By default, it writes the capture file in pcapng format, and writes all of the
 packets in the input capture files to the output file. The `-F` flag can be used
@@ -167,10 +167,10 @@ Network Monitor 1.x format, and the format used by Windows-based versions of the
 Sniffer software.
 
 Packets from the input files are merged in chronological order based on each
-frame's timestamp, unless the `-a` flag is specified. Mergecap assumes that
+frame’s timestamp, unless the `-a` flag is specified. Mergecap assumes that
 frames within a single capture file are already stored in chronological order.
 When the `-a` flag is specified, packets are copied directly from each input
-file to the output file, independent of each frame's timestamp.
+file to the output file, independent of each frame’s timestamp.
 
 If the `-s` flag is used to specify a snapshot length, frames in the input file
 with more captured data than the specified snapshot length will have only the
@@ -242,7 +242,7 @@ is a sample dump that `text2pcap` can recognize:
 There is no limit on the width or number of bytes per line. Also the text dump
 at the end of the line is ignored. Bytes/hex numbers can be uppercase or
 lowercase. Any text before the offset is ignored, including email forwarding
-characters `>'. Any lines of text between the bytestring lines is ignored.
+characters “>”. Any lines of text between the bytestring lines is ignored.
 The offsets are used to track the bytes, so offsets must be correct. Any line
 which has only bytes without a leading offset is ignored. An offset is
 recognized as being a hex number longer than two characters. Any text after the
@@ -256,7 +256,7 @@ of mangled outputs (including being forwarded through email multiple times, with
 limited line wrap etc.)
 
 There are a couple of other special features to note. Any line where the first
-non-whitespace character is `#' will be ignored as a comment. Any line beginning
+non-whitespace character is “#” will be ignored as a comment. Any line beginning
 with #TEXT2PCAP is a directive and options can be inserted after this command to
 be processed by `text2pcap`. Currently there are no directives implemented; in the
 future, these may be used to give more fine grained control on the dump and the