review edits

Author: TylerMSFT

docs/build/reference/experimental-module.md

@@ -1,23 +1,27 @@
 ---
 title: "/experimental:module (Enable module support)"
 description: "Use the /experimental:module compiler option to enable experimental compiler support for named modules."
-ms.date: 01/27/2022
+ms.date: 02/12/2025
 f1_keywords: ["module", "/experimental:module"]
 helpviewer_keywords: ["module", "/experimental:module", "Enable module support"]
 ---
 # `/experimental:module` (Enable experimental module support)
 
-Enables experimental compiler support for C++ Standard modules. This option is obsolete for C++20 standard modules in Visual Studio version 16.11 and later. This switch is only used (along with [`/std:c++latest`](std-specify-language-standard-version.md)) if you are still using the older experimental Standard library modules. We recommend that you use the new Standard Library modules provided by Microsoft without using this switch.
+Enables experimental compiler support for C++ Standard modules. This option is obsolete for C++20 standard modules in Visual Studio 2019 version 16.11 and later. This switch is only used (along with [`/std:c++latest`](std-specify-language-standard-version.md)) if you are still using the older experimental Standard library modules. We recommend that you use the new Standard Library modules provided by Microsoft without using this switch.
 
 ## Syntax
 
 > **`/experimental:module`**\[**`-`**]
 
 ## Remarks
 
+Although you can use this switch to use the older experimental named modules listed below, we recommend that you use the the new, standardized, way of consuming the C++ Standard Library as modules described in [Import the C++ standard library using modules](../../cpp/tutorial-import-stl-named-module.md).
+
+Before you can use the experimental modules, ensure that **C++ Modules for v143 build tools (x64/x86 - experimental)** in selected the VS Installer. It's available in the **Individual components** tab of the installer. Search for **experimental** to see the option. For more information, see [Install C++ support in Visual Studio](../install/install-visual-cpp.md).
+
 In versions of Visual Studio before Visual Studio 2019 version 16.11, you can enable experimental modules support using the **`/experimental:module`** compiler option along with the [`/std:c++latest`](std-specify-language-standard-version.md) option. In Visual Studio 2019 version 16.11, module support is enabled automatically by either **`/std:c++20`** or **`/std:c++latest`**. Use **`/experimental:module-`** to disable experimental module support.
 
-This compiler switch is available starting in Visual Studio 2015 Update 1. Modules support is feature complete in Visual Studio 2019 version 16.10. You can use the modules feature import the Standard Library modules provided by Microsoft. The new, standardized, way of consuming the C++ Standard Library as modules is described in [Import the C++ standard library using modules](tutorial-import-stl-named-module.md).
+This compiler switch is available starting in Visual Studio 2015 Update 1. Modules support is feature complete in Visual Studio 2019 version 16.10.
 
 For more information about how to use and create modules, see [Overview of modules in C++](../../cpp/modules-cpp.md).
 
@@ -36,7 +40,7 @@ import std.core;
 import std.regex;
 ```
 
-To consume the experimental Microsoft Standard Library modules, compile your program with the [`/EHsc`](../build/reference/eh-exception-handling-model.md) and [`/MD`](../build/reference/md-mt-ld-use-run-time-library.md) options.
+To consume the experimental Microsoft Standard Library modules, compile your program with the [`/EHsc`](eh-exception-handling-model.md) and [`/MD`](md-mt-ld-use-run-time-library.md) options.
 
 ### To set this compiler option in the Visual Studio development environment
 

docs/cpp/tutorial-named-modules-cpp.md

@@ -1,6 +1,6 @@
 ---
 title: "Named modules tutorial in C++"
-ms.date: 08/08/2022
+ms.date: 02/12/2025
 ms.topic: "tutorial"
 author: "tylermsft"
 ms.author: "twhitney"
@@ -237,7 +237,7 @@ int main()
 }
 ```
 
-The statement `import BasicPlane.Figures;` makes all the exported functions and types from the `BasicPlane.Figures` module visible to this file. It can come before or after any `#include` directives.
+The statement `import BasicPlane.Figures;` makes all the exported functions and types from the `BasicPlane.Figures` module visible to this file. It should come after any `#include` directives.
 
 The app then uses the types and functions from the module to output the area and width of the defined rectangle:
 
@@ -265,7 +265,7 @@ module; // optional. Defines the beginning of the global module fragment
 
 // #include directives go here but only apply to this file and
 // aren't shared with other module implementation files.
-// Macro definitions aren't visible outside this file, or to importers.
+// Macro definitions aren't visible outside this file or to importers.
 // import statements aren't allowed here. They go in the module preamble, below.
 
 export module [module-name]; // Required. Marks the beginning of the module preamble
@@ -305,7 +305,8 @@ Module implementation units are useful for breaking up a large module into small
 Module implementation unit files have a *`.cpp`* extension. The basic outline of a module implementation unit file is:
 
 ```cpp
-// optional #include or import statements. These only apply to this file
+// optional #include statements. These only apply to this file
+// optional import statements. These only apply to this file
 // imports in the associated module's interface are automatically available to this file
 
 module [module-name]; // required. Identifies which named module this implementation unit belongs to