fix suggestions and broken links (#50112)

Author: gewarren

docs/core/compatibility/sdk/10.0/code-coverage-dynamic-native-instrumentation.md

@@ -16,7 +16,7 @@ Running `dotnet test --collect:"Code Coverage"` now disables dynamic native inst
 
 ## Previous behavior
 
-Previously, dynamic native instrumentation was enabled by default and used a fallback for native modules when static native instrumentation couldn't be used. This behavior is described in [Static and dynamic native instrumentation](/visualstudio/test/customizing-code-coverage-analysis?view=vs-2022#static-and-dynamic-native-instrumentation).
+Previously, dynamic native instrumentation was enabled by default and used a fallback for native modules when static native instrumentation couldn't be used. This behavior is described in [Static and dynamic native instrumentation](/visualstudio/test/customizing-code-coverage-analysis#static-and-dynamic-native-instrumentation).
 
 ```bash
 dotnet test --collect:"Code Coverage"

docs/core/runtime-config/debugging-profiling.md

@@ -35,9 +35,9 @@ This article details the settings you can use to configure .NET debugging and pr
 
 - Specifies the GUID of the profiler to load into the currently running process.
 
-| | Setting name | Values |
-| - | - | - |
-| **runtimeconfig.json** | N/A | N/A |
+|                          | Setting name                            | Values        |
+|--------------------------|-----------------------------------------|---------------|
+| **runtimeconfig.json**   | N/A                                     | N/A           |
 | **Environment variable** | `CORECLR_PROFILER` or `DOTNET_PROFILER` | *string-guid* |
 
 ## Profiler location
@@ -49,11 +49,11 @@ Once profiling is enabled, the profiler can be loaded in two ways: with environm
 - Specifies the path to the profiler DLL to load into the currently running process (or 32-bit or 64-bit process).
 - If more than one variable is set, the bitness-specific variables take precedence. They specify which bitness of profiler to load.
 
-| | Setting name | Values |
-| - | - | - |
-| **Environment variable** | `CORECLR_PROFILER_PATH` or `DOTNET_PROFILER_PATH` | *string-path* |
-| **Environment variable** | `CORECLR_PROFILER_PATH_32` or `DOTNET_PROFILER_PATH_32` | *string-path* |
-| **Environment variable** | `CORECLR_PROFILER_PATH_64` or `DOTNET_PROFILER_PATH_64` | *string-path* |
+|                          | Setting name                                                  | Values        |
+|--------------------------|---------------------------------------------------------------|---------------|
+| **Environment variable** | `CORECLR_PROFILER_PATH` or `DOTNET_PROFILER_PATH`             | *string-path* |
+| **Environment variable** | `CORECLR_PROFILER_PATH_32` or `DOTNET_PROFILER_PATH_32`       | *string-path* |
+| **Environment variable** | `CORECLR_PROFILER_PATH_64` or `DOTNET_PROFILER_PATH_64`       | *string-path* |
 | **Environment variable** | `CORECLR_PROFILER_PATH_ARM32` or `DOTNET_PROFILER_PATH_ARM32` | *string-path* |
 | **Environment variable** | `CORECLR_PROFILER_PATH_ARM64` or `DOTNET_PROFILER_PATH_ARM64` | *string-path* |
 

docs/fundamentals/networking/quic/quic-troubleshooting.md

@@ -71,4 +71,4 @@ Getting failure for attempt to bind on a port that is from excluded range is exp
 
 ## See also
 
-- [MsQuic troubleshooting guide](https://github.com/microsoft/msquic/blob/main/docs/TSG.md)
+- [MsQuic troubleshooting guide](https://github.com/microsoft/msquic/blob/main/docs/TroubleshootingGuide.md)