Merge pull request #5797 from MicrosoftDocs/main

2/21/2025 AM Publish

Author: Albertyang0

docs/assembler/masm/dot-nolistif.md

@@ -1,10 +1,9 @@
 ---
-description: "Learn more about: .NOLISTIF"
 title: ".NOLISTIF"
+description: "Learn more about: .NOLISTIF"
 ms.date: "12/16/2019"
 f1_keywords: [".NOLISTIF"]
 helpviewer_keywords: [".NOLISTIF directive"]
-ms.assetid: 9243af7a-7221-4531-bbc3-281b6b292bfd
 ---
 # .NOLISTIF
 
@@ -20,5 +19,5 @@ This is the default. Same as [.SFCOND](dot-sfcond.md).
 
 ## See also
 
-[Directives reference](directives-reference.md)
+[Directives reference](directives-reference.md)\
 [MASM BNF Grammar](masm-bnf-grammar.md)

docs/assembler/masm/option-avxencoding-masm.md

@@ -1,9 +1,9 @@
 ---
 title: "OPTION AVXENCODING"
+description: Describes how to select the preferred encoding of AVX instructions when more than one possibility will work
 ms.date: "10/06/2020"
 f1_keywords: ["avxencoding"]
 helpviewer_keywords: ["OPTION AVXENCODING directive"]
-description: Describes how to select the preferred encoding of AVX instructions when more than one possibility will work
 ---
 # OPTION AVXENCODING
 
@@ -47,7 +47,7 @@ The **`OPTION AVXENCODING`** directive is available in Visual Studio 2019 versio
 
 ### Example
 
