Re-enable MD034 (dotnet#35542)

BBOYCOSTY3 · May 31, 2023 · ac64f9d · ac64f9d
1 parent be214a1
commit ac64f9d
Show file tree

Hide file tree

Showing 23 changed files with 407 additions and 505 deletions.
diff --git a/.markdownlint-cli2.jsonc b/.markdownlint-cli2.jsonc
@@ -40,8 +40,6 @@
                 "ul"
             ]
         },
-        // Allow Bare URLs. We often use them in text.
-        "MD034": false,
         "MD036": false,
         "MD040": false,
         // Cannot be enabled because of the include folder snippets

diff --git a/docs/core/diagnostics/dotnet-symbol.md b/docs/core/diagnostics/dotnet-symbol.md
@@ -1,6 +1,6 @@
 ---
 title: dotnet-symbol diagnostic tool - .NET CLI
-description: Learn how to install and use the dotnet-symbol CLI tool to download files required for debugging .NET dumps and minidumps. 
+description: Learn how to install and use the dotnet-symbol CLI tool to download files required for debugging .NET dumps and minidumps.
 ms.date: 11/17/2020
 ms.topic: reference
 ---
@@ -30,7 +30,7 @@ The `dotnet-symbol` global tool downloads files (symbols, DAC, modules, etc.) ne
 
 - **`--microsoft-symbol-server`**
 
-  Add 'http://msdl.microsoft.com/download/symbols' symbol server path (default).
+  Add `http://msdl.microsoft.com/download/symbols` symbol server path (default).
 
 - **`--server-path <symbol server path>`**
 

