aboutsummaryrefslogtreecommitdiffstats
path: root/epan/dissectors/packet-ajp13.c
diff options
context:
space:
mode:
authormoshekaplan <me@moshekaplan.com>2016-01-05 19:58:42 -0500
committerMichael Mann <mmann78@netscape.net>2016-01-08 20:04:56 +0000
commitcd7026951b2354cb633b51cd82d6de0a0f622f00 (patch)
tree98e01231a03392a988f8621a8cbc6f7553bce0ca /epan/dissectors/packet-ajp13.c
parentc1bcbb6eee97239be09d820ca3c16c46cf072fc6 (diff)
Fix a lot of typos and misspellings
Change-Id: I8512cfa1d424f82a873a0e0e1d22c7b075fdd7f3 Reviewed-on: https://code.wireshark.org/review/13069 Reviewed-by: Alexis La Goutte <alexis.lagoutte@gmail.com> Petri-Dish: Alexis La Goutte <alexis.lagoutte@gmail.com> Tested-by: Petri Dish Buildbot <buildbot-no-reply@wireshark.org> Reviewed-by: Michael Mann <mmann78@netscape.net>
Diffstat (limited to 'epan/dissectors/packet-ajp13.c')
-rw-r--r--epan/dissectors/packet-ajp13.c4
1 files changed, 2 insertions, 2 deletions
diff --git a/epan/dissectors/packet-ajp13.c b/epan/dissectors/packet-ajp13.c
index 912d68e1e9..54e6de2f17 100644
--- a/epan/dissectors/packet-ajp13.c
+++ b/epan/dissectors/packet-ajp13.c
@@ -78,7 +78,7 @@ void proto_reg_handoff_ajp13(void);
* looking at raw network packets, aren't we? The stuff on the
* wire. Wireshark has been getting better and better at helping
* dissectors with this. I'm a little fuzzy on the details, but my
- * uderstanding is that wireshark now contains a fairly substantial
+ * understanding is that wireshark now contains a fairly substantial
* user-space TCP/IP stack so it can re-assemble the data. But I might
* be wrong. Since AJP13 is going to be used either on the loopback
* interface or on a LAN, it isn't likely to be a big issues anyway.
@@ -89,7 +89,7 @@ void proto_reg_handoff_ajp13(void);
* PDU can stretch across multiple TCP segments. Assembling them is
* obviously possible, but a royal pain. During the "phase one"
* in-order pass you have to keep track of a bunch of offsets and
- * store which PDU goes with which TCP segment. Luckly, recent
+ * store which PDU goes with which TCP segment. Luckily, recent
* (0.9.4+) versions of wireshark provide the "tcp_dissect_pdus()"
* function that takes care of much of the work. See the comments in
* packet-tcp.c, the example code in packet-dns.c, or check the