aboutsummaryrefslogtreecommitdiffstats
path: root/doc
diff options
context:
space:
mode:
Diffstat (limited to 'doc')
-rw-r--r--doc/README.wmem2
-rw-r--r--doc/README.wslua4
-rw-r--r--doc/tshark.pod2
-rw-r--r--doc/wireshark-filter.pod2
4 files changed, 5 insertions, 5 deletions
diff --git a/doc/README.wmem b/doc/README.wmem
index 24a838952b..9724e24a3a 100644
--- a/doc/README.wmem
+++ b/doc/README.wmem
@@ -108,7 +108,7 @@ wmem_stack.h
wmem_tree.h
- A balanced binary tree (red-black tree) implementation.
-2.2.4 Miscellanious Utilities
+2.2.4 Miscellaneous Utilities
wmem_miscutl.h
- Misc. utility functions like memdup.
diff --git a/doc/README.wslua b/doc/README.wslua
index 4deb39682d..0d2fce759f 100644
--- a/doc/README.wslua
+++ b/doc/README.wslua
@@ -129,7 +129,7 @@ the former __index/__newindex metamethod model does not. Both models are
fairly common in Lua APIs, although having a mixture of both in the same API
probably isn't. There is even a third model in use: pre-loading the member
fields of the class table with the values, instead of waiting for the Lua
-script to access a particular one to retrieve it; for exmaple the Listener tap
+script to access a particular one to retrieve it; for example the Listener tap
extractors table is pre-populated (see files 'wslua_listener.c' and 'taps'
which through the make-taps.pl perl script creates 'taps_wslua.c'). The
downside of that approach is the performance impact, filling fields the Lua
@@ -392,7 +392,7 @@ Example:
WSLUA_ERROR - this C macro takes arguments, and expands to call luaL_error()
using them, and returns 0. The arguments it takes is the full function name
and a string describing the error. For documentation, it uses the string
-arguement and displays it with the function it's associated to.
+argument and displays it with the function it's associated to.
Example:
if (!wtap_dump_can_write_encap(filetype, encap))
diff --git a/doc/tshark.pod b/doc/tshark.pod
index 4d5b5ed4af..23f95f60e6 100644
--- a/doc/tshark.pod
+++ b/doc/tshark.pod
@@ -994,7 +994,7 @@ display the contents of a TCP stream between 200.57.7.197 port 32891 and
===================================================================
Follow: tcp,ascii
- Filter: (ommitted for readability)
+ Filter: (omitted for readability)
Node 0: 200.57.7.197:32891
Node 1: 200.57.7.198:2906
38
diff --git a/doc/wireshark-filter.pod b/doc/wireshark-filter.pod
index d4523c5b00..79f1697572 100644
--- a/doc/wireshark-filter.pod
+++ b/doc/wireshark-filter.pod
@@ -246,7 +246,7 @@ or
frame[-4:] == 0.1.2.3
-A slice is alwasy compared against either a string or a byte sequence.
+A slice is always compared against either a string or a byte sequence.
As a special case, when the slice is only 1 byte wide, you can compare
it against a hex integer that 0xff or less (which means it fits inside
one byte). This is not allowed for byte sequences greater than one byte,