wsfulton
diff --git a/‎docs/build/reference/qpar-auto-parallelizer.md‎
Lines changed: 18 additions & 20 deletions b/‎docs/build/reference/qpar-auto-parallelizer.md‎
Lines changed: 18 additions & 20 deletions
diff --git a/‎docs/build/reference/stack-stack-allocations.md‎
Lines changed: 12 additions & 14 deletions b/‎docs/build/reference/stack-stack-allocations.md‎
Lines changed: 12 additions & 14 deletions
diff --git a/‎docs/build/reference/zm-specify-precompiled-header-memory-allocation-limit.md‎
Lines changed: 25 additions & 27 deletions b/‎docs/build/reference/zm-specify-precompiled-header-memory-allocation-limit.md‎
Lines changed: 25 additions & 27 deletions
diff --git a/‎docs/code-quality/clang-tidy.md‎
Lines changed: 5 additions & 5 deletions b/‎docs/code-quality/clang-tidy.md‎
Lines changed: 5 additions & 5 deletions
@@ -1,45 +1,43 @@
 ---
-description: "Learn more about: /Qpar (Auto-Parallelizer)"
-title: "/Qpar (Auto-Parallelizer)"
-ms.date: "11/04/2016"
+description: "Learn more about: /Qpar (Auto-parallelizer)"
+title: "/Qpar (Auto-parallelizer)"
+ms.date: 02/22/2022
 f1_keywords: ["VC.Project.VCCLCompilerTool.EnableParallelCodeGeneration"]
 ms.assetid: 33ecf49d-c0d5-4f34-bce3-84ff03f38918
 ---
-# /Qpar (Auto-Parallelizer)
+# `/Qpar` (Auto-parallelizer)
 
-Enables the [Auto-Parallelizer](../../parallel/auto-parallelization-and-auto-vectorization.md) feature of the compiler to automatically parallelize loops in your code.
+Enables the [Auto-parallelizer](../../parallel/auto-parallelization-and-auto-vectorization.md) feature of the compiler to automatically parallelize loops in your code.
 
 ## Syntax
 
-```
-/Qpar
-```
+> **`/Qpar`**
 
 ## Remarks
 
-When  the compiler automatically parallelizes loops in code, it spreads computation across multiple processor cores. A loop is parallelized only if the compiler determines that it is legal to do so and that parallelization would improve performance.
+When the compiler automatically parallelizes loops in code, it spreads computation across multiple processor cores. The compiler parallelizes a loop only if it determines that it's legal to do so and that parallelization would improve performance.
 
-The `#pragma loop()` directives are available to help the optimizer parallelize specific loops. For more information, see [loop](../../preprocessor/loop.md).
+The `#pragma loop()` directives are available to help the optimizer parallelize specific loops. For more information, see [`loop`](../../preprocessor/loop.md).
 
-For information about how to enable output messages for the auto-parallelizer, see [/Qpar-report (Auto-Parallelizer Reporting Level)](qpar-report-auto-parallelizer-reporting-level.md).
+For information about how to enable output messages for the auto-parallelizer, see [`/Qpar-report` (Auto-parallelizer reporting level)](qpar-report-auto-parallelizer-reporting-level.md).
 
-### To set the /Qpar compiler option in Visual Studio
+### To set the `/Qpar` compiler option in Visual Studio
 
 1. Open the project's **Property Pages** dialog box. For details, see [Set C++ compiler and build properties in Visual Studio](../working-with-project-properties.md).
 
-1. Select the **Configuration Properties** > **C/C++** > **Command Line** property page.
+1. Select the **Configuration Properties** > **C/C++** > **Code Generation** property page.
 
-1. In the **Additional Options** box, enter *`/Qpar`*.
+1. Modify the **Enable Parallel Code Generation** property. Choose **OK** or **Apply** to save your changes.
 
-### To set the /Qpar compiler option programmatically
+### To set the `/Qpar` compiler option programmatically
 
 - Use the code example in <xref:Microsoft.VisualStudio.VCProjectEngine.VCCLCompilerTool.AdditionalOptions%2A>.
 
 ## See also
 
