acrolinx

Author: TylerMSFT

docs/build/reference/oi-generate-intrinsic-functions.md

@@ -17,18 +17,18 @@ Replaces some function calls with intrinsic or otherwise special forms of the fu
 
 ## Remarks
 
-Programs that use intrinsic functions are faster because they do not have the overhead of function calls but may be larger because of the additional code created.
+Programs that use intrinsic functions are faster because they don't have the overhead of function calls but may be larger because of the extra code created.
 
-See [intrinsic](../../preprocessor/intrinsic.md) for more information on which functions have intrinsic forms.
+For more information about which functions have intrinsic forms, see [intrinsic](../../preprocessor/intrinsic.md).
 
-**/Oi** is only a request to the compiler to replace some function calls with intrinsics. The compiler may call the function (and not replace the function call with an intrinsic) if it will result in better performance.\
+**/Oi** is only a request to the compiler to replace some function calls with intrinsics. The compiler may call the function (and not replace the function call with an intrinsic) if it results in better performance.\
 **/Oi-** turns off this behavior, which may be useful if `/Oi` has been specified elsewhere and you want to override it.
 
 **x86 Specific**
 
-The intrinsic floating-point functions do not perform any special checks on input values and so work in restricted ranges of input, and have different exception handling and boundary conditions than the library routines with the same name. Using the true intrinsic forms implies loss of IEEE exception handling, and loss of `_matherr` and `errno` functionality; the latter implies loss of ANSI conformance. However, the intrinsic forms can considerably speed up floating-point-intensive programs, and for many programs, the conformance issues are of little practical value.
+The intrinsic floating-point functions don't perform any special checks on input values and so work in restricted ranges of input, and have different exception handling and boundary conditions than the library routines with the same name. Using the true intrinsic forms implies loss of IEEE exception handling, and loss of `_matherr` and `errno` functionality; the latter implies loss of ANSI conformance. However, the intrinsic forms can considerably speed up floating-point-intensive programs, and for many programs, the conformance issues are of little practical value.
 
-You can use the [Za](za-ze-disable-language-extensions.md) compiler option to override generation of true intrinsic floating-point options. In this case, the functions are generated as library routines that pass arguments directly to the floating-point chip instead of pushing them onto the program stack.
+You can use the [`Za`](za-ze-disable-language-extensions.md) compiler option to override generation of true intrinsic floating-point options. In this case, the functions are generated as library routines that pass arguments directly to the floating-point chip instead of pushing them onto the program stack.
 
 **END x86 Specific**