Fix links (#23481)

Author: gewarren

docs/csharp/language-reference/compiler-options/advanced.md

@@ -254,9 +254,9 @@ The following table lists common subsystem versions of Windows.
 The default value of the **SubsystemVersion** compiler option depends on the conditions in the following list:
 
 - The default value is 6.02 if any compiler option in the following list is set:
-  - [-target:appcontainerexe](./target-appcontainerexe-compiler-option.md)
-  - [-target:winmdobj](./target-winmdobj-compiler-option.md)
-  - [-platform:arm](./platform-compiler-option.md)
+  - [-target:appcontainerexe](output.md)
+  - [-target:winmdobj](output.md)
+  - [-platform:arm](output.md)
 - The default value is 6.00 if you're using MSBuild, you're targeting .NET Framework 4.5, and you haven't set any of the compiler options that were specified earlier in this list.
 - The default value is 4.00 if none of the previous conditions are true.
 

docs/csharp/language-reference/compiler-options/output.md

@@ -138,6 +138,6 @@ The **winmdobj** setting signals to the compiler that an intermediate module is
 
 ### appcontainerexe
 
-If you use the **appcontainerexe** compiler option, the compiler creates a Windows executable (*.exe*) file that must be run in an app container. This option is equivalent to [-target:winexe](./target-winexe-compiler-option.md) but is designed for Windows 8.x Store apps.
+If you use the **appcontainerexe** compiler option, the compiler creates a Windows executable (*.exe*) file that must be run in an app container. This option is equivalent to [-target:winexe](output.md) but is designed for Windows 8.x Store apps.
 
 To require the app to run in an app container, this option sets a bit in the [Portable Executable](/windows/desktop/Debug/pe-format) (PE) file. When that bit is set, an error occurs if the CreateProcess method tries to launch the executable file outside an app container. Unless you use the [**OutputAssembly**](#outputassembly) option, the output file name takes the name of the input file that contains the [`Main`](../../programming-guide/main-and-command-args/index.md) method.

docs/csharp/language-reference/operators/null-forgiving.md

@@ -48,4 +48,4 @@ For more information, see [The null-forgiving operator](~/_csharplang/proposals/
 
 - [C# reference](../index.md)
 - [C# operators and expressions](index.md)
-- [Tutorial: Design with nullable reference types](../../tutorials/nullable-reference-types.md)
+- [Tutorial: Design with nullable reference types](../../whats-new/tutorials/nullable-reference-types.md)

docs/csharp/misc/cs2002.md

@@ -14,7 +14,7 @@ Source file 'file' specified multiple times
 
  A source file name was passed to the compiler more than once. You can only specify a file once to the compiler to build an output file.  
 
- This warning cannot be suppressed by the [-nowarn](../language-reference/compiler-options/nowarn-compiler-option.md) option.  
+ This warning cannot be suppressed by the [-nowarn](../language-reference/compiler-options/errors-warnings.md) option.  
 
  The following sample generates CS2002:  
 

docs/csharp/misc/cs2020.md

@@ -12,4 +12,4 @@ ms.assetid: b2db7a05-5965-4a9b-86c3-0c4792b29a6c
 
 Only the first set of input files can build a target other than 'module'  
 
- In a multi-output compilation, the first output file must be built with [-target:exe](../language-reference/compiler-options/target-exe-compiler-option.md), [-target:winexe](../language-reference/compiler-options/target-winexe-compiler-option.md), or [-target:library](../language-reference/compiler-options/target-library-compiler-option.md). Any subsequent output files must be built with [-target:module](../language-reference/compiler-options/target-module-compiler-option.md).
+ In a multi-output compilation, the first output file must be built with [-target:exe](../language-reference/compiler-options/output.md), [-target:winexe](../language-reference/compiler-options/output.md), or [-target:library](../language-reference/compiler-options/output.md). Any subsequent output files must be built with [-target:module](../language-reference/compiler-options/output.md).

docs/csharp/nullable-migration-strategies.md

@@ -210,5 +210,5 @@ You'll never observe an actual null value at runtime except as a result of a pro
 
 ## See also
 
-- [Migrate an existing codebase to nullable references](tutorials/upgrade-to-nullable-references.md)
+- [Migrate an existing codebase to nullable references](whats-new/tutorials/upgrade-to-nullable-references.md)
 - [Working with Nullable Reference Types in EF Core](/ef/core/miscellaneous/nullable-reference-types)

docs/csharp/nullable-references.md

@@ -211,5 +211,5 @@ In the preceding example, the declaration of the array shows it holds non-nullab
 
 - [Draft nullable reference types specification](~/_csharplang/proposals/csharp-9.0/nullable-reference-types-specification.md)
 - [Intro to nullable references tutorial](whats-new/tutorials/nullable-reference-types.md)
-- [Migrate an existing codebase to nullable references](tutorials/upgrade-to-nullable-references.md)
+- [Migrate an existing codebase to nullable references](whats-new/tutorials/upgrade-to-nullable-references.md)
 - [**Nullable** (C# Compiler option)](language-reference/compiler-options/language.md#nullable)

docs/csharp/tour-of-csharp/features.md

@@ -112,7 +112,7 @@ The following code sample demonstrates how to get the `HelpAttribute` instances
 
 ## Learn more
 
-You can explore more about C# by trying one of our [tutorials](../tutorials/index.md).
+You can explore more about C# by trying one of our [tutorials](../tutorials/intro-to-csharp/introduction-to-classes.md).
 
 >[!div class="step-by-step"]
 >[Previous](program-building-blocks.md)

docs/csharp/tour-of-csharp/tutorials/arrays-and-collections.md

@@ -205,6 +205,6 @@ You can see an example solution by [looking at the finished sample code on GitHu
 
 With each iteration of the loop, you're taking the last two integers in the list, summing them, and adding that value to the list. The loop repeats until you've added 20 items to the list.
 
-Congratulations, you've completed the list tutorial. You can continue with [additional](../../tutorials/index.md) tutorials in your own development environment.
+Congratulations, you've completed the list tutorial. You can continue with [additional](../../tutorials/intro-to-csharp/introduction-to-classes.md) tutorials in your own development environment.
 
 You can learn more about working with the `List` type in the .NET fundamentals article on [collections](../../../standard/collections/index.md). You'll also learn about many other collection types.

docs/csharp/tutorials/intro-to-csharp/object-oriented-programming.md

@@ -186,4 +186,4 @@ This tutorial demonstrated many of the techniques used in Object-Oriented progra
 - You used *Inheritance* when you leveraged the implementation already created in the `BankAccount` class to save code.
 - You used *Polymorphism* when you created `virtual` methods that derived classes could override to create specific behavior for that account type.
 
-Congratulations, you've finished all of our introduction to C# tutorials. To learn more, try more of our [tutorials](../index.md).
+Congratulations, you've finished all of our introduction to C# tutorials. To learn more, try more of our [tutorials](introduction-to-classes.md).