Merge pull request #4556 from MicrosoftDocs/main

10/3 AM Publishing

Author: v-alje

docs/build/reference/scandependencies.md

@@ -9,7 +9,7 @@ helpviewer_keywords: ["/scanDependencies compiler option", "/scanDependencies"]
 ---
 # `/scanDependencies` (List module dependencies in standard form)
 
-This compiler option generates a JSON file that lists module and header-unit dependencies according to C++ Standard proposal [`P1689R4 Format for describing dependencies of source files`](https://wg21.link/P1689r4).
+This compiler option generates a JSON file that lists module and header-unit dependencies according to C++ Standard proposal [`P1689R5 Format for describing dependencies of source files`](https://wg21.link/P1689r5).
 
 ## Syntax
 
@@ -34,7 +34,7 @@ The **`/scanDependencies`** compiler option identifies which dependencies, modul
 
 This command-line option is similar to [`/sourceDependencies:directives`](sourcedependencies-directives.md) and [`/sourceDependencies`](sourcedependencies.md), but differs in the following ways:
 
-- The output uses the [`P1689R4`](https://wg21.link/P1689r4) schema, instead of the Microsoft-specific schema generated by **`/sourceDependencies:directives`**.
+- The output uses the [`P1689R5`](https://wg21.link/P1689r5) schema, instead of the Microsoft-specific schema generated by **`/sourceDependencies:directives`**.
 - Unlike **`/sourceDependencies`**, the compiler doesn't produce compiled output. Instead, the files are scanned for module directives. No compiled code, modules, or header units are produced.
 - The output JSON file doesn't list imported modules and imported header units (*`.ifc`* files) because this option only scans the project files. There are no built modules or header units to list.
 - Only directly imported modules or header units are listed. It doesn't list the dependencies of the imported modules or header units themselves.
@@ -49,7 +49,7 @@ When a non-fatal compiler error occurs, the dependency information still gets wr
 
 All file paths appear as absolute paths in the output.
 
-For details on the format and schema used in the output JSON file, see [`P1689R4`](https://wg21.link/P1689r4#_format) section 6.
+For details on the format and schema used in the output JSON file, see [`P1689R5`](https://wg21.link/P1689r5#_format) section 6.
 
 ### Examples
 

docs/build/walkthrough-header-units.md

@@ -156,4 +156,4 @@ Enabling the new preprocessor affects the processing of variadic macros. For mor
 [`/headerUnit`](./reference/headerunit.md)\
 [`header-units.json`](./reference/header-unit-json-reference.md)\
 [Overview of modules in C++](../cpp/modules-cpp.md)\
-[Walkthrough: Import STL libraries as header units](walkthrough-import-stl-header-units.md#approach1)
+[Walkthrough: Import STL libraries as header units](walkthrough-import-stl-header-units.md#approach1)

docs/overview/what-s-new-for-visual-cpp-in-visual-studio.md

@@ -57,15 +57,15 @@ For a summary of new features and bug fixes in Visual Studio in version 17.2, se
   - We've added thread awareness for device targets to the call stack window.
   - Users can now select a pin icon next to peripherals, registers, or fields to pin them the top of the Peripheral View.
 
-- We've added implementations of the remaining C++20 defect reports (also known as *backports*). All C++20 features are now available under the **`/std:c++20 `** option. For more information about the implemented backports, see the [C++20 Defect Reports project](https://github.com/microsoft/STL/projects/9) in the Microsoft/STL GitHub repository and the [MSVC's STL Completes `/std:c++20`](https://devblogs.microsoft.com/cppblog/msvcs-stl-completes-stdc20/) blog post.
+- We've added implementations of the remaining C++20 defect reports (also known as *backports*). All C++20 features are now available under the **`/std:c++20`** option. For more information about the implemented backports, see the [C++20 Defect Reports project](https://github.com/microsoft/STL/projects/9) in the Microsoft/STL GitHub repository and the [MSVC's STL Completes `/std:c++20`](https://devblogs.microsoft.com/cppblog/msvcs-stl-completes-stdc20/) blog post.
 
 - We added various C++23 Library features, available under the **`/std:c++latest`** option. For more information about the new features, see the [STL Repo changelog](https://github.com/microsoft/STL/wiki/Changelog).
 
 - Improved performance of the initial C++ indexing by up to 20%, depending on the depth of the include graph.
 
 ## What's new for C++ in Visual Studio version 17.1
 
-For a summary of new features and bug fixes in Visual Studio in version `7.`, see [Visual Studio 2022 version 17.1 Release Notes](/visualstudio/releases/2022/release-notes-v17.1).
+For a summary of new features and bug fixes in Visual Studio in version 17.1, see [Visual Studio 2022 version 17.1 Release Notes](/visualstudio/releases/2022/release-notes-v17.1).
 
 - A new **Configure Preset** template has been added to configure and build CMake projects on a remote macOS system with *`CMakePresets.json`*. You can also launch CMake targets on a remote macOS system, and then debug remotely in the Visual Studio debugger backed by GDB or LLDB.
 
@@ -113,7 +113,7 @@ In Visual Studio 2022, when you start your app in the debugger, you can use the
 
 - The Project menu in CMake projects has been streamlined and exposes options to "Delete Cache and Reconfigure" and "View Cache".
 
-- Implemented the **`/scanDependencies`** compiler option to list C++20 module dependencies for CMake projects, as described in [P1689R4](https://wg21.link/P1689r4). It's a step towards support for building modules-based projects with CMake and we're working on completing this support in later releases.
+- Implemented the **`/scanDependencies`** compiler option to list C++20 module dependencies for CMake projects, as described in [P1689R5](https://wg21.link/P1689r5). It's a step towards support for building modules-based projects with CMake and we're working on completing this support in later releases.
 
 ### Standard Library improvements