RomandevJavaScript
diff --git a/‎docs/build/reference/scandependencies.md‎
Lines changed: 3 additions & 3 deletions b/‎docs/build/reference/scandependencies.md‎
Lines changed: 3 additions & 3 deletions
diff --git a/‎docs/overview/what-s-new-for-visual-cpp-in-visual-studio.md‎
Lines changed: 1 addition & 1 deletion b/‎docs/overview/what-s-new-for-visual-cpp-in-visual-studio.md‎
Lines changed: 1 addition & 1 deletion
@@ -9,13 +9,13 @@ 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 [`P1689R3 Format for describing dependencies of source files`](https://wg21.link/P1689r3).
+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).
 
 The **`/scanDependencies`** compiler option identifies which modules and header units need to be compiled before you can compile the project that uses them. For instance, it lists `import <library>;` or `import "library";` as a header unit dependency, and `import name;` as a module dependency. The intent is to provide this information in a common format consumable by build tools such as CMake.
 
 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 [`P1689R3`](https://wg21.link/P1689r3) schema, instead of the Microsoft-specific schema generated by **`/sourceDependencies-directives`**.
+- The output uses the [`P1689R4`](https://wg21.link/P1689r4) 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 [`P1689R3`](https://wg21.link/P1689r3#_format) section 6.
+For details on the format and schema used in the output JSON file, see [`P1689R4`](https://wg21.link/P1689r4#_format) section 6.
 
 ### Examples
 
 
@@ -59,7 +59,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 [P1689r3](https://wg21.link/P1689r3). 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 [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.
 
 ### Standard Library improvements