address various PR feedback

Author: carsonRadtke

docs/code-quality/c26865.md

@@ -4,15 +4,15 @@ title: Warning C26865
 ms.date: 10/03/2022
 f1_keywords: ["C26865", "ALLOCATION_DEALLOCATION_MISMATCH", "__WARNING_ALLOCATION_DEALLOCATION_MISMATCH"]
 helpviewer_keywords: ["C26865"]
-ms.assetid: 2fbe9dc5-fa43-47b9-97a7-3f8215da1d40 # TODO (@carsonradtke): I generated this with `PS > (New-Guid).ToString()`. Is that OK?
+ms.assetid: 2fbe9dc5-fa43-47b9-97a7-3f8215da1d40
 ---
 # Warning C26865
 
 > Memory allocated with '\<allocation-function\>' is being deallocated with '\<wrong-deallocation-function\>'. Use '\<correct-deallocation-function\>' instead.
 
 ## Remarks
 
-This warning indicates that the memory was allocated with one family of allocation functions, but was freed with a deallocation function from a different family. This usage is undefined behavior according to the C++ standard and the Microsoft C++ implementation.
+This warning indicates that the memory was allocated with one family of allocation functions, but was freed with a deallocation function from a different family. This usage results in undefined behavior according to C/C++ and the Microsoft MSVC implementation.
 
 The exact ramifications of this defect are difficult to predict. It might result in leaks for classes with destructors that perform memory deallocation. It could cause inconsistent behavior for classes with destructors that perform semantically significant operations, or memory corruptions and crashes. In other cases the mismatch might be unimportant, depending on the implementation of the compiler and its libraries. Analysis tools can't always distinguish between these situations.
 

docs/code-quality/toc.yml

@@ -661,6 +661,8 @@ items:
     href: ../code-quality/c26863.md
   - name: Warning C26864
     href: ../code-quality/c26864.md
+  - name: Warning C26864
+    href: ../code-quality/c26865.md
   - name: Warning C28020
     href: ../code-quality/c28020.md
   - name: Warning C28021