oleaut32: Fix the spelling of some comments.

dlls/oleaut32/dispatch.c

@@ -176,7 +176,7 @@ done:
  *  (linked at run-time), as opposed to early-bound (linked at compile time).
  *
  *  The interface is used by objects that wish to called by scripting
- *  languages such as VBA, in order to minimise the amount of COM and C/C++
+ *  languages such as VBA, in order to minimize the amount of COM and C/C++
  *  knowledge required, or by objects that wish to live out of process from code
  *  that will call their methods.
  *

dlls/oleaut32/tests/vartype.c

@@ -5934,7 +5934,7 @@ static void test_bstr_cache(void)
     str = SysAllocStringLen(NULL, 24);
     ok(str == strs[0], "str != strs[0]\n");
 
-    /* Smaller buffers may also use larget cached buffers */
+    /* Smaller buffers may also use larger cached buffers */
     str2 = SysAllocStringLen(NULL, 16);
     ok(str2 == strs[1], "str2 != strs[1]\n");
 

dlls/oleaut32/typelib.c

@@ -4202,7 +4202,7 @@ static void SLTG_DoFuncs(char *pBlk, char *pFirstItem, ITypeInfoImpl *pTI,
 	       letter of the name, else the next WORD is an offset to
 	       the arg type and paramName points to the first letter.
 	       So let's take one char off paramName and see if we're
-	       pointing at an alpha-numeric char.  However if *pArg is
+	       pointing at an alphanumeric char.  However if *pArg is
 	       0xffff or 0xfffe then the param has no name, the former
 	       meaning that the next WORD is the type, the latter
 	       meaning that the next WORD is an offset to the type. */

dlls/oleaut32/typelib.h

@@ -325,7 +325,7 @@ typedef struct {
 } SLTG_BlkEntry;
 
 /* The order of the blocks in the file is given by starting at Block
-   entry firt_blk and stepping through using the next pointer */
+   entry first_blk and stepping through using the next pointer */
 
 /* These then get followed by this magic */
 typedef struct {