acrolinx

Author: TylerMSFT

docs/c-runtime-library/reference/memcpy-wmemcpy.md

@@ -55,7 +55,7 @@ The value of *`dest`*.
 >
 > Because **`memcpy`** usage by the VC++ compiler and libraries has been so carefully scrutinized, these calls are permitted within code that otherwise conforms with the SDL.  **`memcpy`** calls introduced in application source code only conform with the SDL when that use has been reviewed by security experts.
 
-The **`memcpy`** and **`wmemcpy`** functions are only deprecated if the constant `_CRT_SECURE_DEPRECATE_MEMORY` is defined before the include statement, as in the example below:
+The **`memcpy`** and **`wmemcpy`** functions are only deprecated if the constant `_CRT_SECURE_DEPRECATE_MEMORY` is defined before the `#include` statement, as in the following examples:
 
 ```C
 #define _CRT_SECURE_DEPRECATE_MEMORY

docs/c-runtime-library/reference/memmove-wmemmove.md

@@ -49,7 +49,7 @@ Copies *`count`* bytes (**`memmove`**) or characters (**`wmemmove`**) from *`src
 
 **Security Note** Make sure that the destination buffer is large enough to accommodate the number of moved characters. For more information, see [Avoiding buffer overruns](/windows/win32/SecBP/avoiding-buffer-overruns).
 
-The **`memmove`** and **`wmemmove`** functions will only be deprecated if the constant `_CRT_SECURE_DEPRECATE_MEMORY` is defined before the inclusion statement in order for the functions to be deprecated, such as in the example below:
+The **`memmove`** and **`wmemmove`** functions are only deprecated if the constant `_CRT_SECURE_DEPRECATE_MEMORY` is defined before the `#include` statement, as shown in the following example:
 
 ```C
 #define _CRT_SECURE_DEPRECATE_MEMORY