Fix all code blocks

Author: Colin Robertson

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

@@ -39,7 +39,7 @@ void abort( void );
 
 **Microsoft Specific**
 
-By default, when an app is built with the debug runtime library, the `abort` routine displays an error message before `SIGABRT` is raised. For console apps running in console mode, the message is sent to `STDERR`. Windows desktop apps and console apps running in windowed mode display the message in a message box. To suppress the message, use [_set_abort_behavior](../../c-runtime-library/reference/set-abort-behavior.md) to clear the `_WRITE_ABORT_MSG` flag. The message displayed depends on the version of the runtime environment used. For applications built by using the most recent versions of Visual C++, the message resembles this:
+By default, when an app is built with the debug runtime library, the `abort` routine displays an error message before `SIGABRT` is raised. For console apps running in console mode, the message is sent to `STDERR`. Windows desktop apps and console apps running in windowed mode display the message in a message box. To suppress the message, use [_set_abort_behavior](set-abort-behavior.md) to clear the `_WRITE_ABORT_MSG` flag. The message displayed depends on the version of the runtime environment used. For applications built by using the most recent versions of Visual C++, the message resembles this:
 
 > R6010 - abort() has been called
 
@@ -49,11 +49,11 @@ In previous versions of the C runtime library, this message was displayed:
 
 When the program is compiled in debug mode, the message box displays options to **Abort**, **Retry**, or **Ignore**. If the user chooses **Abort**, the program terminates immediately and returns an exit code of 3. If the user chooses **Retry**, a debugger is invoked for just-in-time debugging, if available. If the user chooses **Ignore**, `abort` continues normal processing.
 
-In both retail and debug builds, `abort` then checks whether an abort signal handler is set. If a non-default signal handler is set, `abort` calls `raise(SIGABRT)`. Use the [signal](../../c-runtime-library/reference/signal.md) function to associate an abort signal handler function with the `SIGABRT` signal. You can perform custom actions—for example, clean up resources or log information—and terminate the app with your own error code in the handler function. If no custom signal handler is defined, `abort` does not raise the `SIGABRT` signal.
+In both retail and debug builds, `abort` then checks whether an abort signal handler is set. If a non-default signal handler is set, `abort` calls `raise(SIGABRT)`. Use the [signal](signal.md) function to associate an abort signal handler function with the `SIGABRT` signal. You can perform custom actions—for example, clean up resources or log information—and terminate the app with your own error code in the handler function. If no custom signal handler is defined, `abort` does not raise the `SIGABRT` signal.
 
 By default, in non-debug builds of desktop or console apps, `abort` then invokes the Windows Error Reporting Service mechanism (formerly known as Dr. Watson) to report failures to Microsoft. This behavior can be enabled or disabled by calling `_set_abort_behavior` and setting or masking the `_CALL_REPORTFAULT` flag. When the flag is set, Windows displays a message box that has text something like "A problem caused the program to stop working correctly." The user can choose to invoke a debugger with a **Debug** button, or choose the **Close program** button to terminate the app with an error code that's defined by the operating system.
 
-If the Windows error reporting handler is not invoked, then `abort` calls [_exit](../../c-runtime-library/reference/exit-exit-exit.md) to terminate the process with exit code 3 and returns control to the parent process or the operating system. `_exit` does not flush stream buffers or do `atexit`/`_onexit` processing.
+If the Windows error reporting handler is not invoked, then `abort` calls [_exit](exit-exit-exit.md) to terminate the process with exit code 3 and returns control to the parent process or the operating system. `_exit` does not flush stream buffers or do `atexit`/`_onexit` processing.
 
 For more information about CRT debugging, see [CRT Debugging Techniques](/visualstudio/debugger/crt-debugging-techniques).
 
@@ -107,9 +107,9 @@ File could not be opened: No such file or directory
 [abort Function](../../c-language/abort-function-c.md)<br/>
 [Process and Environment Control](../../c-runtime-library/process-and-environment-control.md)<br/>
 [_exec, _wexec Functions](../../c-runtime-library/exec-wexec-functions.md)<br/>
-[exit, _Exit, _exit](../../c-runtime-library/reference/exit-exit-exit.md)<br/>
-[raise](../../c-runtime-library/reference/raise.md)<br/>
-[signal](../../c-runtime-library/reference/signal.md)<br/>
+[exit, _Exit, _exit](exit-exit-exit.md)<br/>
+[raise](raise.md)<br/>
+[signal](signal.md)<br/>
 [_spawn, _wspawn Functions](../../c-runtime-library/spawn-wspawn-functions.md)<br/>
 [_DEBUG](../../c-runtime-library/debug.md)<br/>
