RomandevJavaScript
diff --git a/‎docs/atl-mfc-shared/strings-atl-mfc.md‎
Lines changed: 6 additions & 7 deletions b/‎docs/atl-mfc-shared/strings-atl-mfc.md‎
Lines changed: 6 additions & 7 deletions
diff --git a/‎docs/atl/reference/cregkey-class.md‎
Lines changed: 292 additions & 293 deletions b/‎docs/atl/reference/cregkey-class.md‎
Lines changed: 292 additions & 293 deletions
diff --git a/‎docs/c-runtime-library/format-specification-fields-scanf-and-wscanf-functions.md‎
Lines changed: 7 additions & 8 deletions b/‎docs/c-runtime-library/format-specification-fields-scanf-and-wscanf-functions.md‎
Lines changed: 7 additions & 8 deletions
diff --git a/‎docs/c-runtime-library/reference/crtdumpmemoryleaks.md‎
Lines changed: 10 additions & 11 deletions b/‎docs/c-runtime-library/reference/crtdumpmemoryleaks.md‎
Lines changed: 10 additions & 11 deletions
diff --git a/‎docs/c-runtime-library/reference/fflush.md‎
Lines changed: 15 additions & 16 deletions b/‎docs/c-runtime-library/reference/fflush.md‎
Lines changed: 15 additions & 16 deletions
diff --git a/‎docs/c-runtime-library/reference/getch.md‎
Lines changed: 2 additions & 3 deletions b/‎docs/c-runtime-library/reference/getch.md‎
Lines changed: 2 additions & 3 deletions
@@ -3,26 +3,25 @@ description: "Learn more about: Strings (ATL/MFC)"
 title: "Strings (ATL-MFC)"
 ms.date: "11/04/2016"
 helpviewer_keywords: ["const char pointers", "strings [C++], in ATL", "MFC [C++], string handling class", "MBCS [C++], CString support", "strings [C++], class CStringT", "char pointers", "reference counting [C++]", "strings [C++], string operations", "portability [C++], Unicode and ANSI string objects", "literal strings [C++], class CString", "copying string objects", "ATL, string handling class", "strings [C++], in MFC", "strings [C++]", "C-style strings", "language portability [C++]", "strings [C++], class CString", "literal strings [C++], class CStringT"]
-ms.assetid: 3b33125b-1684-4542-a3a7-b00de7d0419e
 ---
 # Strings (ATL/MFC)
 
 Nearly all programs work with string data. Visual C++ provides several ways to manage this string data.
 
 ## In This Section
 
-[Using CStringT](../atl-mfc-shared/using-cstringt.md)<br/>
-Describes programming using the template class CStringT.
+[Using `CStringT`](../atl-mfc-shared/using-cstringt.md)\
+Describes programming using the template class `CStringT`.
 
-[Using CString](../atl-mfc-shared/using-cstring.md)<br/>
-Describes programming using CString, the default implementation of CStringT.
+[Using `CString`](../atl-mfc-shared/using-cstring.md)\
+Describes programming using `CString`, the default implementation of `CStringT`.
 
 ## Related Sections
 
-[CStringT Overview](../atl-mfc-shared/reference/cstringt-class.md)<br/>
+[`CStringT` Overview](../atl-mfc-shared/reference/cstringt-class.md)\
 Provides reference information about the shared `CStringT` class.
 
-[MFC Concepts](../mfc/mfc-concepts.md)<br/>
+[MFC Concepts](../mfc/mfc-concepts.md)\
 Provides conceptual and task-based topics to help you program using the MFC Library.
 
 ## See also
 
@@ -5,9 +5,8 @@ ms.date: "11/04/2016"
 ms.topic: "reference"
 ms.custom: contperf-fy21q1
 helpviewer_keywords: ["width, specifications in scanf function", "scanf format specifications", "scanf width specifications", "scanf type field characters", "type fields, scanf function", "format specification fields for scanf function", "type fields"]
-ms.assetid: 7e95de1b-0b71-4de3-9f81-c9560c78e039
 ---
-# Format Specification Fields: scanf and wscanf Functions
+# Format Specification Fields: `scanf` and `wscanf` Functions
 
 The information here applies to the entire `scanf` family of functions, including the secure versions and describes the symbols used to tell the `scanf` functions how to parse the input stream, such as the input stream `stdin` for `scanf`, into values that are inserted into program variables.
 
