Index: ossp-pkg/xds/docs/libxds.tex
RCS File: /v/ossp/cvs/ossp-pkg/xds/docs/libxds.tex,v
rcsdiff -q -kk '-r1.14' '-r1.15' -u '/v/ossp/cvs/ossp-pkg/xds/docs/libxds.tex,v' 2>/dev/null
--- libxds.tex	2001/08/09 15:35:23	1.14
+++ libxds.tex	2001/08/13 14:19:57	1.15
@@ -302,7 +302,7 @@
 buffer as a ``gift'' (\textsf{XDS\_GIFT}) or as a ``loan'' (\textsf{XDS\_LOAN}).
 
 The buffer being a ``loan'' means that the buffer is still owned by the
-library --- we're only allowed to peak at it. But any call to an XDS
+library --- we're only allowed to peek at it. But any call to an XDS
 routine may potentially modify the buffer or even change the buffers
 location. Hence the result of a \textsf{xds\_getbuffer()} call with loaning
 semantics is only valid until the next XDS routine is called. After
@@ -479,7 +479,7 @@
 matter whether loan or gift semantics have been chosen.
 
 \paragraph{Lines 53--54.}
-Here come the actual decoding of the buffer's contents using {\sf
+Here comes the actual decoding of the buffer's contents using {\sf
 xds\_decode()}. The syntax is identical to \textsf{xds\_encode()}'s, the only
 difference is that the decoding engines do not expect the values --- like
 the encoding engines did --- but the location where to store the value.