X-Git-Url: http://git.indexdata.com/?a=blobdiff_plain;ds=sidebyside;f=doc%2Fintroduction.xml;h=5222a2d7fae5c968f60afa9961e56a34a55e3893;hb=3b3deb4d093d747360a5eb0e02c6b4e9c8a89b84;hp=785bc82a21c408e8dc53d0f91e77f8dbcc8e9706;hpb=ce853cc4919ab346fd629e7727905d3ee6e1129f;p=yaz-moved-to-github.git

diff --git a/doc/introduction.xml b/doc/introduction.xml
index 785bc82..5222a2d 100644
--- a/doc/introduction.xml
+++ b/doc/introduction.xml
@@ -1,4 +1,4 @@
-<!-- $Id: introduction.xml,v 1.2 2001-07-19 23:29:40 adam Exp $ -->
+<!-- $Id: introduction.xml,v 1.3 2001-08-13 09:42:54 adam Exp $ -->
  <chapter><title>Introduction</title>
   
   <para>
@@ -69,7 +69,7 @@
    and for exchanging BER-encoded PDUs over that connection. When you
    create a connection endpoint, you need to specify what transport to
    use (OSI or TCP/IP), and which protocol you want to use (SR or
-   Z39.50). For the remainer of the connection's lifetime, you don't have
+   Z39.50). For the remainder of the connection's lifetime, you don't have
    to worry about the underlying transport protocol at all - the &comstack;
    will ensure that the correct mechanism is used.
   </para>
@@ -86,7 +86,7 @@
    if you don't like the protocol API provided by &odr;/&asn;, you
    can use SNACC or BERUtils instead, and still have the benefits of the
    transparent transport approach of the &comstack; module. Secondly,
-   we realise that you may have to fit the toolkit into an existing
+   we realize that you may have to fit the toolkit into an existing
    event-processing structure, in a way that
    is incompatible with the &comstack; interface or some other part of &yaz;.
   </para>