add language slugs (#11216)

Author: gewarren

xml/System.Web.Caching/SqlCacheDependency.xml

@@ -145,7 +145,7 @@
 
  The database name passed to the `database` parameter must be defined in the application's Web.config file. For example, the following Web.config file defines a database named pubs for <xref:System.Web.Caching.SqlCacheDependency> change notifications.
 
-```
+```xml
 <configuration>
   <connectionStrings>
     <add name="Pubs" connectionString="Data Source=(local); Initial Catalog=pubs; Integrated Security=true"; providerName="System.Data.SqlClient" />
@@ -247,7 +247,7 @@
 ## Remarks
  The following markup shows a typical output-cache dependency directive.
 
-```
+```xml
 <%@ OutputCache Duration="3600" SqlDependency="Northwind:Employees" VaryByParam="none" %>
 ```
 

xml/System.Web.Compilation/RouteUrlExpressionBuilder.xml

@@ -36,7 +36,7 @@
 ## Examples
  The following example shows how to create markup that generates a hyperlink with a URL that is formatted for a route. The route is defined by using `http://www.contoso.com/search/{searchterm}` as the URL pattern.
 
-```
+```xml
 <asp:HyperLink ID="HyperLink1" runat="server"
                NavigateUrl="<%$ RouteUrl:searchterm=Bicycles %>">
   Search for Bicycles
@@ -47,7 +47,7 @@
 
  If the URL parameters provided to the `RouteUrl` expression are not sufficient to uniquely identify a route, you must include the route name. For example, if a Web application has two routes with `searchterm` as the sole URL parameter, the routes would have to be defined by using route names, and the hyperlink markup would resemble the following example:
 
-```
+```xml
 <asp:HyperLink ID="HyperLink1" runat="server"
                NavigateUrl="<%$ RouteUrl:searchterm=Bicycles,
                routename=BasicSearchRoute %>">

xml/System.Web.Compilation/RouteValueExpressionBuilder.xml

@@ -36,7 +36,7 @@
 ## Examples
  The following example shows how to use markup to display the value of the URL parameter `searchterm`. The route is defined by using `http://www.contoso.com/search/{searchterm}` as the URL pattern.
 
-```
+```xml
 <asp:Label ID="Label1" runat="server"
     text="<%$ RouteValue:searchterm %>">
 </asp:Label>

xml/System.Web.Configuration/AuthorizationSection.xml

@@ -35,7 +35,7 @@
 > [!NOTE]
 >  If you use the `credentials` section, be sure to follow the guidelines explained at [ASP.NET Authentication](https://learn.microsoft.com/previous-versions/aspnet/eeyk640h(v=vs.100)). For scalability and better security capability, it is recommended that you use an external database to store the users' credentials. For more information about building secure ASP.NET applications, see [Securing Your ASP.NET Application](https://learn.microsoft.com/archive/msdn-magazine/2012/january/asp-net-security-securing-your-asp-net-applications) and [Building Secure ASP.NET Applications: Authentication, Authorization, and Secure Communication](https://learn.microsoft.com/previous-versions/msp-n-p/ff649357(v=pandp.10)).
 
-```
+```xml
 <authorization>
   <allow users="userName" roles="admin" verbs="post" />
   <deny users="*" verbs="post"/>

xml/System.Web.Configuration/ClientTarget.xml

@@ -37,7 +37,7 @@
 
  The following code example shows how to declaratively specify values for several properties of the <xref:System.Web.Configuration.ClientTarget> class.
 
-```
+```xml
 <clientTarget>
   <add alias=
     "uplevel"

xml/System.Web.Configuration/ClientTargetCollection.xml

@@ -40,7 +40,7 @@
 
  The following example shows an excerpt from the configuration file.
 
-```
+```xml
 <clientTarget>
   <add alias=
     "uplevel"

xml/System.Web.Configuration/ClientTargetSection.xml

@@ -31,7 +31,7 @@
 
  The following code example shows how to declaratively specify values for several properties of the <xref:System.Web.Configuration.ClientTarget> class.
 
-```
+```xml
 <clientTarget>
   <add alias=
     "uplevel" userAgent="Mozilla/5.0 (compatible;MSIE 6.0;Windows NT 5.1)"/>

xml/System.Web.Configuration/HttpCapabilitiesBase.xml

@@ -2349,7 +2349,7 @@
 ## Remarks
  Intended for internal use only. Some browsers require a meta-tag similar to the following for the browser to render properly.
 
-```
+```html
 <META NAME="NAME" CONTENT="VALUE">
 ```
 
@@ -2421,14 +2421,12 @@
 ## Remarks
  If `true`, server-control adapters insert the following tag into the HTML `<head>` element of a Web page:
 
-```
+```html
 <META HTTP-EQUIV="CONTENT-TYPE" CONTENT=""; CHARSET="">
 ```
 
  In this example, `CONTENT` is the value returned by the <xref:System.Web.Configuration.HttpCapabilitiesBase.PreferredRenderingMime%2A> property, and `charset` is the character encoding used.
 
-
-
 ## Examples
  The following code example shows how to determine whether the browser requires an HTML `<meta>` element for which the `content-type` attribute is specified.
 
@@ -2724,7 +2722,7 @@
 ## Remarks
  HTTP is a stateless protocol, and `VIEWSTATE` is one mechanism used to persist client changes across multiple requests. Each control on a Web page contains a <xref:System.Web.UI.Control.ViewState%2A> property, which represents the accumulation of any changes made by the client. In a Web Forms page, these changes are encoded in postback data as the `value` of an HTML `<input>` element with a `type` attribute of `hidden`. For example:
 
-```
+```html
 <input type="hidden" name="__VIEWSTATE" value="t0PH_u56?cDxleHQ7P=" />
 ```
 
@@ -3147,7 +3145,7 @@
 ## Remarks
  The `cache-control` value for the `http-equiv` attribute of HTML `<meta>` elements allows control over client caching of downloaded content, which includes Web pages. The following HTML fragment shows an example:
 
-```
+```html
 <META HTTP-EQUIV="CACHE-CONTROL" CONTENT="NO-CACHE"/>
 ```
 
@@ -3157,7 +3155,7 @@
 
  The <xref:System.Web.Configuration.HttpCapabilitiesBase.SupportsCacheControlMetaTag%2A> property also applies to the equivalent HTTP header form:
 
-```
+```txt
 CACHE-CONTROL: NO-CACHE
 ```
 

xml/System.Web.Configuration/HttpHandlerAction.xml

@@ -39,7 +39,7 @@
 
  The following configuration excerpt shows how to specify values declaratively for the `httpHandlers` section.
 
-```
+```xml
 <httpHandlers>
   <add path="Calculator.custom"
     type="Samples.Aspnet.SystemWebConfiguration.Calculator, CalculatorHandler"

xml/System.Web.Configuration/HttpHandlersSection.xml

@@ -35,7 +35,7 @@
 
  The following configuration excerpt shows how to specify values declaratively for the `httpHandlers` section.
 
-```
+```xml
 <httpHandlers>
   <add path="Calculator.custom"
     type="Samples.Aspnet.SystemWebConfiguration.Calculator, CalculatorHandler"