Updated C28159

Acrolinx fixes

Author: MugBergerFries

docs/code-quality/c28159.md

@@ -11,24 +11,24 @@ ms.assetid: fab6cd58-0985-4ef6-89a2-64ed04297437
 
 > Consider using `\**function_name_1*` instead of `\**function_name_2*`. Reason: `\**reason*`
 
-This warning occurs when that you use a function that is semantically equivalent to an alternative, preferred function call. 
+This warning occurs when you use a function that is semantically equivalent to an alternative, preferred function call. 
 
 ## Remarks
 
-This is a general warning message; the annotation `__drv_preferredFunction` was used (possibly with a conditional a `__drv_when`() annotation) to flag a bad coding practice.
+C28159 is a general warning message; the annotation `__drv_preferredFunction` was used (possibly with a conditional `__drv_when`() annotation) to flag a bad coding practice.
 
 Code analysis name: USE_OTHER_FUNCTION
 
 ## Example
 
-The following code example generates this warning. This issue is due to the use of `OemToChar`, which does not validate the buffer size:
+The following code example generates this warning. This issue is due to the use of `OemToChar`, which doesn't validate the buffer size:
 
 ```cpp
 char buff[MAX_PATH];
 OemToChar(buff, input);  // If strlen(input) > MAX_PATH, this call leads to buffer overrun
 ```
 
-The following code example avoids this warning by using the recommended alternative `OemToCharBuff`, which takes in the destination buffer size and limits the copy appropriatly:
+The following code example avoids this warning by using the recommended alternative `OemToCharBuff`, which takes in the destination buffer size and limits the copy appropriately:
 
 ```cpp
 char buff[MAX_PATH];