@@ -17,7 +16,7 @@ A format specification has the following form:
 
 The `format` argument specifies the interpretation of the input and can contain one or more of the following:
 
-- White-space characters: blank (' '); tab ('\t'); or newline ('\n'). A white-space character causes `scanf` to read, but not store, all consecutive white-space characters in the input up to the next non-white-space character. One white-space character in the format matches any number (including 0) and combination of white-space characters in the input.
+- White-space characters: blank (` `); tab (`\t`); or newline (`\n`). A white-space character causes `scanf` to read, but not store, all consecutive white-space characters in the input up to the next non-white-space character. One white-space character in the format matches any number (including 0) and combination of white-space characters in the input.
 
 - Non-white-space characters, except for the percent sign (`%`). A non-white-space character causes `scanf` to read, but not store, a matching non-white-space character. If the next character in the input stream does not match, `scanf` terminates.
 
@@ -35,11 +34,11 @@ The simplest format specification contains only the percent sign and a `type` ch
 
 An asterisk (`*`) following the percent sign suppresses assignment of the next input field, which is interpreted as a field of the specified type. The field is scanned but not stored.
 
-The secure versions (those with the `_s` suffix) of the `scanf` family of functions require that a buffer size parameter be passed immediately following each parameter of type `c`, `C`, `s`, `S` or `[`. For more information on the secure versions of the `scanf` family of functions, see [scanf_s, _scanf_s_l, wscanf_s, _wscanf_s_l](../c-runtime-library/reference/scanf-s-scanf-s-l-wscanf-s-wscanf-s-l.md).
+The secure versions (those with the `_s` suffix) of the `scanf` family of functions require that a buffer size parameter be passed immediately following each parameter of type `c`, `C`, `s`, `S` or `[`. For more information on the secure versions of the `scanf` family of functions, see [`scanf_s`, `_scanf_s_l`, `wscanf_s`, `_wscanf_s_l`](../c-runtime-library/reference/scanf-s-scanf-s-l-wscanf-s-wscanf-s-l.md).
 
 ## See also
 
-[scanf Width Specification](../c-runtime-library/scanf-width-specification.md)<br/>
-[scanf Type Field Characters](../c-runtime-library/scanf-type-field-characters.md)<br/>
-[scanf, _scanf_l, wscanf, _wscanf_l](../c-runtime-library/reference/scanf-scanf-l-wscanf-wscanf-l.md)<br/>
-[scanf_s, _scanf_s_l, wscanf_s, _wscanf_s_l](../c-runtime-library/reference/scanf-s-scanf-s-l-wscanf-s-wscanf-s-l.md)
+[`scanf` Width Specification](../c-runtime-library/scanf-width-specification.md)\
+[`scanf` Type Field Characters](../c-runtime-library/scanf-type-field-characters.md)\
+[`scanf`, `_scanf_l`, `wscanf`, `_wscanf_l`](../c-runtime-library/reference/scanf-scanf-l-wscanf-wscanf-l.md)\
+[`scanf_s`, `_scanf_s_l`, `wscanf_s`, `_wscanf_s_l`](../c-runtime-library/reference/scanf-s-scanf-s-l-wscanf-s-wscanf-s-l.md)
@@ -8,9 +8,8 @@ api_type: ["DLLExport"]
 topic_type: ["apiref"]
 f1_keywords: ["CRTDBG_LEAK_CHECK_DF", "CRTDBG_CHECK_CRT_DF", "_CRTDBG_LEAK_CHECK_DF", "CrtDumpMemoryLeaks", "_CrtDumpMemoryLeaks", "_CRTDBG_CHECK_CRT_DF"]
 helpviewer_keywords: ["CrtDumpMemoryLeaks function", "CRTDBG_LEAK_CHECK_DF macro", "_CRTDBG_LEAK_CHECK_DF macro", "_CrtDumpMemoryLeaks function", "CRTDBG_CHECK_CRT_DF macro", "_CRTDBG_CHECK_CRT_DF macro"]
-ms.assetid: 71b2eab4-7f55-44e8-a55a-bfea4f32d34c
 ---
-# _CrtDumpMemoryLeaks
+# `_CrtDumpMemoryLeaks`
 
 Dumps all the memory blocks in the debug heap when a memory leak has occurred (debug version only).
 
