Merge pull request #5746 from Rageking8/structure-warning-references-in-range-c6251-c6310

Structure warning references in range [C6251, C6310]

Author: Court72

docs/code-quality/c6255.md

@@ -1,19 +1,18 @@
 ---
+title: "Warning C6255"
 description: "Learn more about: Warning C6255"
-title: Warning C6255
 ms.date: 11/04/2016
 f1_keywords: ["C6255", "UNPROTECTEDUSEOFALLOCA", "__WARNING_UNPROTECTEDUSEOFALLOCA"]
 helpviewer_keywords: ["C6255"]
-ms.assetid: bb6430b2-782a-4410-a8e1-609df06007de
 ---
 # Warning C6255
 
 > _alloca indicates failure by raising a stack overflow exception. Consider using _malloca instead
 
-This warning indicates that a call to `_alloca` has been detected outside of local exception handling.
-
 ## Remarks
 
+This warning indicates that a call to `_alloca` has been detected outside of local exception handling.
+
 `_alloca` should always be called from within the protected range of an exception handler because it can raise a stack overflow exception on failure. If possible, instead of using `_alloca`, consider using `_malloca`, which is a more secure version of `_alloca`.
 
 Code analysis name: `UNPROTECTEDUSEOFALLOCA`

docs/code-quality/c6258.md

@@ -1,19 +1,18 @@
 ---
+title: "Warning C6258"
 description: "Learn more about: Warning C6258"
-title: Warning C6258
 ms.date: 11/04/2016
 f1_keywords: ["C6258", "USINGTERMINATETHREAD", "__WARNING_USINGTERMINATETHREAD"]
 helpviewer_keywords: ["C6258"]
-ms.assetid: 62f3eed7-d9cd-46eb-8c38-0bc4f647941f
 ---
 # Warning C6258
 
 > Using `TerminateThread` does not allow proper thread clean up.
 
-This warning indicates that a call to `TerminateThread` has been detected.
-
 ## Remarks
 
+This warning indicates that a call to `TerminateThread` has been detected.
+
 `TerminateThread` is a dangerous function that should only be used in the most extreme cases. For more information about problems associated with TerminateThread call, see [`TerminateThread` function](/windows/desktop/api/processthreadsapi/nf-processthreadsapi-terminatethread).
 
 Code analysis name: `USINGTERMINATETHREAD`

docs/code-quality/c6259.md

@@ -1,10 +1,9 @@
 ---
+title: "Warning C6259"
 description: "Learn more about: Warning C6259"
-title: Warning C6259
 ms.date: 11/04/2016
 f1_keywords: ["C6259", "DEADCODEINBITORLIMITEDSWITCH", "__WARNING_DEADCODEINBITORLIMITEDSWITCH"]
 helpviewer_keywords: ["C6259"]
-ms.assetid: a370bfd2-6634-402c-84c7-3d83fa0009b7
 ---
 # Warning C6259
 
@@ -18,7 +17,7 @@ Code analysis name: `DEADCODEINBITORLIMITEDSWITCH`
 
 ## Example
 
