Add "Remarks" and "Example" headings for error references in range [C1081, C1110]

Author: Rageking8

docs/error-messages/compiler-errors-1/fatal-error-c1081.md

@@ -10,6 +10,8 @@ ms.assetid: e58adf17-cbe1-4955-a5c7-80622bbba249
 
 > 'symbol': file name too long
 
+## Remarks
+
 The length of a file pathname exceeds `_MAX_PATH` (defined by STDLIB.h as 260 characters). Shorten the name of the file.
 
 If you call CL.exe with a short filename, the compiler may need to generate a full pathname. For example, `cl -c myfile.cpp` may cause the compiler to generate:

docs/error-messages/compiler-errors-1/fatal-error-c1082.md

@@ -10,4 +10,6 @@ ms.assetid: 173179f1-1e14-4a91-9451-122f8a53c0b8
 
 > Cannot close filetype file: 'file': message
 
+## Remarks
+
 If the message says "bad file number", the file may have been closing in the foreground while compiling in the background.

docs/error-messages/compiler-errors-1/fatal-error-c1083.md

@@ -9,6 +9,8 @@ helpviewer_keywords: ["C1083"]
 
 > Cannot open *filetype* file: '*file*': *message*
 
+## Remarks
+
 The compiler generates a C1083 error when it can't find a file. There are many possible causes for this error. An incorrect include search path or missing or misnamed header files are the most common causes, but other file types and issues can also cause C1083. Here are some of the common reasons why the compiler generates this error.
 
 ## The specified file name is wrong

docs/error-messages/compiler-errors-1/fatal-error-c1084.md

@@ -10,6 +10,8 @@ ms.assetid: b2f273ef-3a14-4d5f-8ce0-7a11a0388fe6
 
 > Cannot read filetype file: 'file': message
 
+## Remarks
+
 This error is generally the result of a failed internal system API call made by the compiler. The message shown when this error is encountered is often generated by either [_wcserror_s](../../c-runtime-library/reference/strerror-s-strerror-s-wcserror-s-wcserror-s.md) or [FormatMessage](/windows/win32/api/winbase/nf-winbase-formatmessage).
 
 Performing the following steps may help resolve C1084:

docs/error-messages/compiler-errors-1/fatal-error-c1086.md

@@ -10,4 +10,6 @@ ms.assetid: 8e3c32c9-cafe-48bf-87bf-f70a1f0367f0
 
 > Cannot seek filetype file: 'file': message
 
+## Remarks
+
 The compiler cannot complete an I/O operation.

docs/error-messages/compiler-errors-1/fatal-error-c1087.md

@@ -10,4 +10,6 @@ ms.assetid: 2fb4c14e-c6ea-45e4-8ce5-a51d15811a01
 
 > Cannot tell filetype file: 'file': message
 
+## Remarks
+
 The compiler cannot complete an I/O operation.

docs/error-messages/compiler-errors-1/fatal-error-c1088.md

@@ -10,4 +10,6 @@ ms.assetid: e61ebbb4-ab50-4a66-b2f6-3cc4400d8511
 
 > Cannot flush filetype file: 'file': message
 
+## Remarks
+
 The compiler cannot complete an I/O operation.

docs/error-messages/compiler-errors-1/fatal-error-c1089.md

@@ -10,4 +10,6 @@ ms.assetid: c4f1e8e5-62c5-464a-9112-99b0790a0fb7
 
 > Cannot truncate filetype file: 'file': message
 
+## Remarks
+
 The compiler cannot shrink a file to zero length.

docs/error-messages/compiler-errors-1/fatal-error-c1090.md

@@ -9,6 +9,8 @@ helpviewer_keywords: ["C1090"]
 
 > PDB API call failed, error code '*error-number*': *message*
 
+## Remarks
+
 An error occurred in processing a PDB file.
 
 Error C1090 is a catch-all for uncommon compiler PDB file errors that aren't reported separately. We only have generic advice for resolving this issue:

docs/error-messages/compiler-errors-1/fatal-error-c1091.md

@@ -10,6 +10,8 @@ ms.assetid: 812d4201-9154-48b0-b9af-5959c082ca33
 
 > compiler limit: string exceeds 'length' bytes in length
 
+## Remarks
+
 A string constant exceeded the current limit on the length of strings.
 
 You might want to split the static string into two (or more) variables and use [strcpy_s](../../c-runtime-library/reference/strcpy-s-wcscpy-s-mbscpy-s.md) to join the result as part of the declaration or during run time.