Fix spelling errors in the documentation

doc/README.developer

@@ -408,7 +408,7 @@ tmpnam is insecure and should not be used any more. Wireshark brings its
 own mkstemp implementation for use on platforms that lack mkstemp.
 Note: mkstemp does not accept NULL as a parameter.
 
-Wireshark requires mininum versions of each of the libraries it uses, in
+Wireshark requires minimum versions of each of the libraries it uses, in
 particular GLib 2.32.0 and Qt 5.3.0 or newer. If you require a mechanism
 that is available only in a newer version of a library then use its
 version detection macros, e.g. "#if GLIB_CHECK_VERSION(...)" and "#if

doc/README.dissector

@@ -1893,7 +1893,7 @@ in the past.
 proto_tree_add_item_ret_XXX()
 ------------------------------
 proto_tree_add_item_ret_XXX is used when you want the displayed value returned
-for futher processing only integer and unsigned integer types up to 32 bits are
+for further processing only integer and unsigned integer types up to 32 bits are
 supported usage of proper FT_ is checked.
 
 proto_tree_add_XXX_item()
@@ -3223,7 +3223,7 @@ persistent data about the packet for the lifetime of the capture (file scope)
 and to exchange data between dissectors across a single packet (packet scope).
 It is also used to provide packet data for Decode As dialog (packet scope).
 
-These functions are delcared in <epan/proto_data.h>.
+These functions are declared in <epan/proto_data.h>.
 
 void
 p_add_proto_data(wmem_allocator_t *scope, packet_info *pinfo, int proto, guint32 key, void *proto_data)

doc/ciscodump.pod

@@ -51,7 +51,7 @@ S<B<--remote-interface>=E<lt>the router interfaceE<gt>>
 
 =head1 DESCRIPTION
 
-B<Ciscodump> is an extcap tool that relys on Cisco EPC to allow a user to run a remote capture
+B<Ciscodump> is an extcap tool that relies on Cisco EPC to allow a user to run a remote capture
 on a Cisco router in a SSH connection. The minimum IOS version supporting this feature is 12.4(20)T. More details can be
 found here:
 https://www.cisco.com/c/en/us/products/collateral/ios-nx-os-software/ios-embedded-packet-capture/datasheet_c78-502727.html

doc/editcap.pod

@@ -239,7 +239,7 @@ This is useful for recreating a particular sequence of errors.
 =item --skip-radiotap-header
 
 Skip the radiotap header of each frame when checking for packet duplicates. This is useful
-when processing a caputure created by combining outputs of multiple capture devices on the same
+when processing a capture created by combining outputs of multiple capture devices on the same
 channel in the vicinity of each other.
 
 =item -S  E<lt>strict time adjustmentE<gt>

doc/extcap_example.py

@@ -24,7 +24,7 @@ the extcap folder, with the following content:
 -------
 
 Windows is not able to execute Python scripts directly, which also goes for all
