Update Win32API-File to CPAN version 0.1200

[perl5.git] / cpan / Win32API-File / buffers.h

diff --git a/cpan/Win32API-File/buffers.h b/cpan/Win32API-File/buffers.h
index 934e57b..cc114e5 100644 (file)
--- a/cpan/Win32API-File/buffers.h
+++ b/cpan/Win32API-File/buffers.h
@@ -52,7 +52,7 @@
  * the size of the written data.  This is what the trunc_*() macros are for.
  *
  * The size sometimes does and sometimes doesn't include the trailing '\0'
- * [or L'\0'], so we always add or substract 1 in the appropriate places so
+ * [or L'\0'], so we always add or subtract 1 in the appropriate places so
  * we don't care about this detail.
  *
  * A call may  1) request a pointer to the buffer size which means that
@@ -70,7 +70,7 @@
  *
  * The user can pass in C<[]> or C<0> to indicate that they don't care about
  * the buffer size [we aren't programming in C here, after all] and just try
- * to get the data.  This will work if either the buffer already alloated for
+ * to get the data.  This will work if either the buffer already allocated for
  * the SV [scalar value] is large enough to hold the data or the API provides
  * an easy way to determine the required size [and the XS code uses it].
  *
@@ -96,7 +96,7 @@
  * section [grow_*()], the INIT: section [init_*()], or the OUTPUT: section
  * [trunc_*()].
  *
- * Buffer arguments should be initialied with C<= NO_INIT> [or C<= NULL;>].
+ * Buffer arguments should be initialised with C<= NO_INIT> [or C<= NULL;>].
  *
  * See also the F<typemap> file.  C<oDWORD>, for example, is for an output-
  * only parameter of type C<DWORD> and you should simply C<#define> it to be
@@ -119,9 +119,9 @@
  * determine the size of data written based on the size of the scalar we
  * output anyway.
  *
- * This second difference doesn't apply unless the paremter is listed in
+ * This second difference doesn't apply unless the parameter is listed in
  * the OUTPUT: section without specific output instructions.  We define
- * no macros for outputing buffer length parameters so be careful to use
+ * no macros for outputting buffer length parameters so be careful to use
  * C<oDWORD> [for example] for them if and only if they are output-only.
  *
  * Note that C<oDWORD> is the same as C<DWORD> in that, if a defined value
@@ -372,7 +372,7 @@
            SvCUR_set( svBuf, lSize );                                  \
        } } STMT_END
 
-/* Same as above except we have a poitner to the returned length: */
+/* Same as above except we have a pointer to the returned length: */
 #define        trunc_buf_pl( bOkay, sBuf,svBuf, plSize )                       \
        trunc_buf_l( bOkay, sBuf,svBuf, *plSize )
 
@@ -383,7 +383,7 @@
            SvCUR_set( svBuf, (lwSize)*sizeof(WCHAR) );                 \
        } } STMT_END
 
-/* Same as above except we have a poitner to the returned length: */
+/* Same as above except we have a pointer to the returned length: */
 #define        trunc_buf_plw( bOkay, swBuf,svBuf, plwSize )                    \
        trunc_buf_lw( bOkay, swBuf,svBuf, *plwSize )