Structure error references in range [R6002, R6035]

docs/error-messages/tool-errors/c-runtime-error-r6002.md

@@ -1,14 +1,15 @@
 ---
-description: "Learn more about: C Runtime Error R6002"
 title: "C Runtime Error R6002"
-ms.date: "11/04/2016"
+description: "Learn more about: C Runtime Error R6002"
+ms.date: 11/04/2016
 f1_keywords: ["R6002"]
 helpviewer_keywords: ["R6002"]
-ms.assetid: 8fbbe65a-9c43-459e-8342-e1f6d1cef7d0
 ---
 # C Runtime Error R6002
 
-floating-point support not loaded
+> floating-point support not loaded
+
+## Remarks
 
 The necessary floating-point library was not linked.
 

docs/error-messages/tool-errors/c-runtime-error-r6008.md

@@ -1,14 +1,15 @@
 ---
-description: "Learn more about: C Runtime Error R6008"
 title: "C Runtime Error R6008"
-ms.date: "11/04/2016"
+description: "Learn more about: C Runtime Error R6008"
+ms.date: 11/04/2016
 f1_keywords: ["R6008"]
 helpviewer_keywords: ["R6008"]
-ms.assetid: f0f304fc-709a-4843-bc7e-bad1ae0d1649
 ---
 # C Runtime Error R6008
 
-not enough space for arguments
+> not enough space for arguments
+
+## Remarks
 
 > [!NOTE]
 > If you encounter this error message while running an app, the app was shut down because it has an internal memory problem. There are several possible reasons for this error, but often it's caused by an extremely low memory condition, too much memory taken by environment variables, or a bug in the program.

docs/error-messages/tool-errors/c-runtime-error-r6009.md

@@ -1,14 +1,15 @@
 ---
-description: "Learn more about: C Runtime Error R6009"
 title: "C Runtime Error R6009"
-ms.date: "11/04/2016"
+description: "Learn more about: C Runtime Error R6009"
+ms.date: 11/04/2016
 f1_keywords: ["R6009"]
 helpviewer_keywords: ["R6009"]
-ms.assetid: edfb1f8b-3807-48f4-a994-318923b747ae
 ---
 # C Runtime Error R6009
 
-not enough space for environment
+> not enough space for environment
+
+## Remarks
 
 > [!NOTE]
 > If you encounter this error message while running an app, the app was shut down because it has an internal memory problem. There are several possible reasons for this error, but often it's caused by an extremely low memory condition, too much memory taken by environment variables, or a bug in the program.

docs/error-messages/tool-errors/c-runtime-error-r6016.md

@@ -1,14 +1,15 @@
 ---
-description: "Learn more about: C Runtime Error R6016"
 title: "C Runtime Error R6016"
-ms.date: "11/04/2016"
+description: "Learn more about: C Runtime Error R6016"
+ms.date: 11/04/2016
 f1_keywords: ["R6016"]
 helpviewer_keywords: ["R6016"]
-ms.assetid: 7bd3f274-d9c4-4bc4-8252-80bf168c4c3a
 ---
 # C Runtime Error R6016
 
-not enough space for thread data
+> not enough space for thread data
+
+## Remarks
 
 > [!NOTE]
 > If you encounter this error message while running an app, the app was shut down because it has an internal memory problem. There are many possible reasons for this error, but often it's caused by an extremely low memory condition, a bug in the app, or by a bug in an add-in or extension used by the app.

docs/error-messages/tool-errors/c-runtime-error-r6017.md

@@ -1,14 +1,15 @@
 ---
-description: "Learn more about: C Runtime Error R6017"
 title: "C Runtime Error R6017"
-ms.date: "11/04/2016"
+description: "Learn more about: C Runtime Error R6017"
+ms.date: 11/04/2016
 f1_keywords: ["R6017"]
 helpviewer_keywords: ["R6017"]
-ms.assetid: df3ec5f5-6771-4648-ba06-0e26c6a1cc6a
 ---
 # C Runtime Error R6017
 