-[_set_abort_behavior](../../c-runtime-library/reference/set-abort-behavior.md)<br/>
+[_set_abort_behavior](set-abort-behavior.md)<br/>

docs/c-runtime-library/reference/abs-labs-llabs-abs64.md

@@ -126,6 +126,6 @@ _abs64(_I64_MIN) returns 0x8000000000000000
 
 [Data Conversion](../../c-runtime-library/data-conversion.md)<br/>
 [Floating-Point Support](../../c-runtime-library/floating-point-support.md)<br/>
-[_cabs](../../c-runtime-library/reference/cabs.md)<br/>
-[fabs, fabsf, fabsl](../../c-runtime-library/reference/fabs-fabsf-fabsl.md)<br/>
-[imaxabs](../../c-runtime-library/reference/imaxabs.md)<br/>
+[_cabs](cabs.md)<br/>
+[fabs, fabsf, fabsl](fabs-fabsf-fabsl.md)<br/>
+[imaxabs](imaxabs.md)<br/>

docs/c-runtime-library/reference/access-crt.md

@@ -21,4 +21,4 @@ manager: "ghogen"
 ms.workload: ["cplusplus"]
 ---
 # access (CRT)
-This POSIX function is deprecated. Use the ISO C++ conformant [_access](../../c-runtime-library/reference/access-waccess.md) or security-enhanced [_access_s](../../c-runtime-library/reference/access-s-waccess-s.md) instead.
+This POSIX function is deprecated. Use the ISO C++ conformant [_access](access-waccess.md) or security-enhanced [_access_s](access-s-waccess-s.md) instead.

docs/c-runtime-library/reference/access-s-waccess-s.md

@@ -22,7 +22,7 @@ ms.workload: ["cplusplus"]
 ---
 # _access_s, _waccess_s
 
-Determines file read/write permissions. This is a version of [_access, _waccess](../../c-runtime-library/reference/access-waccess.md) with security enhancements as described in [Security Features in the CRT](../../c-runtime-library/security-features-in-the-crt.md).
+Determines file read/write permissions. This is a version of [_access, _waccess](access-waccess.md) with security enhancements as described in [Security Features in the CRT](../../c-runtime-library/security-features-in-the-crt.md).
 
 ## Syntax
 
@@ -94,7 +94,7 @@ These functions validate their parameters. If *path* is `NULL` or *mode* does no
 
 This example uses `_access_s` to check the file named crt_access_s.c to see whether it exists and whether writing is allowed.
 
-```
+```C
 // crt_access_s.c
 
 #include <io.h>
@@ -137,8 +137,8 @@ File crt_access_s.c does not have write permission.
 ## See also
 
 [File Handling](../../c-runtime-library/file-handling.md)<br/>
-[_access, _waccess](../../c-runtime-library/reference/access-waccess.md)<br/>
-[_chmod, _wchmod](../../c-runtime-library/reference/chmod-wchmod.md)<br/>
-[_fstat, _fstat32, _fstat64, _fstati64, _fstat32i64, _fstat64i32](../../c-runtime-library/reference/fstat-fstat32-fstat64-fstati64-fstat32i64-fstat64i32.md)<br/>
-[_open, _wopen](../../c-runtime-library/reference/open-wopen.md)<br/>
-[_stat, _wstat Functions](../../c-runtime-library/reference/stat-functions.md)<br/>
+[_access, _waccess](access-waccess.md)<br/>
+[_chmod, _wchmod](chmod-wchmod.md)<br/>
+[_fstat, _fstat32, _fstat64, _fstati64, _fstat32i64, _fstat64i32](fstat-fstat32-fstat64-fstati64-fstat32i64-fstat64i32.md)<br/>
+[_open, _wopen](open-wopen.md)<br/>
+[_stat, _wstat Functions](stat-functions.md)<br/>

docs/c-runtime-library/reference/access-waccess.md

@@ -22,7 +22,7 @@ ms.workload: ["cplusplus"]
 ---
 # _access, _waccess
 
-Determines if a file is read-only or not. More secure versions are available; see [_access_s, _waccess_s](../../c-runtime-library/reference/access-s-waccess-s.md).
+Determines if a file is read-only or not. More secure versions are available; see [_access_s, _waccess_s](access-s-waccess-s.md).
 
 ## Syntax
 
@@ -49,14 +49,11 @@ Read/write attribute.
 
 Each function returns 0 if the file has the given mode. The function returns -1 if the named file does not exist or does not have the given mode; in this case, `errno` is set as shown in the following table.
 