-The following sample code generates this warning because the 'switch' expression `(rand() & 3)` can't evaluate to case label (`case 4`):
+The following example code generates this warning because the 'switch' expression `(rand() & 3)` can't evaluate to case label (`case 4`):
 
 ```cpp
 #include <stdlib.h>

docs/code-quality/c6260.md

@@ -1,19 +1,18 @@
 ---
+title: "Warning C6260"
 description: "Learn more about: Warning C6260"
-title: Warning C6260
 ms.date: 11/04/2016
 f1_keywords: ["C6260", "USEOFBYTEAREA", "__WARNING_USEOFBYTEAREA"]
 helpviewer_keywords: ["C6260"]
-ms.assetid: 9cbedfcb-32b2-4fe4-99f7-a2d4a7f4422a
 ---
 # Warning C6260
 
 > `sizeof` * `sizeof` is almost always wrong, did you intend to use a character count or a byte count?
 
-This warning indicates that the results of two **`sizeof`** operations have been multiplied together.
-
 ## Remarks
 
+This warning indicates that the results of two **`sizeof`** operations have been multiplied together.
+
 The C/C++ **`sizeof`** operator returns the number of bytes of storage an object uses. It's typically incorrect to multiply it by another **`sizeof`** operation. Usually, you're interested in the number of bytes in an object or the number of elements in an array (for example, the number of wide-characters in an array).
 
 There's some unintuitive behavior associated with **`sizeof`** operator. For example, in C, `sizeof ('\0') == 4`, because a character is of an integral type. In C++, the type of a character literal is **`char`**, so `sizeof ('\0') == 1`. However, in both C and C++, the following relation is true:

docs/code-quality/c6262.md

@@ -1,5 +1,5 @@
 ---
-title: Warning C6262
+title: "Warning C6262"
 description: "Visual Studio C++ Code Analysis warning C6262 description and resolution."
 ms.date: 10/14/2020
 f1_keywords: ["C6262", "EXCESSIVESTACKUSAGE", "__WARNING_EXCESSIVESTACKUSAGE"]

docs/code-quality/c6263.md

@@ -1,10 +1,9 @@
 ---
+title: "Warning C6263"
 description: "Learn more about: Warning C6263"
-title: Warning C6263
 ms.date: 11/04/2016
 f1_keywords: ["C6263", "USINGALLOCAINLOOP", "__WARNING_USINGALLOCAINLOOP"]
 helpviewer_keywords: ["C6263"]
-ms.assetid: bc360ad7-5f59-4480-a642-6c7e6beeb5f6
 ---
 # Warning C6263
 

docs/code-quality/c6268.md

@@ -1,19 +1,18 @@
 ---
+title: "Warning C6268"
 description: "Learn more about: Warning C6268"
-title: Warning C6268
 ms.date: 11/04/2016
 f1_keywords: ["C6268", "MISPARENTHESIZED_CASTS", "__WARNING_MISPARENTHESIZED_CASTS"]
 helpviewer_keywords: ["C6268"]
-ms.assetid: fd81e00a-de2f-498b-b3fe-53ce056042d7
 ---
 # Warning C6268
 
 > Incorrect order of operations: ('*TYPE1*')('*TYPE2*')x + y. Possible missing parentheses in ('*TYPE1*')(('*TYPE2*')x + y)
 
-This warning indicates that a complex cast expression might involve a precedence problem when performing pointer arithmetic. Because casts group more closely than binary operators, the result might not be what the programmer intended. In some cases, this defect causes incorrect behavior or a program crash.
-
 ## Remarks
 
+This warning indicates that a complex cast expression might involve a precedence problem when performing pointer arithmetic. Because casts group more closely than binary operators, the result might not be what the programmer intended. In some cases, this defect causes incorrect behavior or a program crash.
+
 In an expression such as:
 
 ```cpp

docs/code-quality/c6269.md

@@ -1,19 +1,18 @@
 ---
+title: "Warning C6269"
 description: "Learn more about: Warning C6269"
-title: Warning C6269
 ms.date: 11/04/2016
 f1_keywords: ["C6269", "POINTER_DEREF_DISCARDED", "__WARNING_POINTER_DEREF_DISCARDED"]
 helpviewer_keywords: ["C6269"]
-ms.assetid: a01fa7fa-fc6c-4af7-ac8c-585e44e60cca
 ---
 # Warning C6269
 
 > Possible incorrect order of operations: dereference ignored
 
-This warning indicates that the result of a pointer dereference is being ignored, which raises the question of why the pointer is being dereferenced in the first place.
-
 ## Remarks
 
+This warning indicates that the result of a pointer dereference is being ignored, which raises the question of why the pointer is being dereferenced in the first place.
+
 The compiler will correctly optimize away the gratuitous dereference. In some cases, however, this defect may reflect a precedence or logic error.
 
 One common cause for this defect is an expression statement of the form:

docs/code-quality/c6270.md

@@ -1,6 +1,6 @@
 ---
+title: "Warning C6270"
 description: "Learn more about: Warning C6270"
-title: Warning C6270
 ms.date: 3/03/2023
 f1_keywords: ["C6270", "MISSING_FLOAT_ARGUMENT_TO_FORMAT_FUNCTION", "__WARNING_MISSING_FLOAT_ARGUMENT_TO_FORMAT_FUNCTION"]
 helpviewer_keywords: ["C6270"]

docs/code-quality/c6271.md

@@ -1,6 +1,6 @@
 ---
+title: "Warning C6271"
 description: "Learn more about: Warning C6271"
-title: Warning C6271
 ms.date: 3/06/2023
 f1_keywords: ["C6271", "EXTRA_ARGUMENT_TO_FORMAT_FUNCTION", "__WARNING_EXTRA_ARGUMENT_TO_FORMAT_FUNCTION"]
 helpviewer_keywords: ["C6271"]
@@ -17,7 +17,7 @@ Code analysis name: `EXTRA_ARGUMENT_TO_FORMAT_FUNCTION`
 
 ## Example
 
-The following sample code generates this warning:
+The following example code generates this warning:
 
 ```cpp
 #include <stdio.h>
@@ -43,7 +43,7 @@ void f()
 }
 ```
 
-The following sample code calls the safe string manipulation function, `sprintf_s`, to correct this warning:
+The following example code calls the safe string manipulation function, `sprintf_s`, to correct this warning:
 
 ```cpp
 #include <stdio.h>