-unexpected multithread lock error
+> unexpected multithread lock error
+
+## Remarks
 
 > [!NOTE]
 > If you encounter this error message while running an app, the app was shut down because it has an internal problem. There are several possible reasons for this error, but often it's caused by a defect in the app's code.

docs/error-messages/tool-errors/c-runtime-error-r6018.md

@@ -1,14 +1,15 @@
 ---
-description: "Learn more about: C Runtime Error R6018"
 title: "C Runtime Error R6018"
-ms.date: "11/04/2016"
+description: "Learn more about: C Runtime Error R6018"
+ms.date: 11/04/2016
 f1_keywords: ["R6018"]
 helpviewer_keywords: ["R6018"]
-ms.assetid: f6dd40d1-a119-4d8b-b39e-97350ea23349
 ---
 # C Runtime Error R6018
 
-unexpected heap error
+> unexpected heap error
+
+## Remarks
 
 > [!NOTE]
 > If you encounter this error message while running an app, the app was shut down because it has an internal problem. There are several possible reasons for this error, but often it's caused by a defect in the app's code.

docs/error-messages/tool-errors/c-runtime-error-r6019.md

@@ -1,14 +1,15 @@
 ---
-description: "Learn more about: C Runtime Error R6019"
 title: "C Runtime Error R6019"
-ms.date: "11/04/2016"
+description: "Learn more about: C Runtime Error R6019"
+ms.date: 11/04/2016
 f1_keywords: ["R6019"]
 helpviewer_keywords: ["R6019"]
-ms.assetid: 8129923e-7db2-40ee-9602-def9365f8d28
 ---
 # C Runtime Error R6019
 
-unable to open console device
+> unable to open console device
+
+## Remarks
 
 > [!NOTE]
 > If you encounter this error message while running an app, the app was shut down because it attempted to access the console, but it didn't have sufficient permission. There are several possible reasons for this error, but it's usually because the program must be run as an administrator, or there is a bug in the program.

docs/error-messages/tool-errors/c-runtime-error-r6024.md

@@ -1,14 +1,15 @@
 ---
-description: "Learn more about: C Runtime Error R6024"
 title: "C Runtime Error R6024"
-ms.date: "11/04/2016"
+description: "Learn more about: C Runtime Error R6024"
+ms.date: 11/04/2016
 f1_keywords: ["R6024"]
 helpviewer_keywords: ["R6024"]
-ms.assetid: 0fb11c0f-9b81-4cab-81bd-4785742946a5
 ---
 # C Runtime Error R6024
 
-not enough space for _onexit/atexit table
+> not enough space for _onexit/atexit table
+
+## Remarks
 
 > [!NOTE]
 > If you encounter this error message while running an app, the app was shut down because it has an internal memory problem. This error is usually caused by an extremely low memory condition, or rarely, by a bug in the program or by corruption of the Visual C++ libraries that it uses.

docs/error-messages/tool-errors/c-runtime-error-r6025.md

@@ -1,14 +1,15 @@
 ---
-description: "Learn more about: C Runtime Error R6025"
 title: "C Runtime Error R6025"
-ms.date: "11/04/2016"
+description: "Learn more about: C Runtime Error R6025"
+ms.date: 11/04/2016
 f1_keywords: ["R6025"]
 helpviewer_keywords: ["R6025"]
-ms.assetid: afa06d98-9c36-445b-b3e7-b6409bc8e779
 ---
 # C Runtime Error R6025
 
-pure virtual function call
+> pure virtual function call
+
+## Remarks
 
 > [!NOTE]
 > If you encounter this error message while running an app, the app was shut down because it has an internal problem. The most common reason for this error is a bug in the app, or a corrupted installation.

docs/error-messages/tool-errors/c-runtime-error-r6026.md

@@ -1,14 +1,15 @@
 ---
-description: "Learn more about: C Runtime Error R6026"
 title: "C Runtime Error R6026"
-ms.date: "11/04/2016"
+description: "Learn more about: C Runtime Error R6026"
+ms.date: 11/04/2016
 f1_keywords: ["R6026"]
 helpviewer_keywords: ["R6026"]
