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