Merge pull request #4615 from corob-msft/bulk-fix-crt-acrolinx-16

Bulk fix CRT acrolinx issues 16 of N

Author: colin-home

docs/c-runtime-library/reference/fmax-fmaxf-fmaxl.md

@@ -55,7 +55,7 @@ The second value to compare.
 
 ## Return value
 
-If successful, returns the larger of *`x`* or *`y`*. The value returned is exact, and does not depend on any form of rounding.
+If successful, returns the larger of *`x`* or *`y`*. The value returned is exact, and doesn't depend on any form of rounding.
 
 Otherwise, may return one of the following values:
 
@@ -65,7 +65,7 @@ Otherwise, may return one of the following values:
 |*`y`* = NaN|*`x`*|
 |*`x`* and *`y`* = NaN|NaN|
 
-This function does not use the errors specified in  [`_matherr`](matherr.md).
+This function doesn't use the errors specified in  [`_matherr`](matherr.md).
 
 ## Remarks
 

docs/c-runtime-library/reference/fmin-fminf-fminl.md

@@ -63,7 +63,7 @@ If successful, returns the smaller of *`x`* or *`y`*.
 |*`y`* is NaN|*`x`*|
 |*`x`* and *`y`* are NaN|NaN|
 
-The function does not cause [`_matherr`](matherr.md) to be invoked, cause any floating-point exceptions, or change the value of `errno`.
+The function doesn't cause [`_matherr`](matherr.md) to be invoked, cause any floating-point exceptions, or change the value of `errno`.
 
 ## Remarks
 

docs/c-runtime-library/reference/fopen-s-wfopen-s.md

@@ -61,7 +61,7 @@ The **`fopen_s`** function opens the file that's specified by *`filename`*. **`_
 
 These functions validate their parameters. If *`pFile`*, *`filename`*, or *`mode`* is a null pointer, these functions generate an invalid parameter exception, as described in [Parameter validation](../parameter-validation.md).
 
-Always check the return value to see if the function succeeded before you do any further operations on the file. If an error occurs, the error code is returned and the global variable `errno` is set. For more information, see [`errno`, `_doserrno`, `_sys_errlist`, and `_sys_nerr`](../errno-doserrno-sys-errlist-and-sys-nerr.md).
+Always check the return value to see if the function succeeded before you do any further operations on the file. If an error occurs, the error code is returned, and the global variable `errno` is set. For more information, see [`errno`, `_doserrno`, `_sys_errlist`, and `_sys_nerr`](../errno-doserrno-sys-errlist-and-sys-nerr.md).
 
 By default, this function's global state is scoped to the application. To change it, see [Global state in the CRT](../global-state.md).
 

docs/c-runtime-library/reference/fopen-wfopen.md

