From 371179340e55e4ae640e84af5a905ce5136f1c90 Mon Sep 17 00:00:00 2001 From: Stephen Fisher Date: Mon, 19 Feb 2007 00:23:58 +0000 Subject: Fix a couple of spelling mistakes svn path=/trunk/; revision=20840 --- doc/README.request_response_tracking | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) (limited to 'doc/README.request_response_tracking') 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 #include -- cgit v1.2.1