Merge branch 'main' of https://github.com/MicrosoftDocs/cpp-docs-pr into linkage-ai

Author: TylerMSFT

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

@@ -1,6 +1,6 @@
 ---
-description: Learn more about the alternatives for the OPTION LANGUAGE directive
 title: "OPTION LANGUAGE"
+description: "Learn more about the alternatives for the OPTION LANGUAGE directive"
 ms.date: 09/21/2021
 f1_keywords: ["language"]
 helpviewer_keywords: ["OPTION LANGUAGE directive"]
@@ -20,11 +20,11 @@ Available languages include:
 :::row:::
    :::column span="":::
       **`C`**\
-      **`SYSCALL`**\
+      **`SYSCALL`**
    :::column-end:::
    :::column span="":::
       **`STDCALL`**\
-      **`PASCAL`**\
+      **`PASCAL`**
    :::column-end:::
    :::column span="":::
       **`FORTRAN`**\

docs/build-insights/index.yml

@@ -17,7 +17,7 @@ landingContent:
 # Cards and links should be based on top customer tasks or top subjects
 # Start card title with a verb
   # Card (optional)
-  - title: Learn how your build performs 
+  - title: Learn how your build performs
     linkLists:
       - linkListType: overview
         links:

docs/build/arm64-exception-handling.md

@@ -1,6 +1,6 @@
 ---
 title: "ARM64 exception handling"
-description: Describes the exception handling conventions and data used by windows on ARM64.
+description: "Describes the exception handling conventions and data used by windows on ARM64."
 ms.date: 01/13/2023
 ---
 # ARM64 exception handling
@@ -287,7 +287,7 @@ The unwind codes are encoded according to the table below. All unwind codes are
 |--|--|
 | `alloc_s` | 000xxxxx: allocate small stack with size \< 512 (2^5 * 16). |
 | `save_r19r20_x` | 001zzzzz: save `<x19,x20>` pair at `[sp-#Z*8]!`, pre-indexed offset >= -248 |
-| `save_fplr` | 01zzzzzz: save `<x29,lr>` pair at `[sp+#Z*8]`,  offset \<= 504. |
+| `save_fplr` | 01zzzzzz: save `<x29,lr>` pair at `[sp+#Z*8]`, offset \<= 504. |
 | `save_fplr_x` | 10zzzzzz: save `<x29,lr>` pair at `[sp-(#Z+1)*8]!`, pre-indexed offset >= -512 |
 | `alloc_m` | 11000xxx'xxxxxxxx: allocate large stack with size \< 32K (2^11 * 16). |
 | `save_regp` | 110010xx'xxzzzzzz: save `x(19+#X)` pair at `[sp+#Z*8]`, offset \<= 504 |

docs/build/cmake-predefined-configuration-reference.md

@@ -1,6 +1,6 @@
 ---
-description: "Learn more about: CMake predefined build configurations"
 title: "CMake predefined configuration reference"
+description: "Learn more about: CMake predefined build configurations"
 ms.description: "Visual Studio provides several predefined build configurations for CMake projects on Linux, Windows, ARM, and IoT."
 ms.date: 08/03/2021
 helpviewer_keywords: ["CMake redefined configurations"]
@@ -30,7 +30,7 @@ In a CMake project, build configurations are stored in a *`CMakeSettings.json`*
 
 When you choose a configuration, it's added to the *`CMakeSettings.json`* file in the project's root folder. You can then use it to build your project. For information about the configuration properties, see [CMakeSettings reference](cmakesettings-reference.md).
 
