fix broken links; fixes #20941 (#20950)

Author: gewarren

docs/architecture/microservices/multi-container-microservice-net-applications/test-aspnet-core-services-web-apps.md

@@ -115,7 +115,7 @@ public class PrimeWebDefaultRequestShould
     <https://github.com/moq/moq>
 
 - **NUnit**. Official site. \
-    <https://www.nunit.org/>
+    <https://nunit.org/>
 
 ### Implementing service tests on a multi-container application
 

docs/core/extensions/logging-providers.md

@@ -93,7 +93,7 @@ The `EventSource` provider writes to a cross-platform event source with the name
 
 The [dotnet-trace](../diagnostics/dotnet-trace.md) tool is a cross-platform CLI global tool that enables the collection of .NET Core traces of a running process. The tool collects <xref:Microsoft.Extensions.Logging.EventSource> provider data using a <xref:Microsoft.Extensions.Logging.EventSource.LoggingEventSource>.
 
-See [dotnet-trace](../diagnostics/dotnet-trace.md) for installation instructions. For a diagnostic tutorial using `dotnet-trace`, see [Debug high CPU usage in .NET Core](/../diagnostics/debug-highcpu.md).
+See [dotnet-trace](../diagnostics/dotnet-trace.md) for installation instructions. For a diagnostic tutorial using `dotnet-trace`, see [Debug high CPU usage in .NET Core](../diagnostics/debug-highcpu.md).
 
 ### Windows EventLog
 

docs/fundamentals/code-analysis/code-style-rule-options.md

@@ -8,13 +8,13 @@ ms.author: gewarren
 ---
 # Code style rule options
 
