Update docs/code-quality/c26833.md

Co-authored-by: dmitrykobets-msft <[email protected]>

Author: Xazax-hun

docs/code-quality/c26833.md

@@ -31,7 +31,7 @@ void foo(unsigned i, unsigned j)
 The code example above has a check `size > 50`. Unfortunately, this check is too late. In case `i + j` overflows, it produces a small value that passes the check. So, `SmallAlloc` allocates a buffer smaller than expected. Future accesses of the buffer like `p[i]` are out of bounds. These code patterns can result in remote code execution vulnerabilities.
 Common allocation functions like `new`, `malloc`, and `VirtualAlloc` are recognized. The check also tries to recognize custom allocator functions by case insensitive search for the `alloc` substring in the function name.
 
-Our analysis engine's numerical solver have some limitations reasoning about numerical overflows. As a result, this check is using some heuristics and sometimes fails to recognize that certain checks can prevent overflows.
+Our analysis engine's numerical solver have some limitations reasoning about numerical overflows. As a result, this check uses some heuristics and sometimes fails to recognize that certain checks can prevent overflows.
 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.