-other script-based formates beside VBScript
+other script-based formats beside VBScript
 }
 
 """
@@ -222,7 +222,7 @@ def pcap_fake_header():
     header += struct.pack('<H', unsigned(2))  # Pcap Major Version
     header += struct.pack('<H', unsigned(4))  # Pcap Minor Version
     header += struct.pack('<I', int(0))  # Timezone
-    header += struct.pack('<I', int(0))  # Accurancy of timestamps
+    header += struct.pack('<I', int(0))  # Accuracy of timestamps
     header += struct.pack('<L', int('0000ffff', 16))  # Max Length of capture frame
     header += struct.pack('<L', unsigned(1))  # Ethernet
     return header
@@ -439,7 +439,7 @@ if __name__ == '__main__':
     parser.add_argument("--delay", help="Demonstrates an integer variable", type=int, default=0, choices=[0, 1, 2, 3, 4, 5, 6] )
     parser.add_argument("--remote", help="Demonstrates a selector choice", default="if1", choices=["if1", "if2", "if3", "if4"] )
     parser.add_argument("--message", help="Demonstrates string variable", nargs='?', default="" )
-    parser.add_argument("--fake_ip", help="Add a fake sender IP adress", nargs='?', default="127.0.0.1" )
+    parser.add_argument("--fake_ip", help="Add a fake sender IP address", nargs='?', default="127.0.0.1" )
     parser.add_argument("--ts", help="Capture start time", action="store_true" )
 
     try:

doc/wireshark.pod.template

@@ -243,9 +243,9 @@ B<files>:I<value> begin again with the first file after I<value> number of
 files were written (form a ring buffer).  This value must be less than 100000.
 Caution should be used when using large numbers of files: some filesystems do
 not handle many files in a single directory well.  The B<files> criterion
-requires one of the other critereon to be specified to
+requires one of the other criteria to be specified to
 control when to go to the next file.  It should be noted that each B<-b>
-parameter takes exactly one criterion; to specify two criterion, each must be
+parameter takes exactly one criterion; to specify two criteria, each must be
 preceded by the B<-b> option.
 
 B<filesize>:I<value> switch to the next file after it reaches a size of

docbook/wsdg_src/WSDG_chapter_quick_setup.adoc

@@ -408,7 +408,7 @@ At the end of the CMake generation process the following should be displayed:
 -- Build files have been written to: C:/Development/wsbuild64
 ----
 
-If you get any other output, there is an issue in your envirnment that must be rectified before building.
+If you get any other output, there is an issue in your environment that must be rectified before building.
 Check the parameters passed to CMake, especially the `-G` option and the path to the Wireshark sources and
 the environment variables `WIRESHARK_BASE_DIR` and `QT5_BASE_DIR`.
 

docbook/wsdg_src/WSDG_chapter_tools.adoc

@@ -67,7 +67,7 @@ is a notable example. While it's typically installed in a top-level
 directory, e.g. _C:\Python37_ or in %PROGRAMFILES%, e.g. _C:\Program
 Files\Python37_, Chocolatey tends to install it under
 _C:\ProgramData\chocolatey_ or _C:\Tools_. If you want to avoid this
-behavior you'll probabaly want to install Python using the packages from
+behavior you'll probably want to install Python using the packages from
 python.org.
 
 Other package managers for Windows include the https://docs.microsoft.com/en-us/windows/package-manager/[Windows Package Manager (winget)] and https://scoop.sh/[Scoop].

docbook/wsug_src/WSUG_chapter_build_install.adoc

@@ -204,9 +204,9 @@ the main Npcap site at {npcap-main-url}.
 
 ==== Update Wireshark
 
-The offical Wireshark Windows package will check for new versions and notify
+The official Wireshark Windows package will check for new versions and notify
 you when they are available. If you have the _Check for updates_ preference
-disabled or if you run Wireshark in an isolated environment you should subcribe
+disabled or if you run Wireshark in an isolated environment you should subscribe
 to the _wireshark-announce_ mailing list to be notified of new versions.
 See <<ChIntroMailingLists>> for details on subscribing to this list.
 

docbook/wsug_src/WSUG_chapter_customize.adoc

@@ -733,7 +733,7 @@ into the search box.
 Type selection::
 Profiles can be filtered between displaying "All profiles", "Personal profiles"
 and "Global profiles"
-* Personal profiles - these are profiles stored in the user's configuration dirctory
+* Personal profiles - these are profiles stored in the user's configuration directory
 * Global profiles - these are profiles provided with Wireshark
 
 New (+)::
@@ -1131,7 +1131,7 @@ https://grpc.io/[gRPC]) based on the message, enum and field definitions.
 You can specify protobuf search paths at the Protobuf protocol preferences.
 For example, if you defined a proto file with path `d:/my_proto_files/helloworld.proto`
 and the `helloworld.proto` contains a line of `import "google/protobuf/any.proto";`
-because the `any` type of offical protobuf library is used. And the real path of
+because the `any` type of official protobuf library is used. And the real path of
 `any.proto` is `d:/protobuf-3.4.1/include/google/protobuf/any.proto`. You should
 add the `d:/protobuf-3.4.1/include/` and `d:/my_proto_files` paths into protobuf
 search paths.
@@ -1147,7 +1147,7 @@ This specifies a directory containing protobuf source files. For example,
 Load all files::
 If this option is enabled, Wireshark will load all *.proto files in this directory
 and its subdirectories when Wireshark startup or protobuf search paths preferences
-changed. Note that the source directories that configured to protobuf offical or third
+changed. Note that the source directories that configured to protobuf official or third
 libraries path (like `d:/protobuf-3.4.1/include/`) should not be set to load all
 files, that may cause unnecessary memory use.
 

docbook/wsug_src/WSUG_chapter_statistics.adoc

@@ -411,7 +411,7 @@ The sum of the values of the field specified in “Y Field” per interval.
 
 COUNT FRAMES(Y Field):::
 The number of frames that contain the field specified in “Y Field” per interval.
-Unlike thie plain “Packets” graph, this always displays <<ChStatIOGraphsMissingValues, zero values>>.
+Unlike the plain “Packets” graph, this always displays <<ChStatIOGraphsMissingValues, zero values>>.
 
 COUNT FIELDS(Y Field):::
 The number of instances of the field specified in “Y Field” per interval.

docbook/wsug_src/WSUG_chapter_use.adoc

@@ -749,7 +749,7 @@ image::wsug_graphics/ws-tools-menu.png[{screenshot-attrs}]
 It is assumed that the rules will be applied to an outside interface.
 
 |menu:Lua[]|| These options allow you to work with the Lua interpreter optionally build into Wireshark. See the “Lua Support in Wireshark” in the Wireshark Developer’s Guide.
-|menu:Credentials[]|| This allows you to extract credentials from the current capture file. Some of the dissectors have been instrumented to provide the module with usernames and passwords and more will be instrumented in te future. The window dialog provides you the packet number where the credentials have been found, the protocol that provided them, the username and the password.
+|menu:Credentials[]|| This allows you to extract credentials from the current capture file. Some of the dissectors have been instrumented to provide the module with usernames and passwords and more will be instrumented in the future. The window dialog provides you the packet number where the credentials have been found, the protocol that provided them, the username and the password.
 |===
 
 [[ChUseHelpMenuSection]]