aboutsummaryrefslogtreecommitdiffstats
path: root/doc/README.request_response_tracking
diff options
context:
space:
mode:
authorStephen Fisher <steve@stephen-fisher.com>2007-02-19 00:23:58 +0000
committerStephen Fisher <steve@stephen-fisher.com>2007-02-19 00:23:58 +0000
commit371179340e55e4ae640e84af5a905ce5136f1c90 (patch)
treea4429a62762445739b8f43d202a4ebcdbb39c816 /doc/README.request_response_tracking
parentab177ee1cd538ee54e7b0feaf2fe211f86b412c4 (diff)
Fix a couple of spelling mistakes
svn path=/trunk/; revision=20840
Diffstat (limited to 'doc/README.request_response_tracking')
-rw-r--r--doc/README.request_response_tracking4
1 files changed, 2 insertions, 2 deletions
diff --git a/doc/README.request_response_tracking b/doc/README.request_response_tracking
index d22b53ca75..031bb9f686 100644
--- a/doc/README.request_response_tracking
+++ b/doc/README.request_response_tracking
@@ -12,7 +12,7 @@ response packet and without the opcode we would not know how to decode the
data.
It is also useful when you need to track information on a per conversation
-basis such as when some parameters are negotiatiod during a login phase of the
+basis such as when some parameters are negotiated during a login phase of the
protocol and when these parameters affect how future commands on that
session are to be decoded. The iSCSI dissector does something similar to that
to track which sessions that HeaderDigest is activated for and which ones
@@ -29,7 +29,7 @@ The example is taken from the PANA dissector :
First we need to include the definitions for conversations and memory
-magament
+management
#include <epan/conversation.h>
#include <epan/emem.h>