-ms.assetid: 7ea751f8-fc20-46ab-99ef-84c95ca0b6b4
 ---
 # C Runtime Error R6026
 
-not enough space for stdio initialization
+> not enough space for stdio initialization
+
+## Remarks
 
 > [!NOTE]
 > If you encounter this error message while running an app, the app was shut down because it has an internal memory problem. There are several possible reasons for this error, but usually it's caused by an extremely low memory condition. It can also be caused by a bug in the app, by corruption of the Visual C++ libraries that it uses, or by a driver.

docs/error-messages/tool-errors/c-runtime-error-r6027.md

@@ -1,14 +1,15 @@
 ---
-description: "Learn more about: C Runtime Error R6027"
 title: "C Runtime Error R6027"
-ms.date: "11/04/2016"
+description: "Learn more about: C Runtime Error R6027"
+ms.date: 11/04/2016
 f1_keywords: ["R6027"]
 helpviewer_keywords: ["R6027"]
-ms.assetid: c06a62b3-08d9-4bf5-bcad-8340ec552f69
 ---
 # C Runtime Error R6027
 
-not enough space for lowio initialization
+> not enough space for lowio initialization
+
+## Remarks
 
 > [!NOTE]
 > If you encounter this error message while running an app, the app was shut down because it has an internal memory problem. There are several possible reasons for this error, but usually it's caused by an extremely low memory condition. It can also be caused by a bug in the app, by corruption of the Visual C++ libraries that it uses, or by a driver.

docs/error-messages/tool-errors/c-runtime-error-r6028.md

@@ -1,14 +1,15 @@
 ---
-description: "Learn more about: C Runtime Error R6028"
 title: "C Runtime Error R6028"
-ms.date: "11/04/2016"
+description: "Learn more about: C Runtime Error R6028"
+ms.date: 11/04/2016
 f1_keywords: ["R6028"]
 helpviewer_keywords: ["R6028"]
-ms.assetid: 81e99079-4388-4244-a4f7-4641c508871c
 ---
 # C Runtime Error R6028
 
-unable to initialize heap
+> unable to initialize heap
+
+## Remarks
 
 > [!NOTE]
 > If you encounter this error message while running an app, the app was shut down because it has an internal memory problem. There are many possible reasons for this error, but often it's caused by an extremely low memory condition, a bug in the program, or by defective hardware drivers.

docs/error-messages/tool-errors/c-runtime-error-r6030.md

@@ -1,14 +1,15 @@
 ---
-description: "Learn more about: C Runtime Error R6030"
 title: "C Runtime Error R6030"
-ms.date: "11/04/2016"
+description: "Learn more about: C Runtime Error R6030"
+ms.date: 11/04/2016
 f1_keywords: ["R6030"]
 helpviewer_keywords: ["R6030"]
-ms.assetid: 0238a6c3-a033-4046-8adc-f8f99d961153
 ---
 # C Runtime Error R6030
 
-CRT not initialized
+> CRT not initialized
+
+## Remarks
 
 > [!NOTE]
 > If you encounter this error message while running an app, the app was shut down because it has an internal problem. This problem is most often caused by certain security software programs, or rarely, by a bug in the program.

docs/error-messages/tool-errors/c-runtime-error-r6031.md

@@ -1,14 +1,15 @@
 ---
-description: "Learn more about: C Runtime Error R6031"
 title: "C Runtime Error R6031"
-ms.date: "11/04/2016"
+description: "Learn more about: C Runtime Error R6031"
+ms.date: 11/04/2016
 f1_keywords: ["R6031"]
 helpviewer_keywords: ["R6031"]
-ms.assetid: 805d4cd1-cb2f-43fe-87e6-e7bd5b7329c5
 ---
 # C Runtime Error R6031
 
-Attempt to initialize the CRT more than once. This indicates a bug in your application.
+> Attempt to initialize the CRT more than once. This indicates a bug in your application.
+
+## Remarks
 
 > [!NOTE]
 > If you encounter this error message while running an app, the app was shut down because it has an internal problem. This may be caused bug in the app, or by a bug in an add-on or extension that the app uses.

