Merge pull request #6031 from MicrosoftDocs/FromPublicMasterBranch

Confirm merge from FromPublicMasterBranch to main to sync with https://github.com/MicrosoftDocs/cpp-docs (branch main)

Author: Albertyang0

docs/assembler/masm/mmword.md

@@ -1,10 +1,9 @@
 ---
-description: "Learn more about: MMWORD"
 title: "MMWORD"
-ms.date: "12/17/2019"
+description: "Learn more about: MMWORD"
+ms.date: 12/17/2019
 f1_keywords: ["MMWORD"]
 helpviewer_keywords: ["MMWORD directive"]
-ms.assetid: b4c5a104-9078-4fb4-afc3-d1e63abe562a
 ---
 # MMWORD
 
@@ -32,6 +31,6 @@ While both instructions work on 64-bit operands, **QWORD** is the type for 64-bi
     movq     mm0, mmword ptr [ebx]
 ```
 
-## See Also
+## See also
 
 [MASM BNF Grammar](masm-bnf-grammar.md)

docs/assembler/masm/xmmword.md

@@ -1,10 +1,9 @@
 ---
-description: "Learn more about: XMMWORD"
 title: "XMMWORD"
-ms.date: "12/17/2019"
+description: "Learn more about: XMMWORD"
+ms.date: 12/17/2019
 f1_keywords: ["XMMWORD"]
 helpviewer_keywords: ["XMMWORD directive"]
-ms.assetid: 18026d32-5cab-403e-ad7e-382fb41aa9b8
 ---
 # XMMWORD
 
@@ -24,6 +23,6 @@ Used for 128-bit multimedia operands with MMX and SSE (XMM) instructions.
     movdqa   xmm0, xmmword ptr [ebx]
 ```
 
-## See Also
+## See also
 
 [MASM BNF Grammar](masm-bnf-grammar.md)

docs/build/reference/profile-performance-tools-profiler.md

@@ -1,6 +1,6 @@
 ---
-description: "Learn more about: /PROFILE (Performance Tools Profiler)"
 title: "/PROFILE (Performance Tools Profiler)"
+description: "Learn more about: /PROFILE (Performance Tools Profiler)"
 ms.date: 10/13/2021
 f1_keywords: ["VC.Project.VCLinkerTool.Profile"]
 helpviewer_keywords: ["-PROFILE linker option", "/PROFILE linker option"]
@@ -57,7 +57,7 @@ Because a **CMake** project doesn't have the usual **Property Pages** support, t
 
 1. Rebuild your solution.
 
-## See Also
+## See also
 
 [MSVC linker reference](linking.md)\
 [MSVC linker options](linker-options.md)

docs/c-runtime-library/crt-debugging-techniques.md

@@ -18,15 +18,15 @@ When you debug a program that uses the C run-time library, these debugging techn
 
 The C runtime (CRT) library provides extensive debugging support. To use one of the CRT debug libraries, you must link with [`/DEBUG`](/cpp/build/reference/debug-generate-debug-info) and compile with [`/MDd`, `/MTd`, or `/LDd`](../build/reference/md-mt-ld-use-run-time-library.md).
 
