Replace term "sample" with "example" for warning references in range [C4701, C4750]

Author: Rageking8

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

@@ -22,7 +22,7 @@ This warning is automatically promoted to an error. If you wish to modify this b
 
 ## Example
 
-The following sample generates C4716:
+The following example generates C4716:
 
 ```cpp
 // C4716.cpp

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

@@ -16,7 +16,7 @@ Every path through a function contains a call to the function. Since there is no
 
 ## Example
 
-The following sample generates C4717:
+The following example generates C4717:
 
 ```cpp
 // C4717.cpp

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

@@ -17,7 +17,7 @@ To resolve, remove the function call that causes the destructor to not return.
 
 ## Example
 
-The following sample generates C4722:
+The following example generates C4722:
 
 ```cpp
 // C4722.cpp

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

@@ -18,7 +18,7 @@ To safely use **`__m64`** types and floating-point types in the same function, e
 
 ## Example
 
-The following sample generates C4730:
+The following example generates C4730:
 
 ```cpp
 // C4730.cpp

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

@@ -16,7 +16,7 @@ A frame pointer register was modified. You must save and restore the register in
 
 ## Example
 
-The following sample generates C4731:
+The following example generates C4731:
 
 ```cpp
 // C4731.cpp

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

@@ -18,7 +18,7 @@ To resolve this warning, either remove the FS:0 definition or turn off this warn
 
 ## Example
 
-The following sample generates C4733:
+The following example generates C4733:
 
 ```cpp
 // C4733.cpp

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

@@ -18,7 +18,7 @@ To resolve this warning, only assign a value to a variable whose size can accomm
 
 ## Example
 
-The following sample generates C4739:
+The following example generates C4739:
 
 ```cpp
 // C4739.cpp

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

@@ -32,7 +32,7 @@ struct X {
 } global;
 ```
 
-The following sample generates C4742.
+The following example generates C4742.
 
 ```c
 // C4742b.c

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

@@ -20,7 +20,7 @@ To resolve this warning, either use the same type definition or use different na
 
 ## Example
 
-The following sample generates C4743. To compile it, place both files in the same folder, then run this command in a developer command prompt:  
+The following example generates C4743. To compile it, place both files in the same folder, then run this command in a developer command prompt:  
 
 ```cmd
 cl /EHsc /W1 /GL /O2 C4743a.cpp C4743b.cpp

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

@@ -16,19 +16,19 @@ An external variable referenced or defined in two files has different types in t
 C4744 is emitted only when files are compiled with /GL.  For more information, see [/GL (Whole Program Optimization)](../../build/reference/gl-whole-program-optimization.md).
 
 > [!NOTE]
-> C4744 usually occurs in C (not C++) files, because in C++ a variable name is decorated with type information.  When the sample (below) is compiles as C++, you'll get linker error LNK2019.
+> C4744 usually occurs in C (not C++) files, because in C++ a variable name is decorated with type information.  When the example (below) is compiles as C++, you'll get linker error LNK2019.
 
 ## Example
 
-This sample contains the first definition.
+This example contains the first definition.
 
 ```c
 // C4744.c
 // compile with: /c /GL
 int global;
 ```
 
-The following sample generates C4744.
+The following example generates C4744.
 
 ```c
 // C4744b.c