-`EACCES`
-Access denied: the file's permission setting does not allow specified access.
-
-`ENOENT`
-File name or path not found.
-
-`EINVAL`
-Invalid parameter.
+|||
+|-|-|
+`EACCES`|Access denied: the file's permission setting does not allow specified access.
+`ENOENT`|File name or path not found.
+`EINVAL`|Invalid parameter.
 
 For more information about these and other return codes, see [_doserrno, errno, _sys_errlist, and _sys_nerr](../../c-runtime-library/errno-doserrno-sys-errlist-and-sys-nerr.md).
 
@@ -94,7 +91,7 @@ This function validates its parameters. If *path* is `NULL` or *mode* does not s
 
 The following example uses `_access` to check the file named crt_ACCESS.C to see whether it exists and whether writing is allowed.
 
-```
+```C
 // crt_access.c
 // compile with: /W1
 // This example uses _access to check the file named
@@ -127,7 +124,7 @@ File crt_ACCESS.C does not have write permission.
 ## See also
 
 [File Handling](../../c-runtime-library/file-handling.md)<br/>
-[_chmod, _wchmod](../../c-runtime-library/reference/chmod-wchmod.md)<br/>
-[_fstat, _fstat32, _fstat64, _fstati64, _fstat32i64, _fstat64i32](../../c-runtime-library/reference/fstat-fstat32-fstat64-fstati64-fstat32i64-fstat64i32.md)<br/>
-[_open, _wopen](../../c-runtime-library/reference/open-wopen.md)<br/>
-[_stat, _wstat Functions](../../c-runtime-library/reference/stat-functions.md)<br/>
+[_chmod, _wchmod](chmod-wchmod.md)<br/>
+[_fstat, _fstat32, _fstat64, _fstati64, _fstat32i64, _fstat64i32](fstat-fstat32-fstat64-fstati64-fstat32i64-fstat64i32.md)<br/>
+[_open, _wopen](open-wopen.md)<br/>
+[_stat, _wstat Functions](stat-functions.md)<br/>

docs/c-runtime-library/reference/acos-acosf-acosl.md

@@ -117,9 +117,9 @@ Arccosine of 0.000000 = 1.570796
 ## See also
 
 [Floating-Point Support](../../c-runtime-library/floating-point-support.md)<br/>
-[asin, asinf, asinl](../../c-runtime-library/reference/asin-asinf-asinl.md)<br/>
-[atan, atanf, atanl, atan2, atan2f, atan2l](../../c-runtime-library/reference/atan-atanf-atanl-atan2-atan2f-atan2l.md)<br/>
-[cos, cosf, cosl](../../c-runtime-library/reference/cos-cosf-cosl.md)<br/>
-[_matherr](../../c-runtime-library/reference/matherr.md)<br/>
-[sin, sinf, sinl](../../c-runtime-library/reference/sin-sinf-sinl.md)<br/>
-[tan, tanf, tanl](../../c-runtime-library/reference/tan-tanf-tanl.md)<br/>
+[asin, asinf, asinl](asin-asinf-asinl.md)<br/>
+[atan, atanf, atanl, atan2, atan2f, atan2l](atan-atanf-atanl-atan2-atan2f-atan2l.md)<br/>
+[cos, cosf, cosl](cos-cosf-cosl.md)<br/>
+[_matherr](matherr.md)<br/>
+[sin, sinf, sinl](sin-sinf-sinl.md)<br/>
+[tan, tanf, tanl](tan-tanf-tanl.md)<br/>

docs/c-runtime-library/reference/acosh-acoshf-acoshl.md

@@ -94,8 +94,8 @@ acosh( 1.324609 ) = 0.785398
 ## See also
 
 [Floating-Point Support](../../c-runtime-library/floating-point-support.md)<br/>
-[asinh, asinhf, asinhl](../../c-runtime-library/reference/asinh-asinhf-asinhl.md)<br/>
-[atanh, atanhf, atanhl](../../c-runtime-library/reference/atanh-atanhf-atanhl.md)<br/>
-[cosh, coshf, coshl](../../c-runtime-library/reference/cosh-coshf-coshl.md)<br/>
-[sinh, sinhf, sinhl](../../c-runtime-library/reference/sinh-sinhf-sinhl.md)<br/>
-[tanh, tanhf, tanhl](../../c-runtime-library/reference/tanh-tanhf-tanhl.md)<br/>
+[asinh, asinhf, asinhl](asinh-asinhf-asinhl.md)<br/>
+[atanh, atanhf, atanhl](atanh-atanhf-atanhl.md)<br/>
+[cosh, coshf, coshl](cosh-coshf-coshl.md)<br/>
+[sinh, sinhf, sinhl](sinh-sinhf-sinhl.md)<br/>
+[tanh, tanhf, tanhl](tanh-tanhf-tanhl.md)<br/>

