diff options
Diffstat (limited to 'epan/dissectors/packet-ajp13.c')
| -rw-r--r-- | epan/dissectors/packet-ajp13.c | 4 |
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 |