acrolinx

TylerMSFT · TylerMSFT · commit 75b7f06d085e · 2025-01-10T15:19:52.000-08:00
diff --git a/docs/code-quality/c26838.md b/docs/code-quality/c26838.md
@@ -4,7 +4,7 @@
 # For valid values of ms.service, ms.prod, and ms.topic, see https://review.learn.microsoft.com/en-us/help/platform/metadata-taxonomies?branch=main
 
 title: Warning C26838
-description: Learn about Microsoft C++ code analysis warning. C26838
+description: Learn about Microsoft C++ code analysis warning C26838.
 author: Rastaban
 ms.author: philc
 ms.topic: reference
@@ -29,7 +29,7 @@ int* CreateIntArray(int numberOfElements)
 }
 ```
 
-In the expression `numberOfElements * sizeof(int)`, `numberOfElements` is signed and `sizeof(int)` is unsigned. On 64 bit machines `numberOfElements` will be promoted to an unsigned value when multiplied
+In the expression `numberOfElements * sizeof(int)`, `numberOfElements` is signed and `sizeof(int)` is unsigned. On 64-bit machines, `numberOfElements` is promoted to an unsigned value when multiplied
 by `sizeof(int)`. When `numberOfElements` is negative, the resulting value may overflow or have unexpected results when passed to `CustomAlloc`.
 
 This check applies to common allocation functions like `new`, `malloc`, and `VirtualAlloc`. The check also applies to custom allocator functions that have `alloc` (case insensitive) in the function name.
@@ -57,7 +57,7 @@ int* CreateIntArray(int numberOfElements)
 ```
 
 In the previous example, checking for a negative value addresses the C26832 warning. Depending on the size of the types involved, this check may result in a different warning such as [`C26831`](c26831.md).
-For example, on a 32 bit system, both `int` and `size_t` are 32 bits, so the result of the multiplication can still overflow without negative values.
+For example, on a 32-bit system, both `int` and `size_t` are 32 bits, so the result of the multiplication can still overflow without negative values.
 
 ## See also
 
diff --git a/docs/code-quality/c26839.md b/docs/code-quality/c26839.md
@@ -16,7 +16,7 @@ ms.date: 1/10/2025
 
 ## Remarks
 
-This warning reports that the size specified for a array new allocation may be the result of the conversion of a possibly negative signed value to an unsigned value. For example:
+This warning reports that the size specified for an array new allocation may be the result of the conversion of a possibly negative signed value to an unsigned value. For example:
 
 ```cpp
 int* CreateIntArray(int size)
@@ -26,7 +26,7 @@ int* CreateIntArray(int size)
 }
 ```
 
-In the expression `new int[size]`, `size` is signed. The compiler will convert the signed value to an unsigned value when calculating how many bytes need to be allocated for the array.
+In the expression `new int[size]`, `size` is signed. The compiler converts the signed value to an unsigned value to calculate how many bytes need to be allocated for the array.
 When `size` is negative, the result of that calculation may overflow or have unexpected results.
 
 This check is the same as [`C26838`](c26838.md), but applies only to array new `new T[]`.