docs/c-runtime-library/reference/aligned-free-dbg.md

@@ -22,7 +22,7 @@ ms.workload: ["cplusplus"]
 ---
 # _aligned_free_dbg
 
-Frees a block of memory that was allocated with [_aligned_malloc](../../c-runtime-library/reference/aligned-malloc.md) or [_aligned_offset_malloc](../../c-runtime-library/reference/aligned-offset-malloc.md) (debug only).
+Frees a block of memory that was allocated with [_aligned_malloc](aligned-malloc.md) or [_aligned_offset_malloc](aligned-offset-malloc.md) (debug only).
 
 ## Syntax
 
@@ -39,7 +39,7 @@ A pointer to the memory block that was returned to the `_aligned_malloc` or `_al
 
 ## Remarks
 
-The `_aligned_free_dbg` function is a debug version of the [_aligned_free](../../c-runtime-library/reference/aligned-free.md) function. When [_DEBUG](../../c-runtime-library/debug.md) is not defined, each call to `_aligned_free_dbg` is reduced to a call to `_aligned_free`. Both `_aligned_free` and `_aligned_free_dbg` free a memory block in the base heap, but `_aligned_free_dbg` accommodates a debugging feature: the ability to keep freed blocks in the heap's linked list to simulate low memory conditions.
+The `_aligned_free_dbg` function is a debug version of the [_aligned_free](aligned-free.md) function. When [_DEBUG](../../c-runtime-library/debug.md) is not defined, each call to `_aligned_free_dbg` is reduced to a call to `_aligned_free`. Both `_aligned_free` and `_aligned_free_dbg` free a memory block in the base heap, but `_aligned_free_dbg` accommodates a debugging feature: the ability to keep freed blocks in the heap's linked list to simulate low memory conditions.
 
 `_aligned_free_dbg` performs a validity check on all specified files and block locations before performing the free operation. The application is not expected to provide this information. When a memory block is freed, the debug heap manager automatically checks the integrity of the buffers on either side of the user portion and issues an error report if overwriting has occurred. If the `_CRTDBG_DELAY_FREE_MEM_DF` bit field of the [_crtDbgFlag](../../c-runtime-library/crtdbgflag.md) flag is set, the freed block is filled with the value 0xDD, assigned the `_FREE_BLOCK` block type, and kept in the heap's linked list of memory blocks.
 

docs/c-runtime-library/reference/aligned-free.md

@@ -22,7 +22,7 @@ ms.workload: ["cplusplus"]
 ---
 # _aligned_free
 
-Frees a block of memory that was allocated with [_aligned_malloc](../../c-runtime-library/reference/aligned-malloc.md) or [_aligned_offset_malloc](../../c-runtime-library/reference/aligned-offset-malloc.md).
+Frees a block of memory that was allocated with [_aligned_malloc](aligned-malloc.md) or [_aligned_offset_malloc](aligned-offset-malloc.md).
 
 ## Syntax
 
@@ -41,7 +41,7 @@ A pointer to the memory block that was returned to the `_aligned_malloc` or `_al
 
 `_aligned_free` is marked `__declspec(noalias)`, meaning that the function is guaranteed not to modify global variables. For more information, see [noalias](../../cpp/noalias.md).
 
-This function does not validate its parameter, unlike the other _aligned CRT functions. If *memblock* is a `NULL` pointer, this function simply performs no actions. It does not change `errno` and it does not invoke the invalid parameter handler. If an error occurs in the function due to not using _aligned functions previously to allocate the block of memory or a misalignment of memory occurs due to some unforeseen calamity, the function generates a debug report from the [_RPT, _RPTF, _RPTW, _RPTFW Macros](../../c-runtime-library/reference/rpt-rptf-rptw-rptfw-macros.md).
+This function does not validate its parameter, unlike the other _aligned CRT functions. If *memblock* is a `NULL` pointer, this function simply performs no actions. It does not change `errno` and it does not invoke the invalid parameter handler. If an error occurs in the function due to not using _aligned functions previously to allocate the block of memory or a misalignment of memory occurs due to some unforeseen calamity, the function generates a debug report from the [_RPT, _RPTF, _RPTW, _RPTFW Macros](rpt-rptf-rptw-rptfw-macros.md).
 
 ## Requirements
 
