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

* Update vcperf-commands.md (#4375)

* Update vcperf-commands.md

Update commands according to https://github.com/microsoft/vcperf#command-line-reference

* Update vcperf-commands.md

* Update with grammar fixes for i18n

---------

Co-authored-by: Colin Robertson <[email protected]>

* Update tutorial-import-stl-named-module.md (#4429)

* Update tutorial-import-stl-named-module.md

The Title of the document doesn't reveal that this procedure is only for a command line case.  Suggest altering the titles to reflect this and improve clarity for readers searching for module documentation.

* Update tutorial-import-stl-named-module.md

Changed the capitalization at Microsoft's request.

---------

Co-authored-by: huypub <[email protected]>
Co-authored-by: learn-build-service-prod[bot] <113403604+learn-build-service-prod[bot]@users.noreply.github.com>
Co-authored-by: Nelson Daniel Troncoso <[email protected]>
Co-authored-by: Colin Robertson <[email protected]>
Co-authored-by: Centurion Maximus <[email protected]>

Author: 5 people

docs/build-insights/reference/vcperf-commands.md

@@ -18,23 +18,23 @@ This article lists and describes the commands available in *`vcperf.exe`*, and h
 ## Commands to start and stop traces
 
 > [!IMPORTANT]
-> The following commands all require administrative privileges.
+> Unless you specify `/noadmin`, the following commands require administrative privileges.
 
 | Option           | Arguments and description |
 |------------------|---------------------------|
-| `/start`         | `[/nocpusampling]` `<sessionName>` |
-|                  | Tells *vcperf.exe* to start a trace under the given session name. There can only be one active session at a time on a given machine. <br/><br/> If the `/nocpusampling` option is specified, *vcperf.exe* doesn't collect CPU samples. It prevents the use of the CPU Usage (Sampled) view in Windows Performance Analyzer, but makes the collected traces smaller. <br/><br/> Once tracing is started, *vcperf.exe* returns immediately. Events are collected system-wide for all processes running on the machine. That means that you don't need to build your project from the same command prompt as the one you used to run *vcperf.exe*. For example, you can build your project from Visual Studio. |
-| `/stop`          | `<sessionName>` `<outputFile.etl>` |
-|                  | Stops the trace identified by the given session name. Runs a post-processing step on the trace to generate a file viewable in Windows Performance Analyzer (WPA). For the best viewing experience, use a version of WPA that includes the C++ Build Insights add-in. For more information, see [Get started with C++ Build Insights](../get-started-with-cpp-build-insights.md). The `<outputFile.etl>` parameter specifies where to save the output file. |
-| `/stopnoanalyze` | `<sessionName>` `<rawOutputFile.etl>` |
-|                  | Stops the trace identified by the given session name and writes the raw, unprocessed data in the specified output file. The resulting file isn't meant to be viewed in WPA. <br/><br/> The post-processing step involved in the `/stop` command can sometimes be lengthy. You can use the `/stopnoanalyze` command to delay this post-processing step. Use the `/analyze` command when you're ready to produce a file viewable in Windows Performance Analyzer. |
+| `/start`         | [`/noadmin`] [`/nocpusampling`] [`/level1` \| `/level2` \| `/level3`] `<sessionName>` |
+|                  | Starts a trace under the given session name. <br/><br/> The `/noadmin` option runs *vcperf.exe* without admin privileges, and it ignores the `/nocpusampling` option. When you run vcperf without admin privileges, there can be more than one active session on a given machine. <br/><br/> The `/nocpusampling` option specifies *vcperf.exe* doesn't collect CPU samples. It prevents the use of the CPU Usage (Sampled) view in Windows Performance Analyzer, but makes the collected traces smaller. <br/><br/> The `/level1`, `/level2`, or `/level3` options specify which MSVC events to collect, in increasing level of information. Level 3 includes all events. Level 2 includes all events except template instantiation events. Level 1 includes all events except template instantiation, function, and file events. If unspecified, `/level2` is selected by default. <br/><br/> Once *vcperf.exe* starts the trace, it returns immediately. The trace collects events system-wide for all processes running on the machine. That means that you don't need to build your project in the same command prompt window as the one you use to run *vcperf.exe*. For example, you can build your project in Visual Studio. |
+| `/stop`          | (1) [`/templates`] `<sessionName> <outputFile.etl>` <br/> (2) [`/templates`] `<sessionName> /timetrace <outputFile.json>` |
+|                  | Stops the trace identified by the given session name. Runs a post-processing step on the trace to generate a file specified by the `<outputFile>` parameter. <br/><br/> The `/templates` option includes template instantiation events in the file. <br/><br/> (1) Generates a file viewable in Windows Performance Analyzer (WPA). The output file requires a `.etl` extension.<br/>(2) Generates a file viewable in the Microsoft Edge trace viewer (`edge://tracing`). The output file requires a `.json` extension. |
+| `/stopnoanalyze` | `<sessionName> <rawOutputFile.etl>` |
+|                  | Stops the trace identified by the given session name and writes the raw, unprocessed data in the specified output file. The resulting file isn't meant for viewing in WPA. <br/><br/> The post-processing step involved in the `/stop` command can sometimes be lengthy. You can use the `/stopnoanalyze` command to delay this post-processing step. Use the `/analyze` command when you're ready to produce a file viewable in Windows Performance Analyzer or the Microsoft Edge trace viewer. |
 
 ## Miscellaneous commands
 
 | Option     | Arguments and description |
 |------------|---------------------------|
-| `/analyze` | `<rawInputFile.etl> <outputFile.etl>` |
-|            | Accepts a raw trace file produced by the `/stopnoanalyze` command. Runs a post-processing step on this trace to generate a file viewable in Windows Performance Analyzer. For the best viewing experience, use a version of WPA that includes the C++ Build Insights add-in. For more information, see [Get started with C++ Build Insights](../get-started-with-cpp-build-insights.md). |
+| `/analyze` | (1) [`/templates`] `<rawInputFile.etl> <outputFile.etl>` <br/>(2) [`/templates`] `<rawInputFile.etl> /timetrace <outputFile.json>` |
+|            | Accepts a raw trace file produced by the `/stopnoanalyze` command. Runs a post-processing step on this trace to generate the file specified by the `<outputFile>` parameter. <br/><br/> The `/templates` option includes template instantiation events in the file. <br/><br/> (1) Generates a file viewable in Windows Performance Analyzer (WPA). The output file requires a `.etl` extension. <br/><br/> (2) Generates a file viewable in the Microsoft Edge trace viewer (`edge://tracing`). The output file requires a `.json` extension. |
 
 ## See also
 

docs/cpp/tutorial-import-stl-named-module.md

@@ -1,13 +1,13 @@
 ---
-title: "Tutorial: Import the standard library (STL) using modules (C++)"
+title: "Tutorial: Import the standard library (STL) using modules from the command line (C++)"
 ms.date: 12/02/2022
 ms.topic: "tutorial"
 author: "tylermsft"
 ms.author: "twhitney"
 helpviewer_keywords: ["modules [C++]", "modules [C++]", "named modules [C++], import standard library (STL) using named modules"]
 description: Learn how to import the C++ standard library (STL) using modules
 ---
-# Tutorial: Import the C++ standard library using modules
+# Tutorial: Import the C++ standard library using modules from the Command Line
 
 Learn how to import the C++ standard library using C++ library modules. This is significantly faster to compile and more robust than using header files or header units or precompiled headers (PCH).
 
@@ -224,4 +224,4 @@ In this tutorial, you've imported the standard library using modules. Next, lear
 [Compare header units, modules, and precompiled headers](../build/compare-inclusion-methods.md)\
 [Overview of modules in C++](modules-cpp.md)\
 [A Tour of C++ Modules in Visual Studio](https://devblogs.microsoft.com/cppblog/a-tour-of-cpp-modules-in-visual-studio)\
-[Moving a project to C++ named Modules](https://devblogs.microsoft.com/cppblog/moving-a-project-to-cpp-named-modules)
+[Moving a project to C++ named Modules](https://devblogs.microsoft.com/cppblog/moving-a-project-to-cpp-named-modules)