fix links

TylerMSFT · TylerMSFT · commit 8a284af34473 · 2024-01-26T11:28:55.000-08:00
diff --git a/docs/cpp/tutorial-import-stl-named-module.md b/docs/cpp/tutorial-import-stl-named-module.md
@@ -62,7 +62,7 @@ The statement `import std;` or `import std.compat;` imports the standard library
 1. Compile the `std` named module with the following command:
 
     ```cmd
-    cl /std:c++latest /EHsc /c /nologo /W4 /c "%VCToolsInstallDir%\modules\std.ixx"
+    cl /std:c++latest /EHsc /nologo /W4 /c "%VCToolsInstallDir%\modules\std.ixx"
     ```
 
     If you get errors, ensure that you're using the correct version of the command prompt. If you're still having issues, please file a bug at [Visual Studio Developer Community](https://developercommunity.visualstudio.com/home).
@@ -79,14 +79,14 @@ The statement `import std;` or `import std.compat;` imports the standard library
     |---|---|
     | [`/std:c++:latest`](../build/reference/std-specify-language-standard-version.md) | Use the latest version of the C++ language standard and library. Although module support is available under `/std:c++20`, you need the latest standard library to get support for standard library named modules. |
     | [`/EHsc`](../build/reference/eh-exception-handling-model.md) | Use C++ exception handling, except for functions marked `extern "C"`. |
-    | [`/c`](../build/reference/c-compile-without-linking.md) | Compile without linking, because we are just building the binary named module interface at this point. |
-    | [`/W4`](../build/reference/w4-enable-all-warnings.md) | Using /W4 is generally recommended, especially for new projects because it enables all level 1, level 2, level 3, and most level 4 (informational) warnings, which can help you catch potential issues early. It essentially provides lint-like warnings that can help ensure the fewest possible hard-to-find code defects. |
+    | [`/W4`](../build/reference//compiler-option-warning-level.md) | Using /W4 is generally recommended, especially for new projects because it enables all level 1, level 2, level 3, and most level 4 (informational) warnings, which can help you catch potential issues early. It essentially provides lint-like warnings that can help ensure the fewest possible hard-to-find code defects. |
+    | [`/c`](../build/reference/c-compile-without-linking.md) | Compile without linking, because we're just building the binary named module interface at this point. |
 
-    If your build scenario requires it, you can control the object file name and the named module interface file name with the following switches:
-    - [`/Fo`](../build/reference/fo-object-file-name.md). For example, `/Fo "somethingelse.obj"`. By default, the compiler creates a file name that is the same as the module name you are compiling. In the example, the output name is `std.obj` because we are compiling the file `std.ixx`.
-    - [`/ifcOutput`](../build/reference/ifcoutput-named-module-interface-file-name.md). For example, `/ifcOutput "somethingelse.ifc"`. In the example, the generated `ifc` file is `std.ifc` because we are compiling the file `std.ixx`.
+    You can control the object file name and the named module interface file name with the following switches:
+    - [`/Fo`](../build/reference/fo-object-file-name.md). For example, `/Fo "somethingelse.obj"`. By default, the compiler creates a file name that is the same as the module name you are compiling. In the example, the output name is `std.obj` because we're compiling the file `std.ixx`.
+    - [`/ifcOutput`](../build/reference/ifc-output.md). For example, `/ifcOutput "somethingelse.ifc"`. In the example, the generated `ifc` file is `std.ifc` because we're compiling the file `std.ixx`.
 
-1. Try importing the `std` library by creating a file named `importExample.cpp` with the following content:
+1. Importing the `std` library you just built by creating a file named `importExample.cpp` with the following content:
 
     ```cpp
     // requires /std:c++latest