@@ -47,7 +47,7 @@ The **`fopen`** function opens the file that is specified by *`filename`*. By de
 
 **`fopen`** accepts paths that are valid on the file system at the point of execution; **`fopen`** accepts UNC paths and paths that involve mapped network drives as long as the system that executes the code has access to the share or mapped drive at the time of execution. When you construct paths for **`fopen`**, make sure that drives, paths, or network shares will be available in the execution environment. You can use either forward slashes (`/`) or backslashes (`\`) as the directory separators in a path.
 
-Always check the return value to see whether the pointer is NULL before you perform any other operations on the file. If an error occurs, the global variable `errno` is set and may be used to obtain specific error information. For more information, see [`errno`, `_doserrno`, `_sys_errlist`, and `_sys_nerr`](../errno-doserrno-sys-errlist-and-sys-nerr.md).
+Always check the return value to see whether the pointer is NULL before you perform any other operations on the file. If an error occurs, the global variable `errno` is set, and may be used to obtain specific error information. For more information, see [`errno`, `_doserrno`, `_sys_errlist`, and `_sys_nerr`](../errno-doserrno-sys-errlist-and-sys-nerr.md).
 
 By default, this function's global state is scoped to the application. To change it, see [Global state in the CRT](../global-state.md).
 

docs/c-runtime-library/reference/fpclass-fpclassf.md

@@ -49,7 +49,7 @@ The **`_fpclass`** and **`_fpclassf`** functions return an integer value that in
 
 ## Remarks
 
-The **`_fpclass`** and **`_fpclassf`** functions are Microsoft-specific. They are similar to [`fpclassify`](fpclassify.md), but return more detailed information about the argument. The **`_fpclassf`** function is only available when compiled for the x64 platform.
+The **`_fpclass`** and **`_fpclassf`** functions are Microsoft-specific. They're similar to [`fpclassify`](fpclassify.md), but return more detailed information about the argument. The **`_fpclassf`** function is only available when compiled for the x64 platform.
 
 By default, this function's global state is scoped to the application. To change this behavior, see [Global state in the CRT](../global-state.md).
 

docs/c-runtime-library/reference/fpieee-flt.md

@@ -49,10 +49,10 @@ The `_FPIEEE_RECORD` structure, defined in Fpieee.h, contains information pertai
 |----------------------------|-----------------|
 |`RoundingMode`<br/>`Precision`|These **`unsigned int`** fields contain information about the floating-point environment at the time the exception occurred.|
 |`Operation`|This **`unsigned int`** field indicates the type of operation that caused the trap. If the type is a comparison (`_FpCodeCompare`), you can supply one of the special `_FPIEEE_COMPARE_RESULT` values (as defined in Fpieee.h) in the **Result.Value** field. The conversion type (`_FpCodeConvert`) indicates that the trap occurred during a floating-point conversion operation. You can look at the `Operand1` and `Result` types to determine the type of conversion being attempted.|
-|`Operand1`<br/>`Operand2`<br/>`Result`|These `_FPIEEE_VALUE` structures indicate the types and values of the proposed result and operands. Each structure contains these fields:<br /><br /> `OperandValid` - Flag indicating whether the responding value is valid.<br />`Format` - Data type of the corresponding value. The format type might be returned even if the corresponding value is not valid.<br />`Value` - Result or operand data value.|
-|`Cause`<br/>`Enable`<br/>`Status`|`_FPIEEE_EXCEPTION_FLAGS` contains one bit field per type of floating point exception. There is a correspondence between these fields and the arguments used to mask the exceptions supplied to [`_controlfp`](control87-controlfp-control87-2.md). The exact meaning of each bit depends on context:<br /><br /> `Cause` - Each set bit indicates the particular exception that was raised.<br />`Enable` - Each set bit indicates that the particular exception is currently unmasked.<br />`Status` - Each set bit indicates that the particular exception is currently pending. This includes exceptions that have not been raised because they were masked by `_controlfp`.|
+|`Operand1`<br/>`Operand2`<br/>`Result`|These `_FPIEEE_VALUE` structures indicate the types and values of the proposed result and operands. Each structure contains these fields:<br /><br /> `OperandValid` - Flag indicating whether the responding value is valid.<br />`Format` - Data type of the corresponding value. The format type might be returned even if the corresponding value isn't valid.<br />`Value` - Result or operand data value.|
+|`Cause`<br/>`Enable`<br/>`Status`|`_FPIEEE_EXCEPTION_FLAGS` contains a bit field for each type of floating point exception. There's a correspondence between these fields and the arguments used to mask the exceptions supplied to [`_controlfp`](control87-controlfp-control87-2.md). The exact meaning of each bit depends on context:<br /><br /> `Cause` - Each set bit indicates the particular exception that was raised.<br />`Enable` - Each set bit indicates that the particular exception is currently unmasked.<br />`Status` - Each set bit indicates that the particular exception is currently pending, which includes exceptions that haven't been raised because they were masked by `_controlfp`.|
 
-Pending exceptions that are disabled are raised when you enable them. This can result in undefined behavior when using **`_fpieee_flt`** as an exception filter. Always call [`_clearfp`](clear87-clearfp.md) before enabling floating point exceptions.
+Pending exceptions that are disabled are raised when you enable them. These exceptions can result in undefined behavior when using **`_fpieee_flt`** as an exception filter. Always call [`_clearfp`](clear87-clearfp.md) before enabling floating point exceptions.
 
 ## Requirements
 

docs/c-runtime-library/reference/fpreset.md

@@ -22,7 +22,7 @@ void _fpreset( void );
 
 ## Remarks
 
-The **`_fpreset`** function reinitializes the floating-point math package. **`_fpreset`** is usually used with `signal`, `system`, or the `_exec` or `_spawn` functions. If a program traps floating-point error signals (`SIGFPE`) with `signal`, it can safely recover from floating-point errors by invoking **`_fpreset`** and using `longjmp`.
+The **`_fpreset`** function reinitializes the floating-point math package. **`_fpreset`** is often used with `signal`, `system`, or the `_exec` or `_spawn` functions. If a program traps floating-point error signals (`SIGFPE`) with `signal`, it can safely recover from floating-point errors by invoking **`_fpreset`** and using `longjmp`.
 
 This function is deprecated when compiling with [/clr (Common Language Runtime Compilation)](../../build/reference/clr-common-language-runtime-compilation.md) because the common language runtime only supports the default floating-point precision.
 

docs/c-runtime-library/reference/fprintf-p-fprintf-p-l-fwprintf-p-fwprintf-p-l.md

@@ -60,7 +60,7 @@ The locale to use.
 
 ## Remarks
 
-**`_fprintf_p`** formats and prints a series of characters and values to the output *`stream`*. Each function *`argument`* (if any) is converted and output according to the corresponding format specification in *`format`*. For **`_fprintf_p`**, the *`format`* argument has the same syntax and use that it has in `_printf_p`. These functions support positional parameters, meaning that the order of the parameters used by the format string can be changed. For more information about positional parameters, see [printf_p Positional Parameters](../printf-p-positional-parameters.md).
+**`_fprintf_p`** formats and prints a series of characters and values to the output *`stream`*. Each function *`argument`* (if any) is converted and output according to the corresponding format specification in *`format`*. For **`_fprintf_p`**, the *`format`* argument has the same syntax that it has in `_printf_p`. These functions support positional parameters, meaning that the order of the parameters used by the format string can be changed. For more information about positional parameters, see [printf_p Positional Parameters](../printf-p-positional-parameters.md).
 
 **`_fwprintf_p`** is a wide-character version of **`_fprintf_p`**; in **`_fwprintf_p`**, *`format`* is a wide-character string. These functions behave identically if the stream is opened in ANSI mode. **`_fprintf_p`** doesn't currently support output into a UNICODE stream.
 

docs/c-runtime-library/reference/fputc-nolock-fputwc-nolock.md

@@ -41,9 +41,9 @@ Each of these functions returns the character written. For error information, se
 
 ## Remarks
 
-**`_fputc_nolock`** and **`_fputwc_nolock`** are identical to `fputc` and `fputwc`, respectively, except that they are not protected from interference by other threads. They might be faster because they do not incur the overhead of locking out other threads. Use these functions only in thread-safe contexts such as single-threaded applications or where the calling scope already handles thread isolation.
+**`_fputc_nolock`** and **`_fputwc_nolock`** are identical to `fputc` and `fputwc`, respectively, except that they aren't protected from interference by other threads. They might be faster because they don't incur the overhead of locking out other threads. Use these functions only in thread-safe contexts such as single-threaded applications or where the calling scope already handles thread isolation.
 
-The two functions behave identically if the stream is opened in ANSI mode. **`_fputc_nolock`** does not currently support output into a UNICODE stream.
+The two functions behave identically if the stream is opened in ANSI mode. **`_fputc_nolock`** doesn't currently support output into a UNICODE stream.
 
 By default, this function's global state is scoped to the application. To change this behavior, see [Global state in the CRT](../global-state.md).
 
@@ -60,7 +60,7 @@ By default, this function's global state is scoped to the application. To change
 |**`_fputc_nolock`**|\<stdio.h>|
 |**`_fputwc_nolock`**|\<stdio.h> or \<wchar.h>|
 
-The console is not supported in Universal Windows Platform (UWP) apps. The standard stream handles that are associated with the console—`stdin`, `stdout`, and `stderr`—must be redirected before C run-time functions can use them in UWP apps. For more compatibility information, see [Compatibility](../compatibility.md).
+The console isn't supported in Universal Windows Platform (UWP) apps. The standard stream handles that are associated with the console—`stdin`, `stdout`, and `stderr`—must be redirected before C run-time functions can use them in UWP apps. For more compatibility information, see [Compatibility](../compatibility.md).
 
 ## Example
 

docs/c-runtime-library/reference/fputchar-fputwchar.md

@@ -32,13 +32,13 @@ Character to be written.
 
 ## Return value
 
-Each of these functions returns the character written. For **`_fputchar`**, a return value of `EOF` indicates an error. For **`_fputwchar`**, a return value of `WEOF` indicates an error. If c is `NULL`, these functions generate an invalid parameter exception, as described in [Parameter validation](../parameter-validation.md). If execution is allowed to continue, they return `EOF` (or `WEOF`) and set `errno` to `EINVAL`.
+Each of these functions returns the character written. For **`_fputchar`**, a return value of `EOF` indicates an error. For **`_fputwchar`**, a return value of `WEOF` indicates an error. If c is `NULL`, these functions generate an invalid parameter exception, as described in [Parameter validation](../parameter-validation.md). If execution is allowed to continue, **`_fputchar`** returns `EOF` (**`_fputwchar`** returns `WEOF`), and they set `errno` to `EINVAL`.
 
 For more information about these and other error codes, see [`errno`, `_doserrno`, `_sys_errlist`, and `_sys_nerr`](../errno-doserrno-sys-errlist-and-sys-nerr.md).
 
 ## Remarks
 
-Both of these functions writes the single character *`c`* to `stdout` and advances the indicator as appropriate. **`_fputchar`** is equivalent to `fputc( stdout )`. It is also equivalent to `putchar`, but implemented only as a function, rather than as a function and a macro. Unlike `fputc` and `putchar`, these functions are not compatible with the ANSI standard.
+Both of these functions write the single character argument *`c`* to `stdout` and advance the indicator as appropriate. **`_fputchar`** is equivalent to `fputc( stdout )`. It's also equivalent to `putchar`, but implemented only as a function, rather than as a function and a macro. Unlike `fputc` and `putchar`, these functions aren't compatible with the ANSI standard.
 
 By default, this function's global state is scoped to the application. To change this behavior, see [Global state in the CRT](../global-state.md).
 
@@ -55,7 +55,7 @@ By default, this function's global state is scoped to the application. To change
 |**`_fputchar`**|\<stdio.h>|
 |**`_fputwchar`**|\<stdio.h> or \<wchar.h>|
 
-The console is not supported in Universal Windows Platform (UWP) apps. The standard stream handles that are associated with the console—`stdin`, `stdout`, and `stderr`—must be redirected before C run-time functions can use them in UWP apps. For more compatibility information, see [Compatibility](../compatibility.md).
+The console isn't supported in Universal Windows Platform (UWP) apps. The standard stream handles that are associated with the console—`stdin`, `stdout`, and `stderr`—must be redirected before C run-time functions can use them in UWP apps. For more compatibility information, see [Compatibility](../compatibility.md).
 
 ## Example
 

docs/c-runtime-library/reference/fputs-fputws.md

@@ -36,13 +36,13 @@ Pointer to `FILE` structure.
 
 ## Return value
 
-Each of these functions returns a nonnegative value if it is successful. On an error, **`fputs`** and **`fputws`** return `EOF`. If *`str`* or *`stream`* is a null pointer, these functions invoke the invalid parameter handler, as described in [Parameter validation](../parameter-validation.md). If execution is allowed to continue, these functions set `errno` to `EINVAL` and then return `EOF`.
+Each of these functions returns a nonnegative value if it's successful. On an error, **`fputs`** and **`fputws`** return `EOF`. If *`str`* or *`stream`* is a null pointer, these functions invoke the invalid parameter handler, as described in [Parameter validation](../parameter-validation.md). If execution is allowed to continue, these functions set `errno` to `EINVAL` and then return `EOF`.
 
 For more information on error codes, see [`errno`, `_doserrno`, `_sys_errlist`, and `_sys_nerr`](../errno-doserrno-sys-errlist-and-sys-nerr.md).
 
 ## Remarks
 
-Each of these functions copies *`str`* to the output *`stream`* at the current position. **`fputws`** copies the wide-character argument *`str`* to *`stream`* as a multibyte-character string or a wide-character string according to whether *`stream`* is opened in text mode or binary mode, respectively. Neither function copies the terminating null character.
+Each of these functions copies *`str`* to the output *`stream`* at the current position. **`fputws`** copies the wide-character argument *`str`* to *`stream`* as a multibyte-character string or a wide-character string when *`stream`* is opened in text mode or binary mode, respectively. Neither function copies the terminating null character.
 
 The two functions behave identically if the stream is opened in ANSI mode. **`fputs`** doesn't currently support output into a UNICODE stream.
 

docs/c-runtime-library/reference/fread-nolock-s2.md

@@ -48,7 +48,7 @@ See [`fread_s`](fread-s.md).
 
 ## Remarks
 
-This function is a non-locking version of `fread_s`. It is identical to `fread_s` except that it is not protected from interference by other threads. It might be faster because it does not incur the overhead of locking out other threads. Use this function only in thread-safe contexts such as single-threaded applications or where the calling scope already handles thread isolation.
+This function is a non-locking version of `fread_s`. It's identical to `fread_s` except that it isn't protected from interference by other threads. It might be faster because it doesn't incur the overhead of locking out other threads. Use this function only in thread-safe contexts such as single-threaded applications or where the calling scope already handles thread isolation.
 
 By default, this function's global state is scoped to the application. To change this behavior, see [Global state in the CRT](../global-state.md).
 

docs/c-runtime-library/reference/fread-nolock.md

@@ -45,7 +45,7 @@ See [`fread`](fread.md).
 
 ## Remarks
 
-This function is a non-locking version of `fread`. It is identical to `fread` except that it is not protected from interference by other threads. It might be faster because it does not incur the overhead of locking out other threads. Use this function only in thread-safe contexts such as single-threaded applications or where the calling scope already handles thread isolation.
+This function is a non-locking version of `fread`. It's identical to `fread` except that it isn't protected from interference by other threads. It might be faster because it doesn't incur the overhead of locking out other threads. Use this function only in thread-safe contexts such as single-threaded applications or where the calling scope already handles thread isolation.
 
 By default, this function's global state is scoped to the application. To change this behavior, see [Global state in the CRT](../global-state.md).