docs/error-messages/tool-errors/c-runtime-error-r6032.md

@@ -1,14 +1,15 @@
 ---
-description: "Learn more about: C Runtime Error R6032"
 title: "C Runtime Error R6032"
-ms.date: "11/04/2016"
+description: "Learn more about: C Runtime Error R6032"
+ms.date: 11/04/2016
 f1_keywords: ["R6032"]
 helpviewer_keywords: ["R6032"]
-ms.assetid: 52092a63-cc51-444a-bfc3-fad965a3558e
 ---
 # C Runtime Error R6032
 
-Not enough space for locale information
+> Not enough space for locale information
+
+## Remarks
 
 > [!NOTE]
 > If you encounter this error message while running an app, the app was shut down because it has an internal memory problem. There are several possible reasons for this error, but often it's caused by an extremely low memory condition, or by a bug in the program.

docs/error-messages/tool-errors/c-runtime-error-r6033.md

@@ -1,14 +1,15 @@
 ---
-description: "Learn more about: C Runtime Error R6033"
 title: "C Runtime Error R6033"
-ms.date: "11/04/2016"
+description: "Learn more about: C Runtime Error R6033"
+ms.date: 11/04/2016
 f1_keywords: ["R6033"]
 helpviewer_keywords: ["R6033"]
-ms.assetid: f9cffdc9-81bd-4a64-a698-02762cbd82c9
 ---
 # C Runtime Error R6033
 
-Attempt to use MSIL code from this assembly during native code initialization. This indicates a bug in your application. It is most likely the result of calling an MSIL-compiled (/clr) function from a native constructor or from DllMain.
+> Attempt to use MSIL code from this assembly during native code initialization. This indicates a bug in your application. It is most likely the result of calling an MSIL-compiled (/clr) function from a native constructor or from DllMain.
+
+## Remarks
 
 > [!NOTE]
 > If you encounter this error message while running an app, the app was shut down because it has an internal problem. This error can be caused by a bug in the app, or by a bug in an add-in or extension that it uses.

docs/error-messages/tool-errors/c-runtime-error-r6035.md

@@ -1,21 +1,24 @@
 ---
-description: "Learn more about: C Runtime Error R6035"
 title: "C Runtime Error R6035"
-ms.date: "11/04/2016"
+description: "Learn more about: C Runtime Error R6035"
+ms.date: 11/04/2016
 f1_keywords: ["R6035"]
 helpviewer_keywords: ["R6035"]
-ms.assetid: f8fb50b8-18bf-4258-b96a-b0a9de468d16
 ---
 # C Runtime Error R6035
 
-Microsoft Visual C++ Runtime Library, Error R6035 - A module in this application is initializing the module's global security cookie while a function relying on that security cookie is active.  Call __security_init_cookie earlier.
+> A module in this application is initializing the module's global security cookie while a function relying on that security cookie is active.  Call __security_init_cookie earlier.
+
+## Remarks
 
 [__security_init_cookie](../../c-runtime-library/reference/security-init-cookie.md) must be called before the first use of the global security cookie.
 
 The global security cookie is used for buffer overrun protection in code compiled with [/GS (Buffer Security Check)](../../build/reference/gs-buffer-security-check.md) and in code that uses structured exception handling. Essentially, on entry to an overrun-protected function, the cookie is put on the stack, and on exit, the value on the stack is compared against the global cookie. Any difference between them indicates that a buffer overrun has occurred and results in immediate termination of the program.
 
 Error R6035 indicates that a call to `__security_init_cookie` was made after a protected function was entered. If execution were to continue, a spurious buffer overrun would be detected because the cookie on the stack would no longer match the global cookie.
 
+## Example
+
 Consider the following DLL example. The DLL entry point is set to DllEntryPoint through the linker [/ENTRY (Entry-Point Symbol)](../../build/reference/entry-entry-point-symbol.md) option. This bypasses the CRT's initialization which would ordinarily initialize the global security cookie, so the DLL itself must call `__security_init_cookie`.
 
 ```