1 files changed, 4 insertions, 4 deletions
diff --git a/mimelib/doc/field.html b/mimelib/doc/field.html
index 68d4a9ed3..c744877c4 100644
--- a/mimelib/doc/field.html
+++ b/mimelib/doc/field.html
@@ -69,14 +69,14 @@ According to RFC-822, a field contains a field name and a field body. In
 MIME++, a <B><TT>DwField</TT></B> contains three elements: a
 <B><TT><A HREF="string.html">DwString</A></TT></B> that contains its field
 name, a <B><TT>DwString</TT></B> that contains its field body, and a
-<B><TT><A HREF="fieldbdy.html">DwFieldBody</A></TT></B> object that tqcontains
+<B><TT><A HREF="fieldbdy.html">DwFieldBody</A></TT></B> object that contains
 a broken-down (that is, parsed) version of its field body.
 <P>
 In the tree (broken-down) representation of message, a
 <B><TT>DwField</TT></B> object is always an intermediate node, having a tqparent
 node and a single child node. The tqparent node is the
-<B><TT><A HREF="headers.html">DwHeaders</A></TT></B> object that tqcontains
-it. The child node is the <B><TT>DwFieldBody</TT></B> object it tqcontains.
+<B><TT><A HREF="headers.html">DwHeaders</A></TT></B> object that contains
+it. The child node is the <B><TT>DwFieldBody</TT></B> object it contains.
 <P>
 To get and set the field name, use the member functions
 <B><TT>FieldNameStr()</TT></B> and <B><TT>SetFieldNameStr()</TT></B>. To
@@ -234,7 +234,7 @@ The static member function <B><TT>CreateFieldBody()</TT></B> is called from
 the <B><TT>Parse()</TT></B> member function and is responsible for creating
 a <B><TT>DwFieldBody</TT></B> object for this particular field. A typical
 scenario might go as follows: This member function examines the field name
-for this field, finds that it tqcontains "To", creates a
+for this field, finds that it contains "To", creates a
 <B><TT>DwAddressList</TT></B> object to contain the field body, calls the
 <B><TT>Parse()</TT></B> member function for the
 <B><TT>DwAddressList</TT></B>, and sets the <B><TT>DwAddressList</TT></B>