@@ -23,25 +22,25 @@ int _CrtDumpMemoryLeaks( void );
 
 ## Return Value
 
-**_CrtDumpMemoryLeaks** returns TRUE if a memory leak is found. Otherwise, the function returns FALSE.
+**`_CrtDumpMemoryLeaks`** returns `TRUE` if a memory leak is found. Otherwise, the function returns `FALSE`.
 
 ## Remarks
 
-The **_CrtDumpMemoryLeaks** function determines whether a memory leak has occurred since the start of program execution. When a leak is found, the debug header information for all the objects in the heap is dumped in a user-readable form. When [_DEBUG](../../c-runtime-library/debug.md) is not defined, calls to **_CrtDumpMemoryLeaks** are removed during preprocessing.
+The **`_CrtDumpMemoryLeaks`** function determines whether a memory leak has occurred since the start of program execution. When a leak is found, the debug header information for all the objects in the heap is dumped in a user-readable form. When [`_DEBUG`](../../c-runtime-library/debug.md) isn't defined, calls to **`_CrtDumpMemoryLeaks`** are removed during preprocessing.
 
-**_CrtDumpMemoryLeaks** is frequently called at the end of program execution to verify that all memory allocated by the application has been freed. The function can be called automatically at program termination by turning on the **_CRTDBG_LEAK_CHECK_DF** bit field of the [_crtDbgFlag](../../c-runtime-library/crtdbgflag.md) flag using the [_CrtSetDbgFlag](crtsetdbgflag.md) function.
+**`_CrtDumpMemoryLeaks`** is frequently called at the end of program execution to verify that all memory allocated by the application has been freed. The function can be called automatically at program termination by turning on the **`_CRTDBG_LEAK_CHECK_DF`** bit field of the [`_crtDbgFlag`](../../c-runtime-library/crtdbgflag.md) flag using the [`_CrtSetDbgFlag`](crtsetdbgflag.md) function.
 
-**_CrtDumpMemoryLeaks** calls [_CrtMemCheckpoint](crtmemcheckpoint.md) to obtain the current state of the heap and then scans the state for blocks that have not been freed. When an unfreed block is encountered, **_CrtDumpMemoryLeaks** calls [_CrtMemDumpAllObjectsSince](crtmemdumpallobjectssince.md) to dump information for all the objects allocated in the heap from the start of program execution.
+**`_CrtDumpMemoryLeaks`** calls [`_CrtMemCheckpoint`](crtmemcheckpoint.md) to obtain the current state of the heap and then scans the state for blocks that haven't been freed. When an unfreed block is encountered, **`_CrtDumpMemoryLeaks`** calls [`_CrtMemDumpAllObjectsSince`](crtmemdumpallobjectssince.md) to dump information for all the objects allocated in the heap from the start of program execution.
 
-By default, internal C run-time blocks (**_CRT_BLOCK**) are not included in memory dump operations. The [_CrtSetDbgFlag](crtsetdbgflag.md) function can be used to turn on the **_CRTDBG_CHECK_CRT_DF** bit of **_crtDbgFlag** to include these blocks in the leak detection process.
+By default, internal C run-time blocks (**`_CRT_BLOCK`**) aren't included in memory dump operations. The [`_CrtSetDbgFlag`](crtsetdbgflag.md) function can be used to turn on the **`_CRTDBG_CHECK_CRT_DF`** bit of **`_crtDbgFlag`** to include these blocks in the leak detection process.
 
-For more information about heap state functions and the **_CrtMemState** structure, see [Heap State Reporting Functions](/visualstudio/debugger/crt-debug-heap-details). For more information about how memory blocks are allocated, initialized, and managed in the debug version of the base heap, see [CRT Debug Heap Details](/visualstudio/debugger/crt-debug-heap-details).
+For more information about heap state functions and the **`_CrtMemState`** structure, see [Heap State Reporting Functions](/visualstudio/debugger/crt-debug-heap-details). For more information about how memory blocks are allocated, initialized, and managed in the debug version of the base heap, see [CRT Debug Heap Details](/visualstudio/debugger/crt-debug-heap-details).
 
 ## Requirements
 
 |Routine|Required header|
 |-------------|---------------------|
