Update docs/code-quality/c26831.md

Xazax-hun · dmitrykobets-msft · web-flow · commit 1f7db3122ef1 · 2023-03-08T09:05:51.000-08:00
Co-authored-by: dmitrykobets-msft &lt;89153909+dmitrykobets-msft@users.noreply.github.com&gt;
diff --git a/docs/code-quality/c26831.md b/docs/code-quality/c26831.md
@@ -25,7 +25,7 @@ void foo(int i, int j)
 
 In case `i+j` overflows, `SmallAlloc` returns a buffer that is smaller than expected. As a result, future accesses to 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 `VirtalAlloc` are recognized. The check also tries to recognize custom allocator functions by case insensitive search for the `alloc` substring in the function name.
+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.
 Usually, checking for a reasonable bound on the allocation should work. 
