Change en dash layout elements to colon-space syntax (#18506)

* Change en dash layout elements to colon-space syntax

* Update

* Update

Author: guardrex

aspnetcore/blazor/call-javascript-from-dotnet.md

@@ -71,8 +71,8 @@ To use the <xref:Microsoft.JSInterop.IJSRuntime> abstraction, adopt any of the f
 
 In the client-side sample app that accompanies this topic, two JavaScript functions are available to the app that interact with the DOM to receive user input and display a welcome message:
 
-* `showPrompt` &ndash; Produces a prompt to accept user input (the user's name) and returns the name to the caller.
-* `displayWelcome` &ndash; Assigns a welcome message from the caller to a DOM object with an `id` of `welcome`.
+* `showPrompt`: Produces a prompt to accept user input (the user's name) and returns the name to the caller.
+* `displayWelcome`: Assigns a welcome message from the caller to a DOM object with an `id` of `welcome`.
 
 *wwwroot/exampleJsInterop.js*:
 

aspnetcore/blazor/call-web-api.md

@@ -57,9 +57,9 @@ The client's base address is set to the originating server's address. Inject an
 
 In the following examples, a Todo web API processes create, read, update, and delete (CRUD) operations. The examples are based on a `TodoItem` class that stores the:
 
-* ID (`Id`, `long`) – Unique ID of the item.
-* Name (`Name`, `string`) – Name of the item.
-* Status (`IsComplete`, `bool`) – Indication if the Todo item is finished.
+* ID (`Id`, `long`): Unique ID of the item.
+* Name (`Name`, `string`): Name of the item.
+* Status (`IsComplete`, `bool`): Indication if the Todo item is finished.
 
 ```csharp
 private class TodoItem
@@ -72,7 +72,7 @@ private class TodoItem
 
 JSON helper methods send requests to a URI (a web API in the following examples) and process the response:
 
-* <xref:System.Net.Http.Json.HttpClientJsonExtensions.GetFromJsonAsync%2A> &ndash; Sends an HTTP GET request and parses the JSON response body to create an object.
+* <xref:System.Net.Http.Json.HttpClientJsonExtensions.GetFromJsonAsync%2A>: Sends an HTTP GET request and parses the JSON response body to create an object.
 
   In the following code, the `todoItems` are displayed by the component. The `GetTodoItems` method is triggered when the component is finished rendering ([OnInitializedAsync](xref:blazor/lifecycle#component-initialization-methods)). See the sample app for a complete example.
 
@@ -88,7 +88,7 @@ JSON helper methods send requests to a URI (a web API in the following examples)
   }
   ```
 
-* <xref:System.Net.Http.Json.HttpClientJsonExtensions.PostAsJsonAsync%2A> &ndash; Sends an HTTP POST request, including JSON-encoded content, and parses the JSON response body to create an object.
+* <xref:System.Net.Http.Json.HttpClientJsonExtensions.PostAsJsonAsync%2A>: Sends an HTTP POST request, including JSON-encoded content, and parses the JSON response body to create an object.
 
   In the following code, `newItemName` is provided by a bound element of the component. The `AddItem` method is triggered by selecting a `<button>` element. See the sample app for a complete example.
 
@@ -116,7 +116,7 @@ JSON helper methods send requests to a URI (a web API in the following examples)
   var content = response.Content.ReadFromJsonAsync<WeatherForecast>();
   ```
 
-* <xref:System.Net.Http.Json.HttpClientJsonExtensions.PutAsJsonAsync%2A> &ndash; Sends an HTTP PUT request, including JSON-encoded content.
+* <xref:System.Net.Http.Json.HttpClientJsonExtensions.PutAsJsonAsync%2A>: Sends an HTTP PUT request, including JSON-encoded content.
 
   In the following code, `editItem` values for `Name` and `IsCompleted` are provided by bound elements of the component. The item's `Id` is set when the item is selected in another part of the UI and `EditItem` is called. The `SaveItem` method is triggered by selecting the Save `<button>` element. See the sample app for a complete example.
 
@@ -302,7 +302,7 @@ To allow other sites to make cross-origin resource sharing (CORS) requests to yo
 
 ## Additional resources
 
-* <xref:security/blazor/webassembly/additional-scenarios> &ndash; Includes coverage on using <xref:System.Net.Http.HttpClient> to make secure web API requests.
+* <xref:security/blazor/webassembly/additional-scenarios>: Includes coverage on using <xref:System.Net.Http.HttpClient> to make secure web API requests.
 * <xref:fundamentals/http-requests>
 * <xref:security/enforcing-ssl>
 * [Kestrel HTTPS endpoint configuration](xref:fundamentals/servers/kestrel#endpoint-configuration)

aspnetcore/blazor/common/samples/3.x/BlazorServerSample/Shared/NavMenu.razor

@@ -39,12 +39,12 @@
         </li>
         <li class="nav-item px-3">
             <NavLink class="nav-link" href="CascadingValuesParametersTheme">
-                <span class="oi oi-plus" aria-hidden="true"></span> Cascading &ndash; Theme
+                <span class="oi oi-plus" aria-hidden="true"></span> Cascading: Theme
             </NavLink>
         </li>
         <li class="nav-item px-3">
             <NavLink class="nav-link" href="CascadingValuesParametersTabSet">
-                <span class="oi oi-plus" aria-hidden="true"></span> Cascading &ndash; TabSet
+                <span class="oi oi-plus" aria-hidden="true"></span> Cascading: TabSet
             </NavLink>
         </li>
         <li class="nav-item px-3">

aspnetcore/blazor/common/samples/3.x/BlazorWebAssemblySample/Shared/NavMenu.razor

@@ -39,12 +39,12 @@
         </li>
         <li class="nav-item px-3">
             <NavLink class="nav-link" href="CascadingValuesParametersTheme">
-                <span class="oi oi-plus" aria-hidden="true"></span> Cascading &ndash; Theme
+                <span class="oi oi-plus" aria-hidden="true"></span> Cascading: Theme
             </NavLink>
         </li>
         <li class="nav-item px-3">
             <NavLink class="nav-link" href="CascadingValuesParametersTabSet">
-                <span class="oi oi-plus" aria-hidden="true"></span> Cascading &ndash; TabSet
+                <span class="oi oi-plus" aria-hidden="true"></span> Cascading: TabSet
             </NavLink>
         </li>
         <li class="nav-item px-3">

aspnetcore/blazor/components.md

@@ -70,8 +70,8 @@ Razor components in Blazor apps extensively use Razor syntax. If you aren't fami
 
 When accessing the content on Razor syntax, pay special attention to the following sections:
 
-* [Directives](xref:mvc/views/razor#directives) – `@`-prefixed reserved keywords that typically change the way component markup is parsed or function.
-* [Directive attributes](xref:mvc/views/razor#directive-attributes) – `@`-prefixed reserved keywords that typically change the way component elements are parsed or function.
+* [Directives](xref:mvc/views/razor#directives): `@`-prefixed reserved keywords that typically change the way component markup is parsed or function.
+* [Directive attributes](xref:mvc/views/razor#directive-attributes): `@`-prefixed reserved keywords that typically change the way component elements are parsed or function.
 
 ## Static assets
 
@@ -975,7 +975,7 @@ However, inline SVG markup isn't supported in all scenarios. If you place an `<s
 
 ## Additional resources
 
-* <xref:security/blazor/server/threat-mitigation> &ndash; Includes guidance on building Blazor Server apps that must contend with resource exhaustion.
+* <xref:security/blazor/server/threat-mitigation>: Includes guidance on building Blazor Server apps that must contend with resource exhaustion.
 
 <!--Reference links in article-->
 [1]: <xref:mvc/views/razor#code>

aspnetcore/blazor/dependency-injection.md

@@ -131,8 +131,8 @@ The DI system is based on the DI system in ASP.NET Core. For more information, s
 
 After services are added to the service collection, inject the services into the components using the [\@inject](xref:mvc/views/razor#inject) Razor directive. [`@inject`](xref:mvc/views/razor#inject) has two parameters:
 
-* Type – The type of the service to inject.
-* Property – The name of the property receiving the injected app service. The property doesn't require manual creation. The compiler creates the property.
+* Type: The type of the service to inject.
+* Property: The name of the property receiving the injected app service. The property doesn't require manual creation. The compiler creates the property.
 
 For more information, see <xref:mvc/views/dependency-injection>.
 

aspnetcore/blazor/event-handling.md

@@ -84,7 +84,7 @@ Supported <xref:System.EventArgs> are shown in the following table.
 For more information, see the following resources:
 
 * [EventArgs classes in the ASP.NET Core reference source (dotnet/aspnetcore release/3.1 branch)](https://github.com/dotnet/aspnetcore/tree/release/3.1/src/Components/Web/src/Web).
-* [MDN web docs: GlobalEventHandlers](https://developer.mozilla.org/docs/Web/API/GlobalEventHandlers) &ndash; Includes information on which HTML elements support each DOM event.
+* [MDN web docs: GlobalEventHandlers](https://developer.mozilla.org/docs/Web/API/GlobalEventHandlers): Includes information on which HTML elements support each DOM event.
 
 ## Lambda expressions
 

aspnetcore/blazor/hosting-models.md

@@ -96,7 +96,7 @@ A Blazor app is composed of reusable elements of UI called *components*. A compo
 * Turned into HTML text (during prerendering†).
 * Used to efficiently update the markup during regular rendering.
 
-†*Prerendering* – The requested Razor component is compiled on the server into static HTML and sent to the client, where it's rendered to the user. After the connection is made between the client and the server, the component's static prerendered elements are replaced with interactive elements. Prerendering makes the app feel more responsive to the user.
+†*Prerendering*: The requested Razor component is compiled on the server into static HTML and sent to the client, where it's rendered to the user. After the connection is made between the client and the server, the component's static prerendered elements are replaced with interactive elements. Prerendering makes the app feel more responsive to the user.
 
 A UI update in Blazor is triggered by:
 

aspnetcore/blazor/integrate-components.md

@@ -17,10 +17,10 @@ Razor components can be integrated into Razor Pages and MVC apps. When the page
 
 After [preparing the app](#prepare-the-app), use the guidance in the following sections depending on the app's requirements:
 
-* Routable components – For components that are directly routable from user requests. Follow this guidance when visitors should be able to make an HTTP request in their browser for a component with an [`@page`](xref:mvc/views/razor#page) directive.
+* Routable components: For components that are directly routable from user requests. Follow this guidance when visitors should be able to make an HTTP request in their browser for a component with an [`@page`](xref:mvc/views/razor#page) directive.
   * [Use routable components in a Razor Pages app](#use-routable-components-in-a-razor-pages-app)
   * [Use routable components in an MVC app](#use-routable-components-in-an-mvc-app)
-* [Render components from a page or view](#render-components-from-a-page-or-view) – For components that aren't directly routable from user requests. Follow this guidance when the app embeds components into existing pages and views with the [Component Tag Helper](xref:mvc/views/tag-helpers/builtin-th/component-tag-helper).
+* [Render components from a page or view](#render-components-from-a-page-or-view): For components that aren't directly routable from user requests. Follow this guidance when the app embeds components into existing pages and views with the [Component Tag Helper](xref:mvc/views/tag-helpers/builtin-th/component-tag-helper).
 
 ## Prepare the app
 

aspnetcore/blazor/progressive-web-app.md

@@ -113,14 +113,14 @@ The built-in *service-worker.published.js* service worker resolves requests usin
 
 The cache-first strategy is valuable because:
 
-* **It ensures reliability.** – Network access isn't a boolean state. A user isn't simply online or offline:
+* **It ensures reliability.** Network access isn't a boolean state. A user isn't simply online or offline:
 
   * The user's device may assume it's online, but the network might be so slow as to be impractical to wait for.
   * The network might return invalid results for certain URLs, such as when there's a captive WIFI portal that's currently blocking or redirecting certain requests.
 
   This is why the browser's `navigator.onLine` API isn't reliable and shouldn't be depended upon.
 
-* **It ensures correctness.** – When building a cache of offline resources, the service worker uses content hashing to guarantee it has fetched a complete and self-consistent snapshot of resources at a single instant in time. This cache is then used as an atomic unit. There's no point asking the network for newer resources, since the only versions required are the ones already cached. Anything else risks inconsistency and incompatibility (for example, trying to use versions of .NET assemblies that weren't compiled together).
+* **It ensures correctness.** When building a cache of offline resources, the service worker uses content hashing to guarantee it has fetched a complete and self-consistent snapshot of resources at a single instant in time. This cache is then used as an atomic unit. There's no point asking the network for newer resources, since the only versions required are the ones already cached. Anything else risks inconsistency and incompatibility (for example, trying to use versions of .NET assemblies that weren't compiled together).
 
 ### Background updates
 

aspnetcore/blazor/routing.md

@@ -169,8 +169,8 @@ The following `NavMenu` component creates a [Bootstrap](https://getbootstrap.com
 
 There are two <xref:Microsoft.AspNetCore.Components.Routing.NavLinkMatch> options that you can assign to the `Match` attribute of the `<NavLink>` element:
 
-* <xref:Microsoft.AspNetCore.Components.Routing.NavLinkMatch.All?displayProperty=nameWithType> &ndash; The <xref:Microsoft.AspNetCore.Components.Routing.NavLink> is active when it matches the entire current URL.
-* <xref:Microsoft.AspNetCore.Components.Routing.NavLinkMatch.Prefix?displayProperty=nameWithType> (*default*) &ndash; The <xref:Microsoft.AspNetCore.Components.Routing.NavLink> is active when it matches any prefix of the current URL.
+* <xref:Microsoft.AspNetCore.Components.Routing.NavLinkMatch.All?displayProperty=nameWithType>: The <xref:Microsoft.AspNetCore.Components.Routing.NavLink> is active when it matches the entire current URL.
+* <xref:Microsoft.AspNetCore.Components.Routing.NavLinkMatch.Prefix?displayProperty=nameWithType> (*default*): The <xref:Microsoft.AspNetCore.Components.Routing.NavLink> is active when it matches any prefix of the current URL.
 
 In the preceding example, the Home <xref:Microsoft.AspNetCore.Components.Routing.NavLink> `href=""` matches the home URL and only receives the `active` CSS class at the app's default base path URL (for example, `https://localhost:5001/`). The second <xref:Microsoft.AspNetCore.Components.Routing.NavLink> receives the `active` class when the user visits any URL with a `MyComponent` prefix (for example, `https://localhost:5001/MyComponent` and `https://localhost:5001/MyComponent/AnotherSegment`).
 
@@ -245,7 +245,7 @@ public void Dispose()
 
 <xref:Microsoft.AspNetCore.Components.Routing.LocationChangedEventArgs> provides the following information about the event:
 
-* <xref:Microsoft.AspNetCore.Components.Routing.LocationChangedEventArgs.Location> &ndash; The URL of the new location.
-* <xref:Microsoft.AspNetCore.Components.Routing.LocationChangedEventArgs.IsNavigationIntercepted> &ndash; If `true`, Blazor intercepted the navigation from the browser. If `false`, <xref:Microsoft.AspNetCore.Components.NavigationManager.NavigateTo%2A?displayProperty=nameWithType> caused the navigation to occur.
+* <xref:Microsoft.AspNetCore.Components.Routing.LocationChangedEventArgs.Location>: The URL of the new location.
+* <xref:Microsoft.AspNetCore.Components.Routing.LocationChangedEventArgs.IsNavigationIntercepted>: If `true`, Blazor intercepted the navigation from the browser. If `false`, <xref:Microsoft.AspNetCore.Components.NavigationManager.NavigateTo%2A?displayProperty=nameWithType> caused the navigation to occur.
 
 For more information on component disposal, see <xref:blazor/lifecycle#component-disposal-with-idisposable>.

aspnetcore/blazor/state-management.md

@@ -47,8 +47,8 @@ To preserve state beyond a single circuit, *don't merely store the data in the s
 
 Data persistence is typically only required for high-value state that users have expended effort to create. In the following examples, persisting state either saves time or aids in commercial activities:
 
-* Multistep webform – It's time-consuming for a user to re-enter data for several completed steps of a multistep process if their state is lost. A user loses state in this scenario if they navigate away from the multistep form and return to the form later.
-* Shopping cart – Any commercially important component of an app that represents potential revenue can be maintained. A user who loses their state, and thus their shopping cart, may purchase fewer products or services when they return to the site later.
+* Multistep webform: It's time-consuming for a user to re-enter data for several completed steps of a multistep process if their state is lost. A user loses state in this scenario if they navigate away from the multistep form and return to the form later.
+* Shopping cart: Any commercially important component of an app that represents potential revenue can be maintained. A user who loses their state, and thus their shopping cart, may purchase fewer products or services when they return to the site later.
 
 It's usually not necessary to preserve easily-recreated state, such as the username entered into a sign-in dialog that hasn't been submitted.