Merge pull request #5734 from Rageking8/structure-warning-references-in-range-c4831-c4940

Structure warning references in range [C4831, C4940]

Author: v-dirichards

docs/error-messages/compiler-warnings/c4834.md

@@ -30,7 +30,7 @@ To turn off the warning for an entire project in the Visual Studio IDE:
 
 ## Example
 
-This sample generates C4834, and shows four ways to fix it:
+This example generates C4834, and shows four ways to fix it:
 
 ```cpp
 // C4834.cpp

docs/error-messages/compiler-warnings/c4841.md

@@ -1,6 +1,6 @@
 ---
-description: "Learn more about: Compiler Warning (level 4) C4841"
 title: "Compiler Warning (level 4) C4841"
+description: "Learn more about: Compiler Warning (level 4) C4841"
 ms.date: 05/03/2021
 f1_keywords: ["C4841"]
 helpviewer_keywords: ["C4841"]

docs/error-messages/compiler-warnings/c4843.md

@@ -1,6 +1,6 @@
 ---
-description: "Learn more about: Compiler Warning (level 4) C4843"
 title: "Compiler Warning (level 4) C4843"
+description: "Learn more about: Compiler Warning (level 4) C4843"
 ms.date: 05/03/2021
 f1_keywords: ["C4843"]
 helpviewer_keywords: ["C4843"]
@@ -17,7 +17,7 @@ This warning is new in Visual Studio 2017 version 15.5. For information on how t
 
 ## Example
 
-This sample shows several **`catch`** statements that cause C4843:
+This example shows several **`catch`** statements that cause C4843:
 
 ```cpp
 // C4843_warning.cpp

docs/error-messages/compiler-warnings/c4866.md

@@ -1,7 +1,7 @@
 ---
-description: "Learn more about: Compiler Warning (level 4) C4866"
 title: "Compiler Warning (Level 4) C4866"
-ms.date: "09/30/2018"
+description: "Learn more about: Compiler Warning (level 4) C4866"
+ms.date: 09/30/2018
 f1_keywords: ["C4866"]
 helpviewer_keywords: ["C4866"]
 ---
@@ -25,11 +25,11 @@ This warning was introduced in Visual Studio 2017 version 15.9 as a result of co
 
 To resolve this warning, first consider whether left-to-right evaluation of the operator elements is necessary, such as when evaluation of the elements might produce order-dependent side-effects. In many cases, the order in which elements are evaluated does not have an observable effect.
 
-If the order of evaluation must be left-to-right, consider whether you can pass the elements by **`const`** reference instead. This change eliminates the warning in the following code sample.
+If the order of evaluation must be left-to-right, consider whether you can pass the elements by **`const`** reference instead. This change eliminates the warning in the following code example.
 
 ## Example
 
-This sample generates C4866, and shows a way to fix it:
+This example generates C4866, and shows a way to fix it:
 
 ```cpp
 // C4866.cpp

docs/error-messages/compiler-warnings/compiler-warning-c4867.md

@@ -1,14 +1,15 @@
 ---
-description: "Learn more about: Compiler Warning C4867"
 title: "Compiler Warning C4867"
-ms.date: "11/04/2016"
+description: "Learn more about: Compiler Warning C4867"
+ms.date: 11/04/2016
 f1_keywords: ["C4867"]
 helpviewer_keywords: ["C4867"]
-ms.assetid: 8a257d70-c3a7-462d-b285-e57c952a8bf7
 ---
 # Compiler Warning C4867
 
-'function': function call missing argument list; use 'call' to create a pointer to member
+> 'function': function call missing argument list; use 'call' to create a pointer to member
+
+## Remarks
 
 A pointer to member function was initialized incorrectly.
 
@@ -18,7 +19,7 @@ This warning is always issued as an error. Use the [warning](../../preprocessor/
 
 ## Example
 
-The following sample generates C4867.
+The following example generates C4867.
 
 ```cpp
 // C4867.cpp

docs/error-messages/compiler-warnings/compiler-warning-c4868.md

@@ -1,15 +1,16 @@
 ---
-description: "Learn more about: Compiler Warning (level 4) C4868"
 title: "Compiler Warning C4868"
-ms.date: "10/26/2017"
+description: "Learn more about: Compiler Warning (level 4) C4868"
+ms.date: 10/26/2017
 f1_keywords: ["C4868"]
 helpviewer_keywords: ["C4868"]
-ms.assetid: fc6aa7e5-34dd-4ec2-88bd-16e430361dc7
 ---
 # Compiler Warning (level 4) C4868
 
 > '_file_(*line_number*)' compiler may not enforce left-to-right evaluation order in braced initializer list
 
+## Remarks
+
 The elements of a braced initializer list are to be evaluated in left-to-right order. There are two cases in which the compiler is unable to guarantee this order: the first is when some of the elements are objects passed by value; the second is  when compiling with `/clr` and some of the elements are fields of objects or are array elements. When the compiler can't guarantee left-to-right evaluation it emits warning C4868.
 
 This warning can be generated as a result of compiler conformance work that was done for Visual Studio 2015 Update 2. Code that compiled prior to Visual Studio 2015 Update 2 can now generate C4868.
@@ -18,11 +19,11 @@ This warning is off by default. Use `/Wall` to activate this warning.
 
 To resolve this warning, first consider whether left-to-right evaluation of the initializer list elements is necessary, such as when evaluation of the elements might produce order-dependent side-effects. In many cases, the order in which elements are evaluated does not have an observable effect.
 
