Replace term "sample" with "example" for error references in range [C1001, C1020]

Author: Rageking8

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

@@ -32,7 +32,7 @@ To resolve this error, check for the following:
 
 ## Example
 
-The following sample generates C1004:
+The following example generates C1004:
 
 ```cpp
 // C1004.cpp

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

@@ -15,7 +15,7 @@ The parentheses in a preprocessor directive do not match.
 
 ## Example
 
-The following sample generates C1012:
+The following example generates C1012:
 
 ```cpp
 // C1012.cpp

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

@@ -16,7 +16,7 @@ The conditional compilation directive ([#ifdef](../../preprocessor/hash-ifdef-an
 
 ## Example
 
-The following sample generates C1016:
+The following example generates C1016:
 
 ```cpp
 // C1016.cpp

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

@@ -18,7 +18,7 @@ Constants defined using `#define` must have values that evaluate to an integer c
 
 ## Example
 
-The following sample generates C1017:
+The following example generates C1017:
 
 ```cpp
 // C1017.cpp
@@ -39,7 +39,7 @@ Possible resolution:
 
 Because `CONSTANT_NAME` evaluates to a string and not an integer, the `#if` directive generates fatal error C1017.
 
-In other cases, the preprocessor evaluates an undefined constant as zero. This can cause unintended results, as shown in the following sample. `YES` is undefined, so it evaluates to zero. The expression `#if` `CONSTANT_NAME` evaluates to false and the code to be used on `YES` is removed by the preprocessor. `NO` is also undefined (zero), so `#elif` `CONSTANT_NAME==NO` evaluates to true (`0 == 0`), causing the preprocessor to leave the code in the `#elif` portion of the statement — exactly the opposite of the intended behavior.
+In other cases, the preprocessor evaluates an undefined constant as zero. This can cause unintended results, as shown in the following example. `YES` is undefined, so it evaluates to zero. The expression `#if` `CONSTANT_NAME` evaluates to false and the code to be used on `YES` is removed by the preprocessor. `NO` is also undefined (zero), so `#elif` `CONSTANT_NAME==NO` evaluates to true (`0 == 0`), causing the preprocessor to leave the code in the `#elif` portion of the statement — exactly the opposite of the intended behavior.
 
 ```cpp
 // C1017c.cpp

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

@@ -16,7 +16,7 @@ The `#elif` directive appears outside an `#if`, `#ifdef`, or `#ifndef` construct
 
 ## Example
 
-The following sample generates C1018:
+The following example generates C1018:
 
 ```cpp
 // C1018.cpp

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

@@ -16,7 +16,7 @@ The `#else` directive appears outside an `#if`, `#ifdef`, or `#ifndef` construct
 
 ## Example
 
-The following sample generates C1019:
+The following example generates C1019:
 
 ```cpp
 // C1019.cpp

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

@@ -18,7 +18,7 @@ This error can occur if you have conditional preprocessor directives before you
 
 ## Example
 
-The following sample generates C1020:
+The following example generates C1020:
 
 ```cpp
 // C1020.cpp