edits

Author: TylerMSFT

docs/code-quality/c26838.md

@@ -1,8 +1,4 @@
 ---
-# Required metadata
-# For more information, see https://review.learn.microsoft.com/en-us/help/platform/learn-editor-add-metadata?branch=main
-# 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.
 author: Rastaban
@@ -12,35 +8,35 @@ ms.date: 1/10/2025
 ---
 # Warning C26838
 
-> Allocation size is the result of a signed to unsigned narrowing conversion that could result in overflow if the signed value is negative
+> Allocation size is the result of a signed to unsigned narrowing conversion that could result in overflow if the signed value is negative.
+
+This warning was added in Visual Studio 2022 version 17.13.
 
 ## Remarks
 
-This warning reports that the size specified for an allocation may be the result of the conversion of a possibly negative signed value to an unsigned value. For example:
+Reports that the size specified for an allocation may be the result of the conversion of a possibly negative signed value to an unsigned value. For example:
 
 ```cpp
 void* CustomAlloc(size_t);
 
 int* CreateIntArray(int numberOfElements)
 {
     int* p = (int*)CustomAlloc(numberOfElements * sizeof(int)); // Warning: C26838
-    // ...
+
     return p;
 }
 ```
 
-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
+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.
 
 This check sometimes fails to recognize that certain checks can prevent overflows because the check is conservative.
 
-This warning is available in Visual Studio 2022 version 17.13 and later versions.
-
 ## Example
 
-To fix the previous code example in which `numberOfElements * sizeof(int)` might overflow due to a negative signed value, introduce a check to make sure it won't. For example:
+To fix the previous code example in which `numberOfElements * sizeof(int)` might overflow due to a negative signed value, introduce a check to ensure it won't. For example:
 
 ```cpp
 void* CustomAlloc(size_t);
@@ -56,13 +52,11 @@ 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.
+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.
 
 ## See also
 
 [`C26831`](c26831.md)\
 [`C26832`](c26832.md)\
 [`C26833`](c26833.md)\
-[`C26833`](c26839.md)
-
+[`C26833`](c26839.md)

docs/code-quality/c26839.md

@@ -1,8 +1,4 @@
 ---
-# Required metadata
-# For more information, see https://review.learn.microsoft.com/en-us/help/platform/learn-editor-add-metadata?branch=main
-# 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 C26839
 description: Learn about Microsoft C++ code analysis warning C26839.
 author: Rastaban
@@ -12,11 +8,13 @@ ms.date: 1/10/2025
 ---
 # Warning C26839
 
-> Array new allocation size is the result of a signed to unsigned narrowing conversion that could result in overflow if the signed value is negative
+> Array new allocation size is the result of a signed to unsigned narrowing conversion that could result in overflow if the signed value is negative.
+
+This warning was added in Visual Studio 2022 version 17.13.
 
 ## Remarks
 
-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:
+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,18 +24,15 @@ int* CreateIntArray(int size)
 }
 ```
 
-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.
+The expression `new int[size]`, `size` is signed. The compiler converts the signed value to an unsigned value to calculate how many bytes to be allocate for the array. When `size` is negative, the result of that calculation may overflow or have unexpected results when passed to `new`.
 
-This check is the same as [`C26838`](c26838.md), but applies only to array new `new T[]`.
+This check is the same as [`C26838`](c26838.md), but applies only to `new T[]`.
 
 This check sometimes fails to recognize that certain checks can prevent overflows because the check is conservative.
 
-This warning is available in Visual Studio 2022 version 17.12 and later versions.
-
 ## Example
 
-To fix the previous code example in which the size calculation might overflow due to a negative signed value, introduce a check to make sure it won't. For example:
+To fix the previous code example in which the size calculation might overflow due to a negative signed value, introduce a check to ensure it won't. For example:
 
 ```cpp
 int* CreateIntArray(int size)

docs/code-quality/toc.yml

@@ -633,7 +633,7 @@ items:
     href: ../code-quality/c26830.md
   - name: Warning C26831
     href: ../code-quality/c26831.md
-  - name: " Warning C26838"
+  - name: Warning C26838
     href: c26838.md
   - name: Warning C26839
     href: c26839.md