-If the order of evaluation must be left-to-right, consider if it's possible to pass the elements by **`const`** reference instead. A change such as this eliminates the warning in the following code sample.
+If the order of evaluation must be left-to-right, consider if it's possible to pass the elements by **`const`** reference instead. A change such as this eliminates the warning in the following code example.
 
 ## Example
 
-This sample generates C4868, and shows a way to fix it:
+This example generates C4868, and shows a way to fix it:
 
 ```cpp
 // C4868.cpp

docs/error-messages/compiler-warnings/compiler-warning-c4936.md

@@ -1,10 +1,9 @@
 ---
-description: "Learn more about: Compiler Warning C4936"
 title: "Compiler Warning C4936"
-ms.date: "11/04/2016"
+description: "Learn more about: Compiler Warning C4936"
+ms.date: 11/04/2016
 f1_keywords: ["C4936"]
 helpviewer_keywords: ["C4936"]
-ms.assetid: 6676de35-bf1b-4d0b-a70f-b5734130336c
 ---
 # Compiler Warning C4936
 
@@ -22,7 +21,7 @@ C4936 is always issued as an error.  You can disable C4936 with the [warning](..
 
 ## Example
 
-The following sample generates C4936:
+The following example generates C4936:
 
 ```cpp
 // C4936.cpp

docs/error-messages/compiler-warnings/compiler-warning-level-1-c4835.md

@@ -1,20 +1,21 @@
 ---
-description: "Learn more about: Compiler Warning (level 1) C4835"
 title: "Compiler Warning (level 1) C4835"
-ms.date: "11/04/2016"
+description: "Learn more about: Compiler Warning (level 1) C4835"
+ms.date: 11/04/2016
 f1_keywords: ["C4835"]
 helpviewer_keywords: ["C4835"]
-ms.assetid: d2e44c62-7b0e-4a45-943d-97903e27ed9d
 ---
 # Compiler Warning (level 1) C4835
 
-'variable' : the initializer for exported data will not be run until managed code is first executed in the host assembly
+> 'variable' : the initializer for exported data will not be run until managed code is first executed in the host assembly
+
+## Remarks
 
 When accessing data between managed components, it is recommended that you not use native C++ import and export mechanisms. Instead, declare your data members inside a managed type and reference the metadata with `#using` in the client. For more information, see [#using Directive](../../preprocessor/hash-using-directive-cpp.md).
 
 ## Examples
 
-The following sample generates C4835.
+The following example generates C4835.
 
 ```cpp
 // C4835.cpp
@@ -26,7 +27,7 @@ __declspec(dllexport) int m = f();   // C4835
 __declspec(dllexport) int *p = &n;   // C4835
 ```
 
-The following sample consumes the component built in the previous sample, showing that the value of the variables is not as expected.
+The following example consumes the component built in the previous example, showing that the value of the variables is not as expected.
 
 ```cpp
 // C4835_b.cpp

docs/error-messages/compiler-warnings/compiler-warning-level-1-c4838.md

@@ -1,22 +1,25 @@
 ---
-description: "Learn more about: Compiler Warning (level 1) C4838"
 title: "Compiler Warning (level 1) C4838"
-ms.date: "11/04/2016"
+description: "Learn more about: Compiler Warning (level 1) C4838"
+ms.date: 11/04/2016
 f1_keywords: ["C4838"]
 helpviewer_keywords: ["C4838"]
-ms.assetid: fea07924-5feb-4ed4-99b5-1a8c41d28db6
 ---
 # Compiler Warning (level 1) C4838
 
-conversion from 'type_1' to 'type_2' requires a narrowing conversion
+> conversion from 'type_1' to 'type_2' requires a narrowing conversion
+
+## Remarks
 
 An implicit narrowing conversion was found when using aggregate or list initialization.
 
 The C language allows implicit narrowing conversions in assignments and initialization, and C++ follows suit, even though unexpected narrowing is a cause of many code errors. To make code safer, the C++ standard requires a diagnostic message when a narrowing conversion occurs in an initialization list. In Visual C++, the diagnostic is [Compiler Error C2397](../../error-messages/compiler-errors-1/compiler-error-c2397.md) when using the uniform initialization syntax supported beginning in Visual Studio 2015. The compiler generates  warning C4838 when using the list or aggregate initialization syntax supported by Visual Studio 2013.
 
 A narrowing conversion can be okay when you know the possible range of converted values can fit in the target. In this case, you know more than the compiler does. If you make a narrowing conversion intentionally, make your intentions explicit by using a static cast. Otherwise, this warning message almost always indicates that you have a bug in your code. You can fix it by making sure the objects you initialize have types that are large enough to handle the inputs.
 
-The following sample generates C4838 and shows one way to fix it:
+## Example
+
+The following example generates C4838 and shows one way to fix it:
 
 ```cpp
 // C4838.cpp -- C++ narrowing conversion diagnostics

docs/error-messages/compiler-warnings/compiler-warning-level-1-c4900.md

@@ -1,13 +1,14 @@
 ---
-description: "Learn more about: Compiler Warning (level 1) C4900"
 title: "Compiler Warning (level 1) C4900"
-ms.date: "11/04/2016"
+description: "Learn more about: Compiler Warning (level 1) C4900"
+ms.date: 11/04/2016
 f1_keywords: ["C4900"]
 helpviewer_keywords: ["C4900"]
-ms.assetid: 826997ec-0803-4794-ad35-bb463f679658
 ---
 # Compiler Warning (level 1) C4900
 
-intermediate language mismatch between 'tool1' version 'version1' and 'tool2' version 'version2'
+> intermediate language mismatch between 'tool1' version 'version1' and 'tool2' version 'version2'
+
+## Remarks
 
 The intermediate language used in *tool1* and *tool2* did not match. Check that the most current version of each tool has been installed.