-You can define and maintain consistent *code style* in your codebase by defining .NET code style rule options in an [EditorConfig](/visualstudio/ide/create-portable-custom-editor-options.md) file. These rules are surfaced by various development IDEs, such as Visual Studio, as you edit your code. For .NET projects, these rules can also be [enforced at build time](overview.md#code-style-analysis). You can enable or disable individual rules and configure the degree to which you want each rule enforced, via a severity level.
+You can define and maintain consistent *code style* in your codebase by defining .NET code style rule options in an [EditorConfig](/visualstudio/ide/create-portable-custom-editor-options) file. These rules are surfaced by various development IDEs, such as Visual Studio, as you edit your code. For .NET projects, these rules can also be [enforced at build time](overview.md#code-style-analysis). You can enable or disable individual rules and configure the degree to which you want each rule enforced, via a severity level.
 
 > [!TIP]
 >
 > - When you define code style options in an EditorConfig file, you're configuring how you want the [code style analyzers](overview.md#code-style-analysis) to analyze your code. The EditorConfig file is the configuration file for these analyzers.
 >
-> - Code style options can also be set in Visual Studio in the [Text editor options](/visualstudio/ide/code-styles-and-code-cleanup.md) dialog. These are per-user options that are only respected while editing in Visual Studio. These options are not respected at build time or by other IDEs. Additionally, if the project or solution opened inside Visual Studio has an EditorConfig file, then options from the EditorConfig file take precedence.
+> - Code style options can also be set in Visual Studio in the [Text editor options](/visualstudio/ide/code-styles-and-code-cleanup) dialog. These are per-user options that are only respected while editing in Visual Studio. These options are not respected at build time or by other IDEs. Additionally, if the project or solution opened inside Visual Studio has an EditorConfig file, then options from the EditorConfig file take precedence.
 
 Code style rules are divided into following subcategories:
 

docs/fundamentals/code-analysis/quality-rules/ca3004.md

@@ -33,11 +33,11 @@ This rule attempts to find an exception message, stack trace, or string represen
 > This rule can't track data across assemblies. For example, if one assembly catches an exception and then passes it to another assembly that outputs the exception, this rule won't produce a warning.
 
 > [!NOTE]
-> There is a configurable limit to how deep this rule will analyze data flow across method calls. See [Analyzer Configuration](https://github.com/dotnet/roslyn-analyzers/blob/master/docs/Analyzer%20Configuration.md#dataflow-analysis) for how to configure the limit in an EditorConfig file.
+> There is a configurable limit to how deep this rule will analyze data flow across method calls. For information about how to configure the limit in an EditorConfig file, see [Analyzer Configuration](https://github.com/dotnet/roslyn-analyzers/blob/master/docs/Analyzer%20Configuration.md#dataflow-analysis).
 
 ## How to fix violations
 
-Don't output exception information to HTTP responses. Instead, provide a generic error message. See [OWASP's Error Handling page](https://www.owasp.org/index.php/Error_Handling) for more guidance.
+Don't output exception information to HTTP responses. Instead, provide a generic error message. For more information, see [OWASP's Improper Error Handling page](https://owasp.org/www-community/Improper_Error_Handling).
 
 ## When to suppress warnings
 

docs/fundamentals/code-analysis/style-rules/naming-rules.md

@@ -182,7 +182,7 @@ The order in which naming rules are defined in an EditorConfig file doesn't matt
 
 > [!NOTE]
 >
-> If you're using a version of Visual Studio earlier than Visual Studio 2019 version 16.2, naming rules should be ordered from most-specific to least-specific in the EditorConfig file. The first rule encountered that can be applied is the only rule that is applied. However, if there are multiple rule *properties* with the same name, the most recently found property with that name takes precedence. For more information, see [File hierarchy and precedence](/visualstudio/ide/create-portable-custom-editor-options.md#file-hierarchy-and-precedence).
+> If you're using a version of Visual Studio earlier than Visual Studio 2019 version 16.2, naming rules should be ordered from most-specific to least-specific in the EditorConfig file. The first rule encountered that can be applied is the only rule that is applied. However, if there are multiple rule *properties* with the same name, the most recently found property with that name takes precedence. For more information, see [File hierarchy and precedence](/visualstudio/ide/create-portable-custom-editor-options#file-hierarchy-and-precedence).
 
 ## Default naming styles
 

docs/machine-learning/resources/metrics.md

@@ -17,7 +17,7 @@ For example, for the classification task, the model is evaluated by measuring ho
 |-----------|-----------------------|-----------|
 | **Accuracy** |  [Accuracy](https://en.wikipedia.org/wiki/Accuracy_and_precision#In_binary_classification) is the proportion of correct predictions with a test data set. It is the ratio of number of correct predictions to the total number of input samples. It works well if there are similar number of samples belonging to each class.| **The closer to 1.00, the better**. But exactly 1.00 indicates an issue (commonly: label/target leakage, over-fitting, or testing with training data). When the test data is unbalanced (where most of the instances belong to one of the classes), the dataset is small, or scores approach 0.00 or 1.00, then accuracy doesn't really capture the effectiveness of a classifier and you need to check additional metrics. |
 | **AUC** |    [aucROC](https://en.wikipedia.org/wiki/Receiver_operating_characteristic) or *Area under the curve* measures the area under the curve created by sweeping the true positive rate vs. the false positive rate.  |   **The closer to 1.00, the better**. It should be greater than 0.50 for a model to be acceptable. A model with AUC of 0.50 or less is worthless. |
-| **AUCPR** | [aucPR](https://www.coursera.org/lecture/ml-classification/precision-recall-curve-rENu8) or *Area under the curve of a Precision-Recall curve*: Useful measure of success of prediction when the classes are imbalanced (highly skewed datasets). |  **The closer to 1.00, the better**. High scores close to 1.00 show that the classifier is returning accurate results (high precision), as well as returning a majority of all positive results (high recall). |
+| **AUCPR** | aucPR or *Area under the curve of a Precision-Recall curve*: Useful measure of success of prediction when the classes are imbalanced (highly skewed datasets). |  **The closer to 1.00, the better**. High scores close to 1.00 show that the classifier is returning accurate results (high precision), as well as returning a majority of all positive results (high recall). |
 | **F1-score** | [F1 score](https://en.wikipedia.org/wiki/F1_score) also known as *balanced F-score or F-measure*. It's the harmonic mean of the precision and recall. F1 Score is helpful when you want to seek a balance between Precision and Recall.| **The closer to 1.00, the better**.  An F1 score reaches its best value at 1.00 and worst score at 0.00. It tells you how precise your classifier is. |
 
 For further details on binary classification metrics read the following articles:

docs/standard/analyzers/platform-compat-analyzer.md

@@ -376,5 +376,5 @@ All the conditional checks used in the [platform guard examples](#guard-platform
 - [Target Framework Names in .NET 5](https://github.com/dotnet/designs/blob/master/accepted/2020/net5/net5.md)
 - [Annotating platform-specific APIs and detecting its use](https://github.com/dotnet/designs/blob/master/accepted/2020/platform-checks/platform-checks.md)
 - [Annotating APIs as unsupported on specific platforms](https://github.com/dotnet/designs/blob/master/accepted/2020/platform-exclusion/platform-exclusion.md)
-- [CA1416 Platform compatibility analyzer](/visualstudio/code-quality/ca1416)
+- [CA1416 Platform compatibility analyzer](../../fundamentals/code-analysis/quality-rules/ca1416.md)
 - [.NET API analyzer](../../standard/analyzers/api-analyzer.md)

docs/standard/linq/functional-vs-imperative-programming.md

@@ -52,5 +52,5 @@ Fortunately, C# and Visual Basic don't require the full leap to functional progr
 ## See also
 
 - [Introduction to pure functional transformations](introduction-pure-functional-transformations.md)
-- [XSLT Transformations](/../../standard/data/xml/xslt-transformations.md)
+- [XSLT Transformations](../data/xml/xslt-transformations.md)
 - [Refactor into pure functions](refactor-pure-functions.md)

docs/visual-basic/misc/bc2027.md

@@ -1,29 +1,29 @@
 ---
 title: "cannot send error report automatically"
 ms.date: 07/20/2015
-f1_keywords: 
+f1_keywords:
   - "bc2027"
   - "vbc2027"
-helpviewer_keywords: 
+helpviewer_keywords:
   - "BC2027"
 ms.assetid: 84ba8580-2234-46d1-b4a5-94b03f64c0c7
 ---
 # cannot send error report automatically
 
-cannot send error report automatically. Please visit 'https://go.microsoft.com/fwlink/?LinkId=42039' to configure send error report settings.  
-  
- You specified the `/errorreport:send` compiler option, but the computer is not configured to send error reports automatically. No information will be sent about internal errors in the Visual Basic compiler.  
-  
- **Error ID:** BC2027  
-  
-## To correct this error  
-  
-- Remove the `/errorreport:send` compiler option, or replace it with `/errorreport:queue`, `/errorreport:prompt`, or `/errorreport:none`.  
-  
-     — or —  
-  
-- Enable automatic error reporting by following the instructions at <https://go.microsoft.com/fwlink/?LinkId=42039>.  
-  
+cannot send error report automatically. Please visit \<link> to configure send error report settings.
+
+You specified the `/errorreport:send` compiler option, but the computer is not configured to send error reports automatically. No information will be sent about internal errors in the Visual Basic compiler.
+
+**Error ID:** BC2027
+
+## To correct this error
+
+- Remove the `/errorreport:send` compiler option, or replace it with `/errorreport:queue`, `/errorreport:prompt`, or `/errorreport:none`.
+
+     — or —
+
+- Enable automatic error reporting by following the instructions at <https://go.microsoft.com/fwlink/?LinkId=42039>.
+
 ## See also
 
 - [-errorreport](../reference/command-line-compiler/errorreport.md)