osmith
/
wireshark
forked from osmocom/wireshark
1
0
Fork 0
Code Pull Requests Releases Wiki Activity

Fix some more doc folder spelling errors.

This commit is contained in:
Martin Mathieson 2020-09-25 22:20:21 +01:00
parent acdaf33630
commit 906ead6993
4 changed files with 11 additions and 11 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

14
doc/README.dissector
View File

@ -262,7 +262,7 @@ gint16 tvb_get_ntohis(tvbuff_t *tvb, const gint offset);
guint32 tvb_get_ntoh24(tvbuff_t *tvb, const gint offset);
gint32 tvb_get_ntohi24(tvbuff_t *tvb, const gint offset);
32-bit unsgined (guint32) and signed (gint32) integers:
32-bit unsigned (guint32) and signed (gint32) integers:
guint32 tvb_get_ntohl(tvbuff_t *tvb, const gint offset);
gint32 tvb_get_ntohil(tvbuff_t *tvb, const gint offset);
@ -3624,7 +3624,7 @@ The arguments to udp_dissect_pdus are:
For the typical dissector there is a 1-1 relationship between it and it's
protocol. However, there are times when a protocol needs multiple "names"
because it has multiple dissection functions going into the same dissector
table. The muliple names removes confusion when picking dissection through
table. The multiple names removes confusion when picking dissection through
Decode As functionality.
Once the "main" protocol name has been created through proto_register_protocol,
@ -3675,7 +3675,7 @@ be passed to the dissector table to change the dissection output.
ip_da pulls everything together including the dissector (protocol) name, the
"layer type" of the dissector, the dissector table name, the function pointer
values as well as handlers for populating, applying and reseting the changes
values as well as handlers for populating, applying and resetting the changes
to the dissector table through Decode As GUI functionality. For dissector
tables that are an integer or string type, the provided "default" handling
functions shown in the example should suffice.
@ -3736,19 +3736,19 @@ certain type of fields (See above under proto_tree_add_item()).
proto_item*
ptvcursor_add_ret_uint(ptvcursor_t* ptvc, int hf, gint length, const guint encoding, guint32 *retval);
Like ptvcursor_add, but returns uint value retreived
Like ptvcursor_add, but returns uint value retrieved
proto_item*
ptvcursor_add_ret_int(ptvcursor_t* ptvc, int hf, gint length, const guint encoding, gint32 *retval);
Like ptvcursor_add, but returns int value retreived
Like ptvcursor_add, but returns int value retrieved
proto_item*
ptvcursor_add_ret_string(ptvcursor_t* ptvc, int hf, gint length, const guint encoding, wmem_allocator_t *scope, const guint8 **retval);
Like ptvcursor_add, but returns string retreived
Like ptvcursor_add, but returns string retrieved
proto_item*
ptvcursor_add_ret_boolean(ptvcursor_t* ptvc, int hf, gint length, const guint encoding, gboolean *retval);
Like ptvcursor_add, but returns boolean value retreived
Like ptvcursor_add, but returns boolean value retrieved
proto_item*
ptvcursor_add_no_advance(ptvcursor_t* ptvc, int hf, gint length, const guint encoding)

2
doc/README.plugins
View File

@ -117,7 +117,7 @@ in the NSIS installer wireshark.nsi file.
3.2.2.1 Changes to packaging/nsis/wireshark.nsi
Add the relative path of your plugin DLL (in alphbetical order) to the
Add the relative path of your plugin DLL (in alphabetical order) to the
list of "File" statements in the "Dissector Plugins" section:
File "${STAGING_DIR}\plugins\${VERSION_MAJOR}.${VERSION_MINOR}\epan\ethercat.dll"

2
doc/README.vagrant
View File

@ -76,7 +76,7 @@ use XQuartz as your X server. XQuartz can be downloaded from
https://www.xquartz.org/.
The VM can be shutdown or suspended from the host system with the
commands `vagrant halt` and `vagrant suspend` repectively. In either case the
commands `vagrant halt` and `vagrant suspend` respectively. In either case the
VM can be brought back up with the command `vagrant up`.
5. Using Vagrant with multiple VMs

4
doc/editcap.pod
View File

@ -91,7 +91,7 @@ file; B<editcap -F> provides a list of the available output formats.
=item -a E<lt>framenum:commentE<gt>
For the specificed frame number, assign the given comment string.
For the specifiqed frame number, assign the given comment string.
Can be repeated for multiple frames. Quotes should be used with comment
strings that include spaces.
@ -238,7 +238,7 @@ This is useful for recreating a particular sequence of errors.
=item --skip-radiotap-header
Skip the readiotap header of each frame when checking for packet duplicates. This is useful
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
channel in the vicinity of each other.