-[/Q Options (Low-Level Operations)](q-options-low-level-operations.md)<br/>
-[/Qpar-report (Auto-Parallelizer Reporting Level)](qpar-report-auto-parallelizer-reporting-level.md)<br/>
-[MSVC Compiler Options](compiler-options.md)<br/>
-[MSVC Compiler Command-Line Syntax](compiler-command-line-syntax.md)<br/>
-[#pragma loop()](../../preprocessor/loop.md)<br/>
+[`/Q` options (Low-level operations)](q-options-low-level-operations.md)\
+[`/Qpar-report` (Auto-parallelizer reporting level)](qpar-report-auto-parallelizer-reporting-level.md)\
+[MSVC compiler options](compiler-options.md)\
+[MSVC compiler command-line syntax](compiler-command-line-syntax.md)\
+[`#pragma loop()`](../../preprocessor/loop.md)\
 [Native code vectorization in Visual Studio](/archive/blogs/nativeconcurrency/auto-vectorizer-in-visual-studio-2012-overview)
@@ -1,28 +1,26 @@
 ---
-description: "Learn more about: /STACK (Stack Allocations)"
-title: "/STACK (Stack Allocations)"
-ms.date: "11/04/2016"
+description: "Learn more about: /STACK (Stack allocations)"
+title: "/STACK (Stack allocations)"
+ms.date: 02/22/2022
 f1_keywords: ["VC.Project.VCLinkerTool.StackReserveSize", "VC.Project.VCLinkerTool.StackCommitSize", "/stack"]
 helpviewer_keywords: ["STACK linker option", "-STACK linker option", "memory allocation, stack", "/STACK linker option", "stack, setting size"]
 ms.assetid: 73283660-e4bd-47cc-b5ca-04c5d739034c
 ---
-# /STACK (Stack Allocations)
+# `/STACK` (Stack allocations)
 
-```
-/STACK:reserve[,commit]
-```
+> **`/STACK:`***`reserve`*[**`,`***`commit`*]
 
 ## Remarks
 
-The /STACK option sets the size of the stack in bytes. Use this option only when you build an .exe file.
+The **`/STACK`** linker option sets the size of the stack in bytes. Use this option only when you build an *`.exe`* file. The **`/STACK`** option is ignored when applied to *`.dll`* files.
 
-The `reserve` value specifies the total stack allocation in virtual memory. For ARM, x86 and x64 machines, the default stack size is 1 MB.
+The *`reserve`* value specifies the total stack allocation in virtual memory. For ARM64, x86, and x64 machines, the default stack size is 1 MB.
 
-`commit` is subject to interpretation by the operating system. In Windows WindowsRT it specifies the amount of physical memory to allocate at a time. Committed virtual memory causes space to be reserved in the paging file. A higher `commit` value saves time when the application needs more stack space, but increases the memory requirements and possibly the startup time. For ARM, x86 and x64 machines, the default commit value is 4 KB.
+The *`commit`* value is subject to interpretation by the operating system. In WindowsRT, it specifies the amount of physical memory to allocate at a time. Committed virtual memory causes space to be reserved in the paging file. A higher *`commit`* value saves time when the application needs more stack space, but increases the memory requirements and possibly the startup time. For ARM64, x86, and x64 machines, the default *`commit`* value is 4 KB.
 
-Specify the `reserve` and `commit` values in decimal or C-language notation.
+Specify the *`reserve`* and *`commit`* values in decimal or C-language hexadecimal notation (use a `0x` prefix).
 
-Another way to set the size of the stack is with the [STACKSIZE](stacksize.md) statement in a module-definition (.def) file. **STACKSIZE** overrides the Stack Allocations (/STACK) option if both are specified. You can change the stack size after the .exe file is built by using the [EDITBIN](editbin-reference.md) tool.
+Another way to set the size of the stack is with the [`STACKSIZE`](stacksize.md) statement in a module-definition (*`.def`*) file. **`STACKSIZE`** overrides the Stack Allocations (**`/STACK`**) option if both are specified. You can change the stack size after the *`.exe`* file is built by using the [`EDITBIN`](editbin-reference.md) tool.
 
 ### To set this linker option in the Visual Studio development environment
 
@@ -42,5 +40,5 @@ Another way to set the size of the stack is with the [STACKSIZE](stacksize.md) s
 
 ## See also
 
-[MSVC linker reference](linking.md)<br/>
-[MSVC Linker Options](linker-options.md)
+[MSVC linker reference](linking.md)\
+[MSVC linker options](linker-options.md)
@@ -1,61 +1,59 @@
 ---
-description: "Learn more about: /Zm (Specify Precompiled Header Memory Allocation Limit)"
-title: "/Zm (Specify Precompiled Header Memory Allocation Limit)"
-ms.date: "03/08/2019"
-f1_keywords: ["/zm"]
+description: "Learn more about: /Zm (Specify precompiled header memory allocation limit)"
+title: "/Zm (Specify precompiled header memory allocation limit)"
+ms.date: 02/22/2022
+f1_keywords: ["/Zm"]
 helpviewer_keywords: ["PCH files, memory allocation limit", "Zm compiler option [C++]", "/Zm compiler option [C++]", "precompiled header files, memory allocation limit", "Specify Precompiled Header Memory Allocation Limit compiler option", "cl.exe compiler, memory allocation limit", ".pch files, memory allocation limit", "memory allocation, Memory Allocation Limit compiler option", "-Zm compiler option [C++]"]
 ms.assetid: 94c77d5e-6672-46a7-92e0-3f69e277727d
 ---
-# /Zm (Specify Precompiled Header Memory Allocation Limit)
+# `/Zm` (Specify precompiled header memory allocation limit)
 
 Determines the amount of memory that the compiler allocates to construct precompiled headers.
 
 ## Syntax
 
-```
-/Zmfactor
-```
+> **`/Zm`***`factor`*
 
 ## Arguments
 
-*factor*<br/>
-A scaling factor that determines the amount of memory that the compiler uses to construct precompiled headers.
+*`factor`*<br/>
+A scaling factor percentage that determines the amount of memory that the compiler uses to construct precompiled headers.
 
-The *factor* argument is a percentage of the default size of a compiler-defined work buffer. The default value of *factor* is 100 (percent), but you can specify larger or smaller amounts.
+The *`factor`* argument is a percentage of the default size of a compiler-defined work buffer. The default value of *`factor`* is 100 (percent), but you can specify larger or smaller amounts.
 
 ## Remarks
 
-In versions before Visual Studio 2015, the C++ compiler used several discrete heaps, and each had a finite limit. Currently, the compiler dynamically grows the heaps as necessary up to a total heap size limit, and allows the precompiled header to comprise multiple address ranges. Consequently, the **/Zm** compiler option is rarely necessary.
+In versions before Visual Studio 2015, the C++ compiler used several discrete heaps, and each had a finite limit. Currently, the compiler dynamically grows the heaps as necessary up to a total heap size limit, and allows the precompiled header to comprise multiple address ranges. Now, the **`/Zm`** compiler option is rarely necessary.
 
-If the compiler runs out of heap space and emits the [C1060](../../error-messages/compiler-errors-1/fatal-error-c1060.md) error message when you use the **/Zm** compiler option, you might have reserved too much memory. Consider removing the **/Zm** option.
+If the compiler runs out of heap space and emits the [C1060](../../error-messages/compiler-errors-1/fatal-error-c1060.md) error message when you use the **`/Zm`** compiler option, you might have reserved too much memory. Consider removing the **`/Zm`** option.
 
-If the compiler emits the [C1076](../../error-messages/compiler-errors-1/fatal-error-c1076.md) error message, an accompanying [C3859](../../error-messages/compiler-errors-2/compiler-error-c3859.md) message specifies the *factor* argument to use when you recompile by using the **/Zm** compiler option. This message is only significant when a precompiled header uses `#pragma hdrstop`. In other cases, it is a spurious error caused by Windows virtual memory pressure issues, and the recommendation to use the **/Zm** option should be ignored. Instead, consider reducing the number of parallel processes when using the **/maxcpucount** option to MSBUILD.EXE in conjunction with the **/MP** option to CL.EXE. For more information, see [Precompiled Header (PCH) issues and recommendations](https://devblogs.microsoft.com/cppblog/precompiled-header-pch-issues-and-recommendations/).
+If the compiler emits the [C1076](../../error-messages/compiler-errors-1/fatal-error-c1076.md) error message, an accompanying [C3859](../../error-messages/compiler-errors-2/compiler-error-c3859.md) message specifies the *`factor`* argument to use when you recompile by using the **`/Zm`** compiler option. This message is only significant when a precompiled header uses `#pragma hdrstop`. In other cases, it's a spurious error caused by Windows virtual memory pressure issues, and the recommendation to use the **`/Zm`** option should be ignored. Instead, consider reducing the number of parallel processes when using the **`/maxcpucount`** option to MSBUILD.EXE together with the **`/MP`** option to CL.EXE. For more information, see [Precompiled Header (PCH) issues and recommendations](https://devblogs.microsoft.com/cppblog/precompiled-header-pch-issues-and-recommendations/).
 
-The following table shows how the *factor* argument affects the memory allocation limit if you assume the size of the default precompiled header buffer is 75 MB.
+The following table shows how the *`factor`* argument affects the memory allocation limit. In the table, we assume the size of the default precompiled header buffer is 75 MB.
 
-|Value of *factor*|Memory allocation limit|
-|-----------------------|-----------------------------|
-|10|7.5 MB|
-|100|75 MB|
-|200|150 MB|
-|1000|750 MB|
-|2000|1500 MB|
+| Value of *`factor`* | Memory allocation limit |
+|--|--|
+| 10 | 7.5 MB |
+| 100 | 75 MB |
+| 200 | 150 MB |
+| 1000 | 750 MB |
+| 2000 | 1500 MB |
 
-## Other Ways to Set the Memory Allocation Limit
+## Other ways to set the memory allocation limit
 
-### To set the /Zm compiler option in the Visual Studio development environment
+### To set the `/Zm` compiler option in the Visual Studio development environment
 
 1. Open the project's **Property Pages** dialog box. For details, see [Set C++ compiler and build properties in Visual Studio](../working-with-project-properties.md).
 
 1. Select the **Configuration Properties** > **C/C++** > **Command Line** property page.
 
 1. Enter the **/Zm** compiler option in the **Additional Options** box.
 
-### To set the /Zm compiler option programmatically
+### To set the `/Zm` compiler option programmatically
 
 - See <xref:Microsoft.VisualStudio.VCProjectEngine.VCCLCompilerTool.AdditionalOptions%2A>.
 
 ## See also
 
-[MSVC Compiler Options](compiler-options.md)<br/>
-[MSVC Compiler Command-Line Syntax](compiler-command-line-syntax.md)
+[MSVC compiler options](compiler-options.md)<br/>
+[MSVC compiler command-line syntax](compiler-command-line-syntax.md)
@@ -1,15 +1,15 @@
 ---
 title: Using Clang-Tidy in Visual Studio
 description: "How to use Clang-Tidy in Visual Studio for Microsoft C++ code analysis."
-ms.date: 02/19/2020
+ms.date: 02/22/2022
 ms.topic: "conceptual"
 f1_keywords: ["vs.codeanalysis.clangtidy"]
 ---
 # Using Clang-Tidy in Visual Studio
 
 ::: moniker range="<=msvc-150"
 
-Support for Clang-Tidy requires Visual Studio 2019 version 16.4 or later. To see the documentation for this version, set the Visual Studio **Version** selector control for this article to Visual Studio 2019. It's found at the top of the table of contents on this page.
+Support for Clang-Tidy requires Visual Studio 2019 version 16.4 or later. To see the documentation for this version, set the Visual Studio **Version** selector control for this article to Visual Studio 2019 or later. It's found at the top of the table of contents on this page.
 
 ::: moniker-end
 
@@ -45,11 +45,11 @@ Clang-Tidy runs result in warnings displayed in the Error List, and as in-editor
 
 ## Clang-Tidy configuration
 
-You can configure the checks that clang-tidy runs inside Visual Studio via the **Clang-Tidy Checks** option. This input is provided to the **`--checks`** argument of the tool. Any further configuration can be included in custom *`.clang-tidy`* files. For more information, see the [Clang-Tidy documentation on LLVM.org](https://clang.llvm.org/extra/clang-tidy/).
+By default, Clang-Tidy does not set any checks when enabled. To see the list of checks in the command-line version, run `clang-tidy -list-checks` in a developer command prompt. You can configure the checks that Clang-Tidy runs inside Visual Studio. In the project Property Pages dialog, open the **Configuration Properties** > **Code Analysis** > **Clang-Tidy** page. Enter checks to run in the **Clang-Tidy Checks** property. A good default set is `clang-analyzer-*`. This property value is provided to the **`--checks`** argument of the tool. Any further configuration can be included in custom *`.clang-tidy`* files. For more information, see the [Clang-Tidy documentation on LLVM.org](https://clang.llvm.org/extra/clang-tidy/).
 
 ## See also
 
-- [Clang/LLVM Support for MSBuild Projects](https://devblogs.microsoft.com/cppblog/clang-llvm-support-for-msbuild-projects/)
-- [Clang/LLVM Support for CMake Projects](https://devblogs.microsoft.com/cppblog/visual-studio-cmake-support-clang-llvm-cmake-3-14-vcpkg-and-performance-improvements/)
+- [Clang/LLVM support for MSBuild projects](https://devblogs.microsoft.com/cppblog/clang-llvm-support-for-msbuild-projects/)
+- [Clang/LLVM support for CMake projects](https://devblogs.microsoft.com/cppblog/visual-studio-cmake-support-clang-llvm-cmake-3-14-vcpkg-and-performance-improvements/)
 
 ::: moniker-end