Give library functions code style

Fix date. Also tweak a sentence for readability.

Author: colin-home

docs/code-quality/c6308.md

@@ -1,7 +1,7 @@
 ---
-title: C6308
+title: Warning C6308
 description: "Understand the causes of Microsoft C/C++ code analysis warning C6308, and learn how to fix them."
-ms.date: 08/18/2022
+ms.date: 09/28/2022
 ms.topic: reference
 f1_keywords: ["C6308", "REALLOCLEAK", "__WARNING_REALLOCLEAK"]
 helpviewer_keywords: ["C6308"]
@@ -13,13 +13,13 @@ ms.assetid: 1162cd96-9037-4576-9858-0c8361a12559
 
 ## Remarks
 
-Heap reallocation functions don't free the passed buffer if reallocation is unsuccessful, potentially resulting in a memory leak if not handled properly. To correct the issue, assign the result of the reallocation function to a temporary location, and then replace the original pointer after successful reallocation.
+Heap reallocation functions don't free the passed buffer if reallocation is unsuccessful, potentially resulting in a memory leak if not handled properly. To correct the issue, assign the result of the reallocation function to a temporary variable, and then replace the original pointer after successful reallocation.
 
 Code analysis name: REALLOCLEAK
 
 ## Example
 
-The following sample code generates this warning. This issue stems from the assignment of `x` to the return value from realloc. If realloc fails and returns a NULL pointer, then `x` will fail to be freed:
+The following sample code generates warning C6308. This issue stems from the assignment of the return value from `realloc` to `x`. If `realloc` fails and returns a null pointer, then the original memory pointed to by `x` won't be freed:
 
 ```cpp
 #include <malloc.h>
@@ -37,7 +37,7 @@ void f( )
 }
 ```
 
-To resolve the issue, you can create a temporary variable to store the return status of realloc. This change allows you to free the previously allocated memory safely if realloc fails:
+To resolve the issue, you can create a temporary variable to store the return value of `realloc`. This change allows you to free the previously allocated memory safely if `realloc` fails:
 
 ```cpp
 #include <malloc.h>
@@ -61,8 +61,8 @@ void f()
 
 This warning might generate noise if there's a live alias to the buffer-to-be-reallocated at the time of the assignment of the result of the reallocation function.
 
-To avoid these kinds of issues altogether, you can use the mechanisms that are provided by the C++ Standard Template Library (STL). These include [shared_ptr](../standard-library/shared-ptr-class.md), [unique_ptr](../standard-library/unique-ptr-class.md), and [vector](../standard-library/vector.md). For more information, see [Smart Pointers](../cpp/smart-pointers-modern-cpp.md) and [C++ Standard Library](../standard-library/cpp-standard-library-reference.md).
+To avoid these kinds of issues altogether, you can use the mechanisms that are provided by the C++ Standard Template Library (STL). These include [`shared_ptr`](../standard-library/shared-ptr-class.md), [`unique_ptr`](../standard-library/unique-ptr-class.md), and [`vector`](../standard-library/vector.md). For more information, see [Smart pointers](../cpp/smart-pointers-modern-cpp.md) and [C++ Standard Library](../standard-library/cpp-standard-library-reference.md).
 
 ## See also
 
-[C6014](../code-quality/c6014.md)
+[Warning C6014](../code-quality/c6014.md)