Index: ossp-pkg/sio/al.pod
RCS File: /v/ossp/cvs/ossp-pkg/sio/Attic/al.pod,v
rcsdiff -q -kk '-r1.6' '-r1.7' -u '/v/ossp/cvs/ossp-pkg/sio/Attic/al.pod,v' 2>/dev/null
--- al.pod	2002/10/17 13:15:07	1.6
+++ al.pod	2002/10/17 14:57:44	1.7
@@ -173,22 +173,22 @@
 
 =item al_rc_t B<al_append_bytes>(al_t *I<al>, const char *I<src>, size_t I<n>);
 
-Append I<n> bytes from a storage array at I<src> to the assembly list, the
+Append I<n> bytes from a storage array at I<src> to the assembly list. The
 bytes are copied, memory is allocated as necessary.
 
 Example: C<al_append_bytes(al, "Goodbye cruel world\n", 20);>
 
 =item al_rc_t B<al_prepend_bytes>(al_t *I<al>, const char *I<src>, size_t I<n>);
 
-Prepend I<n> bytes from a storage array at I<src> to the assembly list, the
+Prepend I<n> bytes from a storage array at I<src> to the assembly list. The
 bytes are copied, memory is allocated as necessary.
 
 Example: C<al_prepend_bytes(al, "Hello world\n", 12);>
 
 =item al_rc_t B<al_attach_buffer>(al_t *I<al>, char *I<p>, size_t I<n>);
 
-Attach the storage array starting at I<p> with size <n> at the end of
-the assembly list. Its content will become part of the assembly list
+Attach the storage array starting at I<p> with size I<n> at the end of
+the assembly list. Its content becomes part of the assembly list
 and is subject to assembly list operations. The storage array must stay
 in scope for the whole life time of the assembly list, there is no way
 to detach it from the assembly list.
@@ -211,7 +211,7 @@
 The move from the new list I<nal> removes the data from its origin.
 
 The target list I<tal> may be B<NULL>, the data bytes that would
-be moved to the target are then discard. This avoids creation
+be moved to the target are then discarded. This avoids creation
 and destruction of a dummy target.
 
 The new list I<nal> may be B<NULL>, then nothing is inserted into