-The main definitions and macros for CRT debugging can be found in the`<crtdbg.h>` header file.
+The main definitions and macros for CRT debugging can be found in the `<crtdbg.h>` header file.
 
 The functions in the CRT debug libraries are compiled with debug information ([/Z7, /Zd, /Zi, /ZI (Debug Information Format)](../build/reference/z7-zi-zi-debug-information-format.md)) and without optimization. Some functions contain assertions to verify parameters that are passed to them, and source code is provided. With this source code, you can step into CRT functions to confirm that the functions are working as you expect and check for bad parameters or memory states. (Some CRT technology is proprietary and doesn't provide source code for exception handling, floating point, and a few other routines.)
 
 For more information on the various run-time libraries you can use, see [C Run-Time Libraries](./crt-library-features.md).
 
 ## Macros for reporting
 
-For debugging, you can use the `_RPTn` and `_RPTFn` macros, defined in`<crtdbg.h>`, to replace the use of `printf` statements. You don't need to enclose them in `#ifdef` directives, because they automatically disappear in your release build when `_DEBUG` isn't defined.
+For debugging, you can use the `_RPTn` and `_RPTFn` macros, defined in `<crtdbg.h>`, to replace the use of `printf` statements. You don't need to enclose them in `#ifdef` directives, because they automatically disappear in your release build when `_DEBUG` isn't defined.
 
 | Macro | Description |
 |---|---|
@@ -81,7 +81,7 @@ You can write several kinds of custom debug hook functions that allow you to ins
 
 ### Client block hook functions
 
-If you want to validate or report the contents of the data stored in `_CLIENT_BLOCK` blocks, you can write a function specifically for this purpose. The function that you write must have a prototype similar to the following, as defined in`<crtdbg.h>`:
+If you want to validate or report the contents of the data stored in `_CLIENT_BLOCK` blocks, you can write a function specifically for this purpose. The function that you write must have a prototype similar to the following, as defined in `<crtdbg.h>`:
 
 ```cpp
 void YourClientDump(void *, size_t)
@@ -91,7 +91,7 @@ In other words, your hook function should accept a `void` pointer to the beginni
 
 Once you've installed your hook function using [_CrtSetDumpClient](./reference/crtsetdumpclient.md), it will be called every time a `_CLIENT_BLOCK` block is dumped. You can then use [_CrtReportBlockType](./reference/crtreportblocktype.md) to get information on the type or subtype of dumped blocks.
 
-The pointer to your function that you pass to `_CrtSetDumpClient` is of type `_CRT_DUMP_CLIENT`, as defined in`<crtdbg.h>`:
+The pointer to your function that you pass to `_CrtSetDumpClient` is of type `_CRT_DUMP_CLIENT`, as defined in `<crtdbg.h>`:
 
 ```cpp
 typedef void (__cdecl *_CRT_DUMP_CLIENT)
@@ -113,7 +113,7 @@ int YourAllocHook(int nAllocType, void *pvData,
         const unsigned char * szFileName, int nLine )
 ```
 
-The pointer that you pass to [`_CrtSetAllocHook`](./reference/crtsetallochook.md) is of type `_CRT_ALLOC_HOOK`, as defined in`<crtdbg.h>`:
+The pointer that you pass to [`_CrtSetAllocHook`](./reference/crtsetallochook.md) is of type `_CRT_ALLOC_HOOK`, as defined in `<crtdbg.h>`:
 
 ```cpp
 typedef int (__cdecl * _CRT_ALLOC_HOOK)

docs/code-quality/c28112.md

@@ -35,7 +35,7 @@ InterlockedDecrement(&inter_var);
 InterlockedIncrement(&inter_var);
 ```
 
-## See Also
+## See also
 
 [InterlockedIncrement function (wdm.h)](/windows-hardware/drivers/ddi/wdm/nf-wdm-interlockedincrement)\
 [InterlockedDecrement function (wdm.h)](/windows-hardware/drivers/ddi/wdm/nf-wdm-interlockeddecrement)

docs/code-quality/c6504.md

@@ -1,10 +1,9 @@
 ---
-description: "Learn more about: Warning C6504"
 title: Warning C6504
+description: "Learn more about: Warning C6504"
 ms.date: 10/03/2022
 f1_keywords: ["C6504", "NULL_ON_NON_POINTER", "__WARNING_NULL_ON_NON_POINTER"]
 helpviewer_keywords: ["C6504"]
-ms.assetid: 6baeed46-e73d-4974-af16-7487c55b3473
 ---
 # Warning C6504
 
@@ -60,6 +59,6 @@ void g(Point& pt)
 }
 ```
 
-## See Also
+## See also
 
 [Annotation Properties](using-sal-annotations-to-reduce-c-cpp-code-defects.md)

docs/code-quality/using-sal-annotations-to-reduce-c-cpp-code-defects.md

@@ -1,13 +1,12 @@
 ---
-description: "Learn more about: Using SAL Annotations to Reduce C/C++ Code Defects"
 title: Using SAL Annotations to Reduce C/C++ Code Defects
+description: "Learn more about: Using SAL Annotations to Reduce C/C++ Code Defects"
 ms.date: 11/04/2016
 ms.topic: "concept-article"
 helpviewer_keywords:
   - "annotations"
   - "SAL annotations"
   - "code analysis, annotation"
-ms.assetid: a16e47d0-6f3e-4ed6-8883-459b2874e9a4
 ---
 # Using SAL Annotations to Reduce C/C++ Code Defects
 
@@ -47,6 +46,6 @@ The articles in this section of the documentation discuss aspects of SAL, provid
 
      Provides examples that show how to use SAL annotations. Also explains common pitfalls.
 
-## See Also
+## See also
 
 [SAL 2.0 Annotations for Windows Drivers](/windows-hardware/drivers/devtest/sal-2-annotations-for-windows-drivers)

docs/cpp/import-export-module.md

@@ -1,9 +1,9 @@
 ---
 title: "module, import, export"
+description: Use import and export declarations to access and to publish types and functions defined in the specified module.
 ms.date: 02/13/2025
 f1_keywords: ["module_cpp", "import_cpp", "export_cpp"]
 helpviewer_keywords: ["modules [C++]", "modules [C++], import", "modules [C++], export"]
-description: Use import and export declarations to access and to publish types and functions defined in the specified module.
 ---
 # `module`, `import`, `export`
 
@@ -109,7 +109,7 @@ import // Always an identifier, never a keyword
 
 **End Microsoft Specific**
 
-## See Also
+## See also
 
 [Overview of modules in C++](modules-cpp.md)\
 [Import the C++ standard library using modules](tutorial-import-stl-named-module.md)

docs/error-messages/compiler-errors-1/compiler-error-c2041.md

@@ -1,18 +1,21 @@
 ---
-description: "Learn more about: Compiler Error C2041"
 title: "Compiler Error C2041"
-ms.date: "11/04/2016"
+description: "Learn more about: Compiler Error C2041"
+ms.date: 11/04/2016
 f1_keywords: ["C2041"]
 helpviewer_keywords: ["C2041"]
-ms.assetid: c9a33bb1-f9cf-47d6-bd21-7d867a8c37d5
 ---
 # Compiler Error C2041
 
-illegal digit 'character' for base 'number'
+> illegal digit 'character' for base 'number'
+
+## Remarks
 
 The specified character is not a valid digit for the base (such as octal or hex).
 
-The following sample generates C2041:
+## Example
+
+The following example generates C2041:
 
 ```cpp
 // C2041.cpp

docs/error-messages/compiler-errors-1/compiler-error-c2042.md

@@ -1,18 +1,21 @@
 ---
-description: "Learn more about: Compiler Error C2042"
 title: "Compiler Error C2042"
-ms.date: "11/04/2016"
+description: "Learn more about: Compiler Error C2042"
+ms.date: 11/04/2016
 f1_keywords: ["C2042"]
 helpviewer_keywords: ["C2042"]
-ms.assetid: e111788f-41ce-405a-9824-a4c1c26059e6
 ---
 # Compiler Error C2042
 
-signed/unsigned keywords mutually exclusive
+> signed/unsigned keywords mutually exclusive
+
+## Remarks
 
 The keywords **`signed`** and **`unsigned`** are used in a single declaration.
 
-The following sample generates C2042:
+## Example
+
+The following example generates C2042:
 
 ```cpp
 // C2042.cpp