-## Linux predefined build configurations:
+## Linux predefined build configurations
 
 ```json
 {

docs/build/cmake-projects-in-visual-studio.md

@@ -3,7 +3,7 @@ title: "CMake projects in Visual Studio"
 description: "Learn how to create and build C++ projects using CMake in Visual Studio."
 ms.date: 03/18/2025
 ms.topic: concept-article
-f1_keywords: ["VS.ToolsOptionsPages.CMake.General", "VS.ToolsOptionsPages.CMake.LanguageServices"] 
+f1_keywords: ["VS.ToolsOptionsPages.CMake.General", "VS.ToolsOptionsPages.CMake.LanguageServices"]
 ms.custom: sfi-image-nochange
 ---
 

docs/build/image.png

@@ -17,7 +17,7 @@ To create the file, right-click on an executable file in **Solution Explorer** a
 | `args` | array | Specifies the command-line arguments passed to the launched program. |
 | `buildConfigurations` | array | A key-value pair that specifies the name of the build mode to apply the configurations. For example, `Debug` or `Release` and the configurations to use according to the selected build mode. |
 | `currentDir` | string | Specifies the full directory path to the Build Target. The directory is detected automatically unless this parameter is set. |
-| `cwd` | string | Full path to the directory on the remote system where the program will run. Defaults to `"${debugInfo.defaultWorkingDirectory}"` |
+| `cwd` | string | Full path to the directory on the remote system where the program will run. Defaults to `"${debugInfo.defaultWorkingDirectory}"`. |
 | `debugType` | string | Specifies the debugging mode according to the type of code (native, managed, or mixed). The mode is automatically detected unless this parameter is set. Allowed values: `"native"`, `"managed"`, `"mixed"`. |
 | `env` | array | Specifies a key-value list of custom environment variables. For example: `env:{"myEnv":"myVal"}`. |
 | `inheritEnvironments` | array | Specifies a set of environment variables inherited from multiple sources. You can define some variables in files like *`CMakeSettings.json`* or *`CppProperties.json`* and make them available to debug context.  **Visual Studio 16.4:** Specify environment variables on a per-target basis using the `env.VARIABLE_NAME` syntax. To unset a variable, set it to `"null"`. |
@@ -27,9 +27,9 @@ To create the file, right-click on an executable file in **Solution Explorer** a
 | `program` | string | The debug command to execute. Defaults to `"${debugInfo.fullTargetPath}"`. |
 | `project` | string | Specifies the relative path to the project file. Normally, you don't need to change this value when debugging a CMake project. |
 | `projectTarget` | string | Specifies the optional target invoked when building `project`. The target must match the name in the **Startup Item** dropdown. |
-| `stopOnEntry` | boolean | Specifies whether to break a soon as the process is launched and the debugger attaches. The default value for this parameter is **`false`**. |
+| `stopOnEntry` | boolean | Specifies whether to break as soon as the process is launched and the debugger attaches. The default value for this parameter is **`false`**. |
 | `remoteMachine` | string | Specifies the name of the remote machine where the program is launched. |
-| `type` | string | Specifies whether the project is a `dll` or `exe` Defaults to .exe |
+| `type` | string | Specifies whether the project is a `dll` or `exe`. Defaults to `"exe"`. |
 
 ## C++ Linux properties
 
@@ -64,7 +64,7 @@ The following macros provide information about the debugging environment. They'r
 
 | Macro | Description | Example |
 |--|--|--|
-| `addressSanitizerRuntimeFlags` | Runtime flags used to customize behavior of the address sanitizer. Used to set the environment variable `"ASAN_OPTIONS"`. | `"env": {"ASAN_OPTIONS": "${addressSanitizerRuntimeFlags}:anotherFlag=true"`} |
+| `addressSanitizerRuntimeFlags` | Runtime flags used to customize behavior of the address sanitizer. Used to set the environment variable `"ASAN_OPTIONS"`. | `"env": {"ASAN_OPTIONS": "${addressSanitizerRuntimeFlags}:anotherFlag=true"}` |
 | `defaultWorkingDirectory` | Set to the directory part of `"fullTargetPath"`. If the CMake variable `VS_DEBUGGER_WORKING_DIRECTORY` is defined, then `defaultWorkingDirectory` is set to that value, instead. | `"cwd":"${debugInfo.defaultWorkingDirectory}"` |
 | `fullTargetPath` | The full path to the binary being debugged. | `"program": "${debugInfo.fullTargetPath}"` |
 | `linuxNatvisPath` | The full windows path to the VS linux `.natvis` file. Usually appears as the value `"visualizerFile"`. | |
@@ -98,7 +98,7 @@ The pipeTransport example below shows how to use some of the `debugInfo` macros
         "/c",
         "${debuggerCommand}"
     ]
-    }
+}
 ```
 
 ## <a name="remote_deploy_debug"></a> C++ Windows remote debug and deploy properties
@@ -109,8 +109,8 @@ Used when debugging and deploying an app on a remote machine.
 |--|--|--|
 | `cwd` | string | The working directory of the target on the remote machine. When using CMake, the macro `${debugInfo.defaultWorkingDirectory}` can be used as the value of this field. The default value is the directory of the debug program/command. |
 | `deploy` | string | Specifies extra files or directories to deploy. For example:<br> `"deploy": {"sourcePath":"<Full path to source file/directory on host machine>", "targetPath":"<Full destination path to file/directory on target machine>"}` |
-| `deployDirectory` | string | The location on the remote machine where project outputs are automatically deployed to. Defaults to "`C:\Windows Default Deploy Directory\<name of app>` |
-| `deployDebugRuntimeLibraries` | string | Specifies whether to deploy the debug runtime libraries for the active platform. Defaults to `"true"` if the active configurationType is `"Debug"` |
+| `deployDirectory` | string | The location on the remote machine where project outputs are automatically deployed to. Defaults to `"C:\Windows Default Deploy Directory\<name of app>"`. |
+| `deployDebugRuntimeLibraries` | string | Specifies whether to deploy the debug runtime libraries for the active platform. Defaults to `"true"` if the active configurationType is `"Debug"`. |
 | `deployRuntimeLibraries` | string | Specifies whether to deploy the runtime libraries for the active platform. Defaults to `"true"` if the active configurationType is `"MinSizeRel"`, `"RelWithDebInfo"`, or `"Release"`. |
 | `disableDeploy` | boolean | Specifies whether files should be deployed. |
 | `remoteMachineName` | string | Specifies the name of the remote ARM64 Windows machine where the program is launched. May be the server name or the remote machine's IP address. |