Fix review comments.

Xazax-hun · Xazax-hun · commit 5c0c49d82c1e · 2023-03-07T14:11:38.000-08:00
diff --git a/docs/code-quality/c26831.md b/docs/code-quality/c26831.md
@@ -11,7 +11,7 @@ helpviewer_keywords: ["C26831"]
 
 ## Remarks
 
-Checks for allocations that have potentially overflown values as their sizes. This check is targeted to find the following code pattern:
+Checks for an allocation whose size may be the result of a numerical overflow. This check is targeted to find the following code pattern:
 
 ```cpp
 void *SmallAlloc(int);
@@ -34,7 +34,7 @@ This warning is available in Visual Studio 2022 version 17.7 and later versions.
 
 ## Example
 
-To fix the code example above, make sure `i+j` can't overflow. For example:
+To fix the previous code example, make sure `i+j` can't overflow. For example:
 
 ```cpp
 void *SmallAlloc(int);
diff --git a/docs/code-quality/c26832.md b/docs/code-quality/c26832.md
@@ -11,7 +11,7 @@ helpviewer_keywords: ["C26832"]
 
 ## Remarks
 
-Checks for allocations that have potentially overflown values as their sizes. This check is targeted to find the following code pattern:
+Checks for an allocation whose size may be the result of a numerical overflow. This check is targeted to find the following code pattern:
 
 ```cpp
 void* SmallAlloc(int);
@@ -35,7 +35,7 @@ Usually, checking for a reasonable bound on the allocation should work.
 This warning is available in Visual Studio 2022 version 17.7 and later versions.
 ## Example
 
-To fix the code example above, make sure `i+j` can't overflow. For example:
+To fix the previous code example, make sure `i+j` can't overflow. For example:
 
 ```cpp
 void *SmallAlloc(int);
diff --git a/docs/code-quality/c26833.md b/docs/code-quality/c26833.md
@@ -11,7 +11,7 @@ helpviewer_keywords: ["C26833"]
 
 ## Remarks
 
-Checks for allocations that have potentially overflown values as their sizes. This check is targeted to find the following code pattern:
+Checks for an allocation whose size may be the result of a numerical overflow. This check is targeted to find the following code pattern:
 
 ```cpp
 void* SmallAlloc(int);
@@ -37,7 +37,7 @@ Usually, checking for a reasonable bound on the allocation should work.
 This warning is available in Visual Studio 2022 version 17.7 and later versions.
 ## Example
 
-To fix the code example above, make sure `i+j` cannot overflow. For example:
+To fix the previous code example, make sure `i+j` cannot overflow. For example:
 
 ```cpp
 void* SmallAlloc(int);