-This example uses `VPDPBUSD` and `VPMADDWD` instructions to illustrate how the **`AVXENCODING`** option works. `VPDPBUSD` was first defined to be encoded only with `EVEX`, and was later extended with a VEX-encoded form for platforms without AVX-512 support, while `VPMADDWD` was AVX and extended to AVX-512. The listing output from assembling the example shows how changing the **`AVXENCODING`** mode affects the object code generated for each instruction. The prefix for each instruction ends at the '/".
+This example uses `VPDPBUSD` and `VPMADDWD` instructions to illustrate how the **`AVXENCODING`** option works. `VPDPBUSD` was first defined to be encoded only with `EVEX`, and was later extended with a VEX-encoded form for platforms without AVX-512 support, while `VPMADDWD` was AVX and extended to AVX-512. The listing output from assembling the example shows how changing the **`AVXENCODING`** mode affects the object code generated for each instruction. The prefix for each instruction ends at the "/".
 
 ```asm
  00000000  62 F2 6D 08/ 50        vpdpbusd xmm1, xmm2, xmm3

docs/assembler/masm/purge.md

@@ -1,10 +1,9 @@
 ---
-description: "Learn more about: PURGE"
 title: "PURGE"
+description: "Learn more about: PURGE"
 ms.date: "12/16/2019"
 f1_keywords: ["PURGE"]
 helpviewer_keywords: ["PURGE directive"]
-ms.assetid: 1e7ec2bf-f123-4ff9-97de-28b512ade2f9
 ---
 # PURGE
 
@@ -16,5 +15,5 @@ Deletes the specified macros from memory.
 
 ## See also
 
-[Directives reference](directives-reference.md)
+[Directives reference](directives-reference.md)\
 [MASM BNF Grammar](masm-bnf-grammar.md)

docs/assembler/masm/subttl.md

@@ -1,10 +1,9 @@
 ---
-description: "Learn more about: SUBTTL"
 title: "SUBTTL"
+description: "Learn more about: SUBTTL"
 ms.date: "12/16/2019"
 f1_keywords: ["SUBTTL"]
 helpviewer_keywords: ["SUBTTL directive"]
-ms.assetid: 927efadd-ec99-4de9-b64d-229bb2df3bf4
 ---
 # SUBTTL
 
@@ -16,5 +15,5 @@ See [SUBTITLE](subtitle.md).
 
 ## See also
 
-[Directives reference](directives-reference.md)
+[Directives reference](directives-reference.md)\
 [MASM BNF Grammar](masm-bnf-grammar.md)

docs/atl-mfc-shared/reference/codesnippet/CPP/cfiledialog-class_3.cpp

@@ -1,7 +1,7 @@
 void CMyClass::OnFileOpen()
 {
    // szFilters is a text string that includes two file name filters:
-   // "*.my" for "MyType Files" and "*.*' for "All Files."
+   // "*.my" for "MyType Files" and "*.*" for "All Files."
    TCHAR szFilters[]= _T("MyType Files (*.my)|*.my|All Files (*.*)|*.*||");
 
    // Create an Open dialog; the default file name extension is ".my".

docs/build-insights/reference/sdk/cpp-event-data-types/environment-variable.md

@@ -38,7 +38,7 @@ Along with the inherited members from its [SimpleEvent](simple-event.md) base cl
 
 ### Functions
 
-[Name](#name)
+[Name](#name)\
 [Value](#value)
 
 ## <a name="environment-variable"></a> EnvironmentVariable

docs/build-insights/reference/sdk/cpp-event-data-types/event-group.md

@@ -42,11 +42,11 @@ The activity type contained in the group.
 
 ### Functions
 
-[Back](#back)
-[begin](#begin)
-[end](#end)
-[Front](#front)
-[operator[]](#subscript-operator)
+[Back](#back)\
+[begin](#begin)\
+[end](#end)\
+[Front](#front)\
+[operator[]](#subscript-operator)\
 [Size](#size)
 
 ## <a name="back"></a> Back

docs/build-insights/reference/sdk/cpp-event-data-types/event-stack.md

@@ -37,8 +37,8 @@ public:
 
 ### Functions
 
-[Back](#back)
-[operator[]](#subscript-operator)
+[Back](#back)\
+[operator[]](#subscript-operator)\
 [Size](#size)
 
 ## <a name="back"></a> Back

docs/build-insights/reference/sdk/cpp-event-data-types/event.md

@@ -43,7 +43,7 @@ public:
 
 ### Functions
 
-[Data](#data)
+[Data](#data)\
 [EventId](#event-id)\
 [EventInstanceId](#event-instance-id)\
 [EventName](#event-name)\

docs/build-insights/reference/sdk/cpp-event-data-types/file-input.md

@@ -48,7 +48,7 @@ Along with the inherited members from its [SimpleEvent](simple-event.md) base cl
 
 ### Functions
 
-[Path](#path)
+[Path](#path)\
 [Type](#type)
 
 ## <a name="file-input"></a> FileInput

docs/build-insights/reference/sdk/cpp-event-data-types/file-output.md

@@ -48,7 +48,7 @@ Along with the inherited members from its [SimpleEvent](simple-event.md) base cl
 
 ### Functions
 
-[Path](#path)
+[Path](#path)\
 [Type](#type)
 
 ## <a name="file-output"></a> FileOutput

docs/build-insights/reference/sdk/cpp-event-data-types/force-inlinee.md

@@ -38,7 +38,7 @@ Along with the inherited members from its [SimpleEvent](simple-event.md) base cl
 
 ### Functions
 
-[Name](#name)
+[Name](#name)\
 [Size](#size)
 
 ## <a name="force-inlinee"></a> ForceInlinee

docs/build-insights/reference/sdk/cpp-event-data-types/invocation.md

@@ -50,10 +50,10 @@ Along with the inherited members from its [Activity](activity.md) base class, th
 
 ### Functions
 
-[ToolPath](#tool-path)
-[ToolVersion](#tool-version)
-[ToolVersionString](#tool-version-string)
-[Type](#type)
+[ToolPath](#tool-path)\
+[ToolVersion](#tool-version)\
+[ToolVersionString](#tool-version-string)\
+[Type](#type)\
 [WorkingDirectory](#working-directory)
 
 ## <a name="invocation"></a> Invocation

docs/build-insights/reference/sdk/cpp-event-data-types/raw-event.md

@@ -67,8 +67,8 @@ If you don't want to convert ticks yourself, the `RawEvent` class provides membe
 [CPUTime](#cpu-time)\
 [Data](#data)\
 [Duration](#duration)\
-[EventId](#event-id)
-[EventInstanceId](#event-instance-id)
+[EventId](#event-id)\
+[EventInstanceId](#event-instance-id)\
 [EventName](#event-name)\
 [EventWideName](#event-wide-name)\
 [ExclusiveCPUTicks](#exclusive-cpu-ticks)\

docs/build-insights/reference/sdk/cpp-event-data-types/symbol-name.md

@@ -38,7 +38,7 @@ Along with the inherited members from its [SimpleEvent](simple-event.md) base cl
 
 ### Functions
 
-[Key](#key)
+[Key](#key)\
 [Name](#name)
 
 ## <a name="key"></a> Key

docs/build-insights/reference/sdk/cpp-event-data-types/template-instantiation.md

@@ -48,8 +48,8 @@ Along with the inherited members from its [Activity](activity.md) base class, th
 
 ### Functions
 
-[Kind](#kind)
-[PrimaryTemplateSymbolKey](#primary-template-symbol-key)
+[Kind](#kind)\
+[PrimaryTemplateSymbolKey](#primary-template-symbol-key)\
 [SpecializationSymbolKey](#specialization-symbol-key)
 
 ## <a name="kind"></a> Kind

docs/build-insights/reference/sdk/cpp-event-data-types/trace-info.md

@@ -47,10 +47,10 @@ If you don't want to convert ticks yourself, the `TraceInfo` class provides a me
 
 ### Functions
 
-[Duration](#duration)
-[LogicalProcessorCount](#logical-processor-count)
-[StartTimestamp](#start-timestamp)
-[StopTimestamp](#stop-timestamp)
+[Duration](#duration)\
+[LogicalProcessorCount](#logical-processor-count)\
+[StartTimestamp](#start-timestamp)\
+[StopTimestamp](#stop-timestamp)\
 [TickFrequency](#tick-frequency)
 
 ## <a name="duration"></a> Duration

docs/build/creating-precompiled-header-files.md

@@ -346,7 +346,7 @@ int main( void )
 
 [Compare header units, modules, and precompiled headers](compare-inclusion-methods.md)\
 [C/C++ building reference](reference/c-cpp-building-reference.md)\
-[MSVC compiler options](reference/compiler-options.md)
+[MSVC compiler options](reference/compiler-options.md)\
 [Overview of modules in C++](../cpp/modules-cpp.md)\
 [Tutorial: Import the C++ standard library using modules](../cpp/tutorial-import-stl-named-module.md)\
 [Walkthrough: Build and import header units in your Visual C++ projects](walkthrough-header-units.md)\

docs/build/vscpp-step-0-installation.md

@@ -64,7 +64,7 @@ After the installer is installed, you can use it to customize your installation
 
 1. Find the workload you want in the **Installing Visual Studio** screen.
 
-   :::image type="content" source="../get-started/media/vs2022-installer-workloads.png" alt-text="Visual studio installer with the Desktop development with C++ workload selected." lightbox="../get-started/media/vs2022-installer-workloads.png":::
+   :::image type="content" source="../get-started/media/vs2022-installer-workloads.png" alt-text="Visual Studio installer with the Desktop development with C++ workload selected." lightbox="../get-started/media/vs2022-installer-workloads.png":::
 
    For core C and C++ support, choose the "Desktop development with C++" workload. It comes with the default core editor, which includes basic code editing support for over 20 languages, the ability to open and edit code from any folder without requiring a project, and integrated source code control.
 

docs/build/vscpp-step-1-create.md

@@ -81,7 +81,7 @@ Visual Studio now knows to build your project to run in a console window. Next,
 
    ![View of the process to add a source file for HelloWorld.cpp.](media/vscpp-add-new-item.gif "Add a source file for HelloWorld.cpp")
 
-Visual studio creates a new, empty source code file and opens it in an editor window, ready to enter your source code.
+Visual Studio creates a new, empty source code file and opens it in an editor window, ready to enter your source code.
 
 [I ran into a problem.](#add-a-source-code-file-issues)
 

docs/c-language/c-primary-expressions.md

@@ -23,5 +23,5 @@ Primary expressions are the building blocks of more complex expressions. They ma
 
 ## See also
 
-[Generic selection](generic-selection.md)
+[Generic selection](generic-selection.md)\
 [Operands and Expressions](../c-language/operands-and-expressions.md)

docs/c-language/static-assert-c.md

@@ -78,5 +78,5 @@ Windows SDK 10.0.20348.0 (version 2104) or later. For more information on instal
 ## See also
 
 [`_STATIC_ASSERT` Macro](../c-runtime-library/reference/static-assert-macro.md)\
-[`assert` macro and `_assert` and `_wassert` functions](../c-runtime-library/reference/assert-macro-assert-wassert.md)
+[`assert` macro and `_assert` and `_wassert` functions](../c-runtime-library/reference/assert-macro-assert-wassert.md)\
 [`/std` (Specify language standard version)](../build/reference/std-specify-language-standard-version.md)

docs/c-runtime-library/is-isw-routines.md

@@ -1,6 +1,6 @@
 ---
-description: "Learn more about: is, isw Routines"
 title: "is, isw Routines"
+description: "Learn more about: is, isw Routines"
 ms.date: 01/11/2022
 helpviewer_keywords: ["is routines", "isw routines"]
 ---
@@ -15,7 +15,7 @@ helpviewer_keywords: ["is routines", "isw routines"]
       [`iscntrl`, `iswcntrl`, `_iscntrl_l`, `_iswcntrl_l`](./reference/iscntrl-iswcntrl-iscntrl-l-iswcntrl-l.md)\
       [`iscsym`, `iscsymf`, `__iscsym`, `__iswcsym`, `__iscsymf`, `__iswcsymf`, `_iscsym_l`, `_iswcsym_l`, `_iscsymf_l`, `_iswcsymf_l`](./reference/iscsym-functions.md)\
       [`_isctype`, `iswctype`, `_isctype_l`, `_iswctype_l`](./reference/isctype-iswctype-isctype-l-iswctype-l.md)\
-      [`isdigit`, `iswdigit`, `_isdigit_l`, `_iswdigit_l`](./reference/isdigit-iswdigit-isdigit-l-iswdigit-l.md)
+      [`isdigit`, `iswdigit`, `_isdigit_l`, `_iswdigit_l`](./reference/isdigit-iswdigit-isdigit-l-iswdigit-l.md)\
       [`isgraph`, `iswgraph`, `_isgraph_l`, `_iswgraph_l`](./reference/isgraph-iswgraph-isgraph-l-iswgraph-l.md)\
       [`isleadbyte`, `_isleadbyte_l`](./reference/isleadbyte-isleadbyte-l.md)\
       [`islower`, `iswlower`, `_islower_l`, `_iswlower_l`](./reference/islower-iswlower-islower-l-iswlower-l.md)\

docs/c-runtime-library/reference/exp2-exp2f-exp2l.md

@@ -8,7 +8,6 @@ api_type: ["DLLExport"]
 topic_type: ["apiref"]
 f1_keywords: ["exp2", "math/exp2", "exp2f", "math/exp2f", "exp2l", "math/exp2l"]
 helpviewer_keywords: ["exp2 function", "exp2f function", "exp2l function"]
-ms.assetid: 526e3e10-201a-4610-a886-533f44ece344
 ---
 # `exp2`, `exp2f`, `exp2l`
 
@@ -79,5 +78,5 @@ For more compatibility information, see [Compatibility](../compatibility.md).
 ## See also
 
 [Alphabetical function reference](crt-alphabetical-function-reference.md)\
-[`exp`, `expf`, `expl`](exp-expf.md)
+[`exp`, `expf`, `expl`](exp-expf.md)\
 [`log2`, `log2f`, `log2l`](log2-log2f-log2l.md)

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

@@ -1,14 +1,13 @@
 ---
-description: "Learn more about: longjmp"
 title: "longjmp"
+description: "Learn more about: longjmp"
 ms.date: "1/14/2021"
 api_name: ["longjmp"]
 api_location: ["msvcrt.dll", "msvcr80.dll", "msvcr90.dll", "msvcr100.dll", "msvcr100_clr0400.dll", "msvcr110.dll", "msvcr110_clr0400.dll", "msvcr120.dll", "msvcr120_clr0400.dll", "ucrtbase.dll", "ntoskrnl.exe"]
 api_type: ["DLLExport"]
 topic_type: ["apiref"]
 f1_keywords: ["longjmp"]
 helpviewer_keywords: ["restoring stack environment and execution locale", "longjmp function"]
-ms.assetid: 0e13670a-5130-45c1-ad69-6862505b7a2f
 ---
 # `longjmp`
 
@@ -75,5 +74,5 @@ See the example for [`_fpreset`](fpreset.md).
 
 ## See also
 
-[Process and environment control](../process-and-environment-control.md)
+[Process and environment control](../process-and-environment-control.md)\
 [`setjmp`](setjmp.md)

docs/c-runtime-library/vprintf-functions.md

@@ -1,9 +1,8 @@
 ---
-description: "Learn more about: vprintf Functions"
 title: "vprintf Functions"
+description: "Learn more about: vprintf Functions"
 ms.date: "11/04/2016"
 helpviewer_keywords: ["vprintf functions", "formatted text [C++]"]
-ms.assetid: 02ac7c51-eab1-4bf0-bf4c-77065e3fa744
 ---
 # `vprintf` functions
 
@@ -17,7 +16,7 @@ Each of the `vprintf` functions takes a pointer to an argument list, then format
 [`_vprintf_p`, `_vprintf_p_l`, `_vwprintf_p`, `_vwprintf_p_l`](./reference/vprintf-p-vprintf-p-l-vwprintf-p-vwprintf-p-l.md)\
 [`vprintf_s`, `_vprintf_s_l`, `vwprintf_s`, `_vwprintf_s_l`](./reference/vprintf-s-vprintf-s-l-vwprintf-s-vwprintf-s-l.md)\
 [`_vscprintf`, `_vscprintf_l`, `_vscwprintf`, `_vscwprintf_l`](./reference/vscprintf-vscprintf-l-vscwprintf-vscwprintf-l.md)\
-[`_vsnprintf`, `_vsnwprintf`](./reference/vsnprintf-vsnprintf-vsnprintf-l-vsnwprintf-vsnwprintf-l.md)
+[`_vsnprintf`, `_vsnwprintf`](./reference/vsnprintf-vsnprintf-vsnprintf-l-vsnwprintf-vsnwprintf-l.md)\
 [`vsprintf`, `vswprintf`](./reference/vsprintf-vsprintf-l-vswprintf-vswprintf-l-vswprintf-l.md)\
 [`_vsprintf_p`, `_vsprintf_p_l`, `_vswprintf_p`, `_vswprintf_p_l`](./reference/vsprintf-p-vsprintf-p-l-vswprintf-p-vswprintf-p-l.md)\
 [`vsprintf_s`, `_vsprintf_s_l`, `vswprintf_s`, `_vswprintf_s_l`](./reference/vsprintf-s-vsprintf-s-l-vswprintf-s-vswprintf-s-l.md)

docs/code-quality/build-reliable-secure-programs.md

@@ -182,7 +182,7 @@ Remove the now-invalidated secrets from your source code, and replace them with
 
 **Azure DevOps (AzDO)**
 
-AzDO users can scan their code through GitHub Advanced Security for Azure DevOps (GHAzDO). GHAzDO also allows users to prevent secret exposures by enabling Push Protection on their repositories, catching potential exposures before they're ever leaked. For more information on how to detect hardcoded secrets in code in Azure DevOps, see *Secret Scanning for Github Advanced Security for Azure DevOps* in each of the following links:
+AzDO users can scan their code through GitHub Advanced Security for Azure DevOps (GHAzDO). GHAzDO also allows users to prevent secret exposures by enabling Push Protection on their repositories, catching potential exposures before they're ever leaked. For more information on how to detect hardcoded secrets in code in Azure DevOps, see *Secret Scanning for GitHub Advanced Security for Azure DevOps* in each of the following links:
 
 - [GitHub advanced security for Azure DevOps](https://azure.microsoft.com/products/devops/github-advanced-security)
 - [Secret Scanning for GitHub Advanced Security for Azure DevOps](/azure/devops/repos/security/github-advanced-security-secret-scanning)