-|**_CrtDumpMemoryLeaks**|\<crtdbg.h>|
+|**`_CrtDumpMemoryLeaks`**|`<crtdbg.h>`|
 
 For more compatibility information, see [Compatibility](../../c-runtime-library/compatibility.md).
 
@@ -51,8 +50,8 @@ Debug versions of [C run-time libraries](../../c-runtime-library/crt-library-fea
 
 ## Example
 
-For a sample of how to use **_CrtDumpMemoryLeaks**, see [crt_dbg1](https://github.com/Microsoft/VCSamples/tree/master/VC2010Samples/crt/crt_dbg1).
+For a sample of how to use **`_CrtDumpMemoryLeaks`**, see [`crt_dbg1`](https://github.com/Microsoft/VCSamples/tree/master/VC2010Samples/crt/crt_dbg1).
 
 ## See also
 
-[Debug Routines](../../c-runtime-library/debug-routines.md)<br/>
+[Debug Routines](../../c-runtime-library/debug-routines.md)
@@ -8,9 +8,8 @@ api_type: ["DLLExport"]
 topic_type: ["apiref"]
 f1_keywords: ["fflush"]
 helpviewer_keywords: ["streams, flushing", "flushing", "fflush function"]
-ms.assetid: 8bbc753f-dc74-4e77-b563-74da2835e92b
 ---
-# fflush
+# `fflush`
 
 Flushes a stream.
 
@@ -24,35 +23,35 @@ int fflush(
 
 ### Parameters
 
-*stream*<br/>
-Pointer to **FILE** structure.
+*`stream`*\
+Pointer to **`FILE`** structure.
 
 ## Return Value
 
-**fflush** returns 0 if the buffer was successfully flushed. The value 0 is also returned in cases in which the specified stream has no buffer or is open for reading only. A return value of **EOF** indicates an error.
+**`fflush`** returns 0 if the buffer was successfully flushed. The value 0 is also returned in cases in which the specified stream has no buffer or is open for reading only. A return value of **`EOF`** indicates an error.
 
 > [!NOTE]
-> If **fflush** returns **EOF**, data may have been lost due to a write failure. When setting up a critical error handler, it is safest to turn buffering off with the **setvbuf** function or to use low-level I/O routines such as **_open**, **_close**, and **_write** instead of the stream I/O functions.
+> If **`fflush`** returns **`EOF`**, data may have been lost due to a write failure. When setting up a critical error handler, it is safest to turn buffering off with the **`setvbuf`** function or to use low-level I/O routines such as **`_open`**, **`_close`**, and **`_write`** instead of the stream I/O functions.
 
 ## Remarks
 
-The **fflush** function flushes the stream *stream*. If the stream was opened in write mode, or it was opened in update mode and the last operation was a write, the contents of the stream buffer are written to the underlying file or device and the buffer is discarded. If the stream was opened in read mode, or if the stream has no buffer, the call to **fflush** has no effect, and any buffer is retained. A call to **fflush** negates the effect of any prior call to **ungetc** for the stream. The stream remains open after the call.
+The **`fflush`** function flushes the stream *`stream`*. If the stream was opened in write mode, or it was opened in update mode and the last operation was a write, the contents of the stream buffer are written to the underlying file or device and the buffer is discarded. If the stream was opened in read mode, or if the stream has no buffer, the call to **`fflush`** has no effect, and any buffer is retained. A call to **`fflush`** negates the effect of any prior call to **`ungetc`** for the stream. The stream remains open after the call.
 
-If *stream* is **NULL**, the behavior is the same as a call to **fflush** on each open stream. All streams opened in write mode and all streams opened in update mode where the last operation was a write are flushed. The call has no effect on other streams.
+If *`stream`* is **`NULL`**, the behavior is the same as a call to **`fflush`** on each open stream. All streams opened in write mode and all streams opened in update mode where the last operation was a write are flushed. The call has no effect on other streams.
 
-Buffers are normally maintained by the operating system, which determines the optimal time to write the data automatically to disk: when a buffer is full, when a stream is closed, or when a program terminates normally without closing the stream. The commit-to-disk feature of the run-time library lets you ensure that critical data is written directly to disk rather than to the operating-system buffers. Without rewriting an existing program, you can enable this feature by linking the program's object files with COMMODE.OBJ. In the resulting executable file, calls to **_flushall** write the contents of all buffers to disk. Only **_flushall** and **fflush** are affected by COMMODE.OBJ.
+Buffers are normally maintained by the operating system, which determines the optimal time to write the data automatically to disk: when a buffer is full, when a stream is closed, or when a program terminates normally without closing the stream. The commit-to-disk feature of the run-time library lets you ensure that critical data is written directly to disk rather than to the operating-system buffers. Without rewriting an existing program, you can enable this feature by linking the program's object files with `COMMODE.OBJ`. In the resulting executable file, calls to **`_flushall`** write the contents of all buffers to disk. Only **`_flushall`** and **`fflush`** are affected by `COMMODE.OBJ`.
 
-For information about controlling the commit-to-disk feature, see [Stream I/O](../../c-runtime-library/stream-i-o.md), [fopen](fopen-wfopen.md), and [_fdopen](fdopen-wfdopen.md).
+For information about controlling the commit-to-disk feature, see [Stream I/O](../../c-runtime-library/stream-i-o.md), [`fopen`](fopen-wfopen.md), and [`_fdopen`](fdopen-wfdopen.md).
 
-This function locks the calling thread and is therefore thread-safe. For a non-locking version, see **_fflush_nolock**.
+This function locks the calling thread and is therefore thread-safe. For a non-locking version, see **`_fflush_nolock`**.
 
 By default, this function's global state is scoped to the application. To change this, see [Global state in the CRT](../global-state.md).
 
 ## Requirements
 
 |Function|Required header|
 |--------------|---------------------|
-|**fflush**|\<stdio.h>|
+|**`fflush`**|`<stdio.h>`|
 
 For additional compatibility information, see [Compatibility](../../c-runtime-library/compatibility.md).
 
@@ -108,7 +107,7 @@ User selected 5
 
 ## See also
 
-[Stream I/O](../../c-runtime-library/stream-i-o.md)<br/>
-[fclose, _fcloseall](fclose-fcloseall.md)<br/>
-[_flushall](flushall.md)<br/>
-[setvbuf](setvbuf.md)<br/>
+[Stream I/O](../../c-runtime-library/stream-i-o.md)\
+[`fclose`, `_fcloseall`](fclose-fcloseall.md)\
+[`_flushall`](flushall.md)\
+[`setvbuf`](setvbuf.md)
@@ -8,13 +8,12 @@ api_type: ["DLLExport"]
 topic_type: ["apiref"]
 f1_keywords: ["getch"]
 helpviewer_keywords: ["getch function"]
-ms.assetid: d3a0b744-d63c-4f71-960e-24e619dccd01
 ---
 # getch
 
-The Microsoft-specific function name `getch` is a deprecated alias for the [_getch](getch-getwch.md) function. By default, it generates [Compiler warning (level 3) C4996](../../error-messages/compiler-warnings/compiler-warning-level-3-c4996.md). The name is deprecated because it doesn't follow the Standard C rules for implementation-specific names. However, the function is still supported.
+The Microsoft-specific function name `getch` is a deprecated alias for the [`_getch`](getch-getwch.md) function. By default, it generates [Compiler warning (level 3) C4996](../../error-messages/compiler-warnings/compiler-warning-level-3-c4996.md). The name is deprecated because it doesn't follow the Standard C rules for implementation-specific names. However, the function is still supported.
 
-We recommend you use [_getch](getch-getwch.md) instead. Or, you can continue to use this function name, and disable the warning. For more information, see [Turn off the warning](../../error-messages/compiler-warnings/compiler-warning-level-3-c4996.md#turn-off-the-warning) and [POSIX function names](../../error-messages/compiler-warnings/compiler-warning-level-3-c4996.md#posix-function-names).
+We recommend you use [`_getch`](getch-getwch.md) instead. Or, you can continue to use this function name, and disable the warning. For more information, see [Turn off the warning](../../error-messages/compiler-warnings/compiler-warning-level-3-c4996.md#turn-off-the-warning) and [POSIX function names](../../error-messages/compiler-warnings/compiler-warning-level-3-c4996.md#posix-function-names).
 
 > [!IMPORTANT]
 > This API cannot be used in applications that execute in the Windows Runtime. For more information, see [CRT functions not supported in Universal Windows Platform apps](../../cppcx/crt-functions-not-supported-in-universal-windows-platform-apps.md).