diff --git a/docs/core/install/linux-package-mixup.md b/docs/core/install/linux-package-mixup.md
@@ -227,7 +227,7 @@ Many other users have reported these problems. The following is a list of those
 - Fatal error: folder _/host/fxr_ doesn't exist
 
   - [Core #5746: The folder does not exist when installing 3.1 on CentOS 8 with packages.microsoft.com repo enabled](https://github.com/dotnet/core/issues/5746)
-  - [SDK #15476: A fatal error occurred. The folder [/usr/share/dotnet/host/fxr] does not exist](https://github.com/dotnet/sdk/issues/15476):
+  - [SDK #15476: A fatal error occurred. The folder '/usr/share/dotnet/host/fxr' does not exist](https://github.com/dotnet/sdk/issues/15476):
 
 - Fatal error: folder _/host/fxr_ doesn't contain any version-numbered child folders
 

diff --git a/docs/core/introduction.md b/docs/core/introduction.md
@@ -137,12 +137,12 @@ The runtime is designed to support multiple programming languages. C#, F#, and V
 * [C#](../csharp/index.yml) is a modern, object-oriented, and type-safe programming language. It has its roots in the C family of languages and will be immediately familiar to C, C++, Java, and JavaScript programmers.
 
 * [F#](../fsharp/index.yml) is an interoperable programming language for writing succinct, robust, and performant code. F# programming is data-oriented, where code involves transforming data with functions.
-  
+
 * [Visual Basic](../visual-basic/index.yml) uses a more verbose syntax that is closer to ordinary human language. It can be an easier language to learn for people new to programming.
 
 ## Compilation
 
-.NET apps (as written in a high-level language like C#) are compiled into an [Intermediate](https://en.wikipedia.org/wiki/Common_Intermediate_Language) Language (IL)](https://en.wikipedia.org/wiki/Common_Intermediate_Language). IL is a compact code format that can be supported on any operating system or architecture. Most .NET apps use APIs that are supported in multiple environments, requiring only the .NET runtime to run.
+.NET apps (as written in a high-level language like C#) are compiled into an [Intermediate Language (IL)](https://en.wikipedia.org/wiki/Common_Intermediate_Language). IL is a compact code format that can be supported on any operating system or architecture. Most .NET apps use APIs that are supported in multiple environments, requiring only the .NET runtime to run.
 
 IL needs to be compiled to native code to execute on a CPU, for example, Arm64 or x64. .NET supports both Ahead-Of-Time (AOT) and Just-In-Time (JIT) compilation models.
 

diff --git a/docs/core/porting/third-party-deps.md b/docs/core/porting/third-party-deps.md
@@ -88,7 +88,7 @@ Remember that open-source project maintainers and NuGet package publishers are o
 
 If you can't resolve your issue with any of these options, you may have to port to .NET Core at a later date.
 
-The .NET Team would like to know which libraries are the most important to support with .NET Core. You can send an email to [email protected] about the libraries you'd like to use.
+The .NET Team would like to know which libraries are the most important to support with .NET Core. You can send an email to <[email protected]> about the libraries you'd like to use.
 
 ## Analyze non-NuGet dependencies
 

diff --git a/docs/framework/configure-apps/file-schema/wcf/issuedtokenparameters.md b/docs/framework/configure-apps/file-schema/wcf/issuedtokenparameters.md
@@ -6,19 +6,19 @@ ms.assetid: 120b3f37-7331-4816-b712-d6aab39655a4
 ---
 # \<issuedTokenParameters>
 
-Specifies the parameters for a security token issued in a Federated security scenario.  
-  
+Specifies the parameters for a security token issued in a Federated security scenario.
+
 [**\<configuration>**](../configuration-element.md)\
 &nbsp;&nbsp;[**\<system.serviceModel>**](system-servicemodel.md)\
 &nbsp;&nbsp;&nbsp;&nbsp;[**\<bindings>**](bindings.md)\
 &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;[**\<customBinding>**](custombinding.md)\
 &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;**\<binding>**\
 &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;[**\<security>**](security-of-custombinding.md)\
-&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;**\<issuedTokenParameters>**  
-  
-## Syntax  
-  
-```xml  
+&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;**\<issuedTokenParameters>**
+
+## Syntax
+
+```xml
 <issuedTokenParameters defaultMessageSecurityVersion="System.ServiceModel.MessageSecurityVersion"
                        inclusionMode="AlwaysToInitiator/AlwaysToRecipient/Never/Once"
                        keySize="Integer"
@@ -33,42 +33,42 @@ Specifies the parameters for a security token issued in a Federated security sce
           binding="" />
   <issuerMetadata address="String" />
 </issuedTokenParameters>
-```  
-  
-## Type  
-
- `Type`  
-  
-## Attributes and Elements  
-
- The following sections describe attributes, child elements, and parent elements.  
-  
-### Attributes  
-  
-|Attribute|Description|  
-|---------------|-----------------|  
-|defaultMessageSecurityVersion|Specifies the versions of the security specifications, (WS-Security, WS-Trust, WS-Secure Conversation and WS-Security Policy) that must be supported by the binding. This value is of type <xref:System.ServiceModel.MessageSecurityVersion>.|  
-|inclusionMode|Specifies the token inclusion requirements. This attribute is of type <xref:System.ServiceModel.Security.Tokens.SecurityTokenInclusionMode>.|  
-|keySize|An integer that specifies the token key size. The default value is 256.|  
-|keyType|A valid value of <xref:System.IdentityModel.Tokens.SecurityKeyType> that specifies the key type. The default is `SymmetricKey`.|  
-|tokenType|A string that specifies the token type. The default is "http://docs.oasis-open.org/wss/oasis-wss-saml-token-profile-1.1#SAML".|  
-  
-### Child Elements  
-  
-|Element|Description|  
-|-------------|-----------------|  
-|[\<additionalRequestParameters>](additionalrequestparameters-element.md)|A collection of configuration elements that specify additional request parameters.|  
-|[\<claimTypeRequirements>](claimtyperequirements-element.md)|Specifies a collection of required claim types.<br /><br /> In a federated scenario, services state the requirements on incoming credentials. For example, the incoming credentials must possess a certain set of claim types. Each element in this collection specifies the types of required and optional claims expected to appear in a federated credential.|  
-|[\<issuer>](issuer-of-issuedtokenparameters.md)|A configuration element that specifies the endpoint that issues the current token.|  
-|[\<issuerMetadata>](issuermetadata-of-issuedtokenparameters.md)|A configuration element that specifies the endpoint address of the token issuer's metadata.|  
-  
-### Parent Elements  
-  
-|Element|Description|  
-|-------------|-----------------|  
-|[\<secureConversationBootstrap>](secureconversationbootstrap.md)|Specifies the default values used for initiating a secure conversation service.|  
-|[\<security>](security-of-custombinding.md)|Specifies the security options for a custom binding.|  
-  
+```
+
+## Type
+
+ `Type`
+
+## Attributes and Elements
+
+ The following sections describe attributes, child elements, and parent elements.
+
+### Attributes
+
+|Attribute|Description|
+|---------------|-----------------|
+|defaultMessageSecurityVersion|Specifies the versions of the security specifications, (WS-Security, WS-Trust, WS-Secure Conversation and WS-Security Policy) that must be supported by the binding. This value is of type <xref:System.ServiceModel.MessageSecurityVersion>.|
+|inclusionMode|Specifies the token inclusion requirements. This attribute is of type <xref:System.ServiceModel.Security.Tokens.SecurityTokenInclusionMode>.|
+|keySize|An integer that specifies the token key size. The default value is 256.|
+|keyType|A valid value of <xref:System.IdentityModel.Tokens.SecurityKeyType> that specifies the key type. The default is `SymmetricKey`.|
+|tokenType|A string that specifies the token type. The default is `"http://docs.oasis-open.org/wss/oasis-wss-saml-token-profile-1.1#SAML"`.|
+
+### Child Elements
+
+|Element|Description|
+|-------------|-----------------|
+|[\<additionalRequestParameters>](additionalrequestparameters-element.md)|A collection of configuration elements that specify additional request parameters.|
+|[\<claimTypeRequirements>](claimtyperequirements-element.md)|Specifies a collection of required claim types.<br /><br /> In a federated scenario, services state the requirements on incoming credentials. For example, the incoming credentials must possess a certain set of claim types. Each element in this collection specifies the types of required and optional claims expected to appear in a federated credential.|
+|[\<issuer>](issuer-of-issuedtokenparameters.md)|A configuration element that specifies the endpoint that issues the current token.|
+|[\<issuerMetadata>](issuermetadata-of-issuedtokenparameters.md)|A configuration element that specifies the endpoint address of the token issuer's metadata.|
+
+### Parent Elements
+
+|Element|Description|
+|-------------|-----------------|
+|[\<secureConversationBootstrap>](secureconversationbootstrap.md)|Specifies the default values used for initiating a secure conversation service.|
+|[\<security>](security-of-custombinding.md)|Specifies the security options for a custom binding.|
+
 ## See also
 
 - <xref:System.ServiceModel.Security.Tokens.IssuedSecurityTokenParameters>