@@ -51,7 +51,7 @@ This function does not validate its parameter, unlike the other _aligned CRT fun
 
 ## Example
 
-For more information, see [_aligned_malloc](../../c-runtime-library/reference/aligned-malloc.md).
+For more information, see [_aligned_malloc](aligned-malloc.md).
 
 ## See also
 

docs/c-runtime-library/reference/aligned-malloc-dbg.md

@@ -55,7 +55,7 @@ A pointer to the memory block that was allocated or `NULL` if the operation fail
 
 ## Remarks
 
-`_aligned_malloc_dbg` is a debug version of the [_aligned_malloc](../../c-runtime-library/reference/aligned-malloc.md) function. When [_DEBUG](../../c-runtime-library/debug.md) is not defined, each call to `_aligned_malloc_dbg` is reduced to a call to `_aligned_malloc`. Both `_aligned_malloc` and `_aligned_malloc_dbg` allocate a block of memory in the base heap, but `_aligned_malloc_dbg` offers several debugging features: buffers on either side of the user portion of the block to test for leaks, and *filename*/*linenumber* information to determine the origin of allocation requests.
+`_aligned_malloc_dbg` is a debug version of the [_aligned_malloc](aligned-malloc.md) function. When [_DEBUG](../../c-runtime-library/debug.md) is not defined, each call to `_aligned_malloc_dbg` is reduced to a call to `_aligned_malloc`. Both `_aligned_malloc` and `_aligned_malloc_dbg` allocate a block of memory in the base heap, but `_aligned_malloc_dbg` offers several debugging features: buffers on either side of the user portion of the block to test for leaks, and *filename*/*linenumber* information to determine the origin of allocation requests.
 
 `_aligned_malloc_dbg` allocates the memory block with slightly more space than the requested *size*. The additional space is used by the debug heap manager to link the debug memory blocks and to provide the application with debug header information and overwrite buffers. When the block is allocated, the user portion of the block is filled with the value 0xCD and each of the overwrite buffers are filled with 0xFD.
 

docs/c-runtime-library/reference/aligned-malloc.md

@@ -47,7 +47,7 @@ A pointer to the memory block that was allocated or `NULL` if the operation fail
 
 ## Remarks
 
-`_aligned_malloc` is based on [malloc](../../c-runtime-library/reference/malloc.md).
+`_aligned_malloc` is based on [malloc](malloc.md).
 
 `_aligned_malloc` is marked `__declspec(noalias)` and `__declspec(restrict)`, meaning that the function is guaranteed not to modify global variables and that the pointer returned is not aliased. For more information, see [noalias](../../cpp/noalias.md) and [restrict](../../cpp/restrict.md).
 
@@ -61,7 +61,7 @@ This function sets `errno` to `ENOMEM` if the memory allocation failed or if the
 
 ## Example
 
-```
+```C
 // crt_aligned_malloc.c
 
 #include <malloc.h>

docs/c-runtime-library/reference/aligned-msize-dbg.md

@@ -53,7 +53,7 @@ Returns the size (in bytes) as an unsigned integer.
 
 The *alignment* and *offset* values must be the same as the values passed to the function that allocated the block.
 
-`_aligned_msize_dbg` is a debug version of the [_aligned_msize](../../c-runtime-library/reference/aligned-msize.md) function. When [_DEBUG](../../c-runtime-library/debug.md) is not defined, each call to `_aligned_msize_dbg` is reduced to a call to `_aligned_msize`. Both `_aligned_msize` and `_aligned_msize_dbg` calculate the size of a memory block in the base heap, but `_aligned_msize_dbg` adds a debugging feature: It includes the buffers on either side of the user portion of the memory block in the returned size.
+`_aligned_msize_dbg` is a debug version of the [_aligned_msize](aligned-msize.md) function. When [_DEBUG](../../c-runtime-library/debug.md) is not defined, each call to `_aligned_msize_dbg` is reduced to a call to `_aligned_msize`. Both `_aligned_msize` and `_aligned_msize_dbg` calculate the size of a memory block in the base heap, but `_aligned_msize_dbg` adds a debugging feature: It includes the buffers on either side of the user portion of the memory block in the returned size.
 
 This function validates its parameter. If *memblock* is a null pointer or *alignment* is not a power of 2, `_msize` invokes an invalid parameter handler, as described in [Parameter Validation](../../c-runtime-library/parameter-validation.md). If the error is handled, the function sets `errno` to `EINVAL` and returns -1.