Updated the incorrect list bullets

.github/ISSUE_TEMPLATE/doc-request.md

@@ -5,12 +5,12 @@ about: Request a new topic to help us improve
 
 **Help us make content visible**
 
-- Tell us what search terms you used and how you searched docs.
-- Tell us what docs you found that didn't address your concern.
+* Tell us what search terms you used and how you searched docs.
+* Tell us what docs you found that didn't address your concern.
 
 **Describe the new topic**
 
-- Explain why this topic is needed.
-- Suggest a location in the Table of Contents.
-- Write an abstract. In one **short** paragraph, describe what this topic will cover.
-- Create an outline for the new topic. We'll help review the outline and approve it before anyone writes a topic.
+* Explain why this topic is needed.
+* Suggest a location in the Table of Contents.
+* Write an abstract. In one **short** paragraph, describe what this topic will cover.
+* Create an outline for the new topic. We'll help review the outline and approve it before anyone writes a topic.

aspnetcore/data/ef-rp/intro/samples/cu/wwwroot/lib/bootstrap/ISSUE_TEMPLATE.md

@@ -1,22 +1,22 @@
 Before opening an issue:
 
-- [Search for duplicate or closed issues](https://github.com/twbs/bootstrap/issues?utf8=%E2%9C%93&q=is%3Aissue)
-- [Validate](http://validator.w3.org/nu/) and [lint](https://github.com/twbs/bootlint#in-the-browser) any HTML to avoid common problems
-- Prepare a [reduced test case](https://css-tricks.com/reduced-test-cases/) for any bugs
-- Read the [contributing guidelines](https://github.com/twbs/bootstrap/blob/master/CONTRIBUTING.md)
+* [Search for duplicate or closed issues](https://github.com/twbs/bootstrap/issues?utf8=%E2%9C%93&q=is%3Aissue)
+* [Validate](http://validator.w3.org/nu/) and [lint](https://github.com/twbs/bootlint#in-the-browser) any HTML to avoid common problems
+* Prepare a [reduced test case](https://css-tricks.com/reduced-test-cases/) for any bugs
+* Read the [contributing guidelines](https://github.com/twbs/bootstrap/blob/master/CONTRIBUTING.md)
 
 When asking general "how to" questions:
 
-- Please do not open an issue here
-- Instead, ask for help on [StackOverflow, IRC, or Slack](https://github.com/twbs/bootstrap/blob/master/README.md#community)
+* Please do not open an issue here
+* Instead, ask for help on [StackOverflow, IRC, or Slack](https://github.com/twbs/bootstrap/blob/master/README.md#community)
 
 When reporting a bug, include:
 
-- Operating system and version (Windows, Mac OS X, Android, iOS, Win10 Mobile)
-- Browser and version (Chrome, Firefox, Safari, IE, MS Edge, Opera 15+, Android Browser)
-- Reduced test cases and potential fixes using [JS Bin](https://jsbin.com)
+* Operating system and version (Windows, Mac OS X, Android, iOS, Win10 Mobile)
+* Browser and version (Chrome, Firefox, Safari, IE, MS Edge, Opera 15+, Android Browser)
+* Reduced test cases and potential fixes using [JS Bin](https://jsbin.com)
 
 When suggesting a feature, include:
 
-- As much detail as possible for what we should add and why it's important to Bootstrap
-- Relevant links to prior art, screenshots, or live demos whenever possible
+* As much detail as possible for what we should add and why it's important to Bootstrap
+* Relevant links to prior art, screenshots, or live demos whenever possible

aspnetcore/data/scaffold_RP.md

@@ -33,9 +33,9 @@ To launch the interactive tool, run `dotnet scaffold`. The UI changes as more fe
 
 To navigate the UI, use the:
 
-- Up and down arrow keys to navigate the menu items.
-- Enter key to select the highlighted menu item.
-- Select and enter **Back** to return to the previous menu.
+* Up and down arrow keys to navigate the menu items.
+* Enter key to select the highlighted menu item.
+* Select and enter **Back** to return to the previous menu.
 
 ## Create and scaffold a data model in a Razor Pages project
 
@@ -59,11 +59,11 @@ If you have any problems with the following steps, see [Tutorial: Create a Razor
 
   The `dotnet scaffold` tool makes the following changes to the project files:
 
-- A package reference is added for Entity Framework.
-- `Program.cs` is updated to initialize the database connection.
-- `appsettings.json` is updated with connection information.
-- `ContactDbContext.cs` is created and added to the project root directory.
-- Razor Pages for CRUD operations are added to the Pages folder.
+* A package reference is added for Entity Framework.
+* `Program.cs` is updated to initialize the database connection.
+* `appsettings.json` is updated with connection information.
+* `ContactDbContext.cs` is created and added to the project root directory.
+* Razor Pages for CRUD operations are added to the Pages folder.
 
 The content has been generated but the database isn't initialized. Run the following commands to initialize the DB.
 
@@ -75,10 +75,10 @@ dotnet ef database update
 ```
 
 In  The preceding commands:
-- `dotnet tool uninstall --global dotnet-ef` uninstalls the `dotnet-ef` tool. Uninstalling ensures the latest tool is successfully installed. If `dotnet-ef` isn't installed, an error messages **A tool with the package Id 'dotnet-ef' could not be found.** You can ignore this message.
-- `dotnet tool install --global dotnet-ef` installs globally the `dotnet-ef` tool.
-- `dotnet ef migrations add initialMigration` adds the initial migration. For more information, see [Create the initial database schema using EF's migration feature](/aspnet/core/tutorials/razor-pages/model&tabs=visual-studio-code)
-- `dotnet ef database update` applies the migrations to the database.
+* `dotnet tool uninstall --global dotnet-ef` uninstalls the `dotnet-ef` tool. Uninstalling ensures the latest tool is successfully installed. If `dotnet-ef` isn't installed, an error messages **A tool with the package Id 'dotnet-ef' could not be found.** You can ignore this message.
+* `dotnet tool install --global dotnet-ef` installs globally the `dotnet-ef` tool.
+* `dotnet ef migrations add initialMigration` adds the initial migration. For more information, see [Create the initial database schema using EF's migration feature](/aspnet/core/tutorials/razor-pages/model&tabs=visual-studio-code)
+* `dotnet ef database update` applies the migrations to the database.
 
 Run the app:
 
@@ -91,7 +91,7 @@ Run the app:
 
 ## Additional resources
 
-- [dotnet scaffold repo on GitHub](https://github.com/dotnet/Scaffolding)
-- [How to manage .NET tools](/dotnet/core/tools/global-tools)
-- [Microsoft.dotnet-scaffold](https://www.nuget.org/packages/Microsoft.dotnet-scaffold) NuGet package.
-- [Detailed tutorial on EF scaffolding Razor Pages](/aspnet/core/data/scaffold_rp)
+* [dotnet scaffold repo on GitHub](https://github.com/dotnet/Scaffolding)
+* [How to manage .NET tools](/dotnet/core/tools/global-tools)
+* [Microsoft.dotnet-scaffold](https://www.nuget.org/packages/Microsoft.dotnet-scaffold) NuGet package.
+* [Detailed tutorial on EF scaffolding Razor Pages](/aspnet/core/data/scaffold_rp)

aspnetcore/diagnostics/mvc1000.md

@@ -24,8 +24,8 @@ Rendering a partial using `IHtmlHelper.Partial` or `IHtmlHelper.RenderPartial` e
 
 ## How to fix violations
 
-- Use the <xref:Microsoft.AspNetCore.Mvc.TagHelpers.PartialTagHelper>
-- Use the <xref:Microsoft.AspNetCore.Mvc.Rendering.HtmlHelperPartialExtensions.PartialAsync%2A> or <xref:Microsoft.AspNetCore.Mvc.Rendering.HtmlHelperPartialExtensions.RenderPartialAsync%2A>
+* Use the <xref:Microsoft.AspNetCore.Mvc.TagHelpers.PartialTagHelper>
+* Use the <xref:Microsoft.AspNetCore.Mvc.Rendering.HtmlHelperPartialExtensions.PartialAsync%2A> or <xref:Microsoft.AspNetCore.Mvc.Rendering.HtmlHelperPartialExtensions.RenderPartialAsync%2A>
 
 ## When to suppress warnings
 

aspnetcore/fundamentals/apis.md

@@ -34,12 +34,12 @@ Both API projects refer to the following class:
 
 Minimal APIs have many of the same capabilities as controller-based APIs. They support the configuration and customization needed to scale to multiple APIs, handle complex routes, apply authorization rules, and control the content of API responses. There are a few capabilities available with controller-based APIs that are not yet supported or implemented by minimal APIs. These include:
 
-- No built-in support for model binding (<xref:Microsoft.AspNetCore.Mvc.ModelBinding.IModelBinderProvider>, <xref:Microsoft.AspNetCore.Mvc.ModelBinding.IModelBinder>). Support can be added with a custom binding shim.
-- No built-in support for validation (<xref:Microsoft.AspNetCore.Mvc.ModelBinding.Validation.IModelValidator>).
-- No support for [application parts](xref:mvc/extensibility/app-parts) or the [application model](xref:mvc/controllers/application-model). There's no way to apply or build your own conventions.
-- No built-in view rendering support. We recommend using [Razor Pages](xref:tutorials/razor-pages/razor-pages-start) for rendering views.
-- No support for [JsonPatch](https://www.nuget.org/packages/Microsoft.AspNetCore.JsonPatch/)
-- No support for [OData](https://www.nuget.org/packages/Microsoft.AspNetCore.OData/)
+* No built-in support for model binding (<xref:Microsoft.AspNetCore.Mvc.ModelBinding.IModelBinderProvider>, <xref:Microsoft.AspNetCore.Mvc.ModelBinding.IModelBinder>). Support can be added with a custom binding shim.
+* No built-in support for validation (<xref:Microsoft.AspNetCore.Mvc.ModelBinding.Validation.IModelValidator>).
+* No support for [application parts](xref:mvc/extensibility/app-parts) or the [application model](xref:mvc/controllers/application-model). There's no way to apply or build your own conventions.
+* No built-in view rendering support. We recommend using [Razor Pages](xref:tutorials/razor-pages/razor-pages-start) for rendering views.
+* No support for [JsonPatch](https://www.nuget.org/packages/Microsoft.AspNetCore.JsonPatch/)
+* No support for [OData](https://www.nuget.org/packages/Microsoft.AspNetCore.OData/)
 
 ## See also
 

aspnetcore/fundamentals/includes/apis6.md

@@ -20,13 +20,13 @@ Both API projects refer to the following class:
 
 Minimal APIs have many of the same capabilities as controller-based APIs. They support the configuration and customization needed to scale to multiple APIs, handle complex routes, apply authorization rules, and control the content of API responses. There are a few capabilities available with controller-based APIs that are not yet supported or implemented by minimal APIs. These include:
 
-- No built-in support for model binding (<xref:Microsoft.AspNetCore.Mvc.ModelBinding.IModelBinderProvider>, <xref:Microsoft.AspNetCore.Mvc.ModelBinding.IModelBinder>). Support can be added with a custom binding shim.
-- No support for binding from forms. This includes binding <xref:Microsoft.AspNetCore.Http.IFormFile>.
-- No built-in support for validation (<xref:Microsoft.AspNetCore.Mvc.ModelBinding.Validation.IModelValidator>).
-- No support for [application parts](xref:mvc/extensibility/app-parts) or the [application model](xref:mvc/controllers/application-model). There's no way to apply or build your own conventions.
-- No built-in view rendering support. We recommend using [Razor Pages](xref:tutorials/razor-pages/razor-pages-start) for rendering views.
-- No support for [JsonPatch](https://www.nuget.org/packages/Microsoft.AspNetCore.JsonPatch/)
-- No support for [OData](https://www.nuget.org/packages/Microsoft.AspNetCore.OData/)
+* No built-in support for model binding (<xref:Microsoft.AspNetCore.Mvc.ModelBinding.IModelBinderProvider>, <xref:Microsoft.AspNetCore.Mvc.ModelBinding.IModelBinder>). Support can be added with a custom binding shim.
+* No support for binding from forms. This includes binding <xref:Microsoft.AspNetCore.Http.IFormFile>.
+* No built-in support for validation (<xref:Microsoft.AspNetCore.Mvc.ModelBinding.Validation.IModelValidator>).
+* No support for [application parts](xref:mvc/extensibility/app-parts) or the [application model](xref:mvc/controllers/application-model). There's no way to apply or build your own conventions.
+* No built-in view rendering support. We recommend using [Razor Pages](xref:tutorials/razor-pages/razor-pages-start) for rendering views.
+* No support for [JsonPatch](https://www.nuget.org/packages/Microsoft.AspNetCore.JsonPatch/)
+* No support for [OData](https://www.nuget.org/packages/Microsoft.AspNetCore.OData/)
 
 ## See also
 

aspnetcore/fundamentals/minimal-apis/security.md

@@ -51,8 +51,8 @@ In some cases, such as controlling middleware order, it's necessary to explicitl
 
 Authentication strategies typically support a variety of configurations that are loaded via options. Minimal apps support loading options from configuration for the following authentication strategies:
 
-- [JWT bearer-based](https://jwt.io/introduction)
-- [OpenID Connection-based](https://openid.net/developers/how-connect-works/)
+* [JWT bearer-based](https://jwt.io/introduction)
+* [OpenID Connection-based](https://openid.net/developers/how-connect-works/)
 
 The ASP.NET Core framework expects to find these options under the `Authentication:Schemes:{SchemeName}` section in [configuration](/aspnet/core/fundamentals/configuration). In the following sample, two different schemes, `Bearer` and `LocalAuthIssuer`, are defined with their respective options. The `Authentication:DefaultScheme` option can be used to configure the default authentication strategy that's used.
 
@@ -102,13 +102,13 @@ Configuring authorization requirements on a resource is a two-step process that
 
 In the following code, <xref:Microsoft.Extensions.DependencyInjection.PolicyServiceCollectionExtensions.AddAuthorizationBuilder%2A> is invoked which:
 
-- Adds authorization-related services to the DI container.
-- Returns an <xref:Microsoft.AspNetCore.Authorization.AuthorizationBuilder> that can be used to directly register authorization policies.
+* Adds authorization-related services to the DI container.
+* Returns an <xref:Microsoft.AspNetCore.Authorization.AuthorizationBuilder> that can be used to directly register authorization policies.
 
 The code creates a new authorization policy, named `admin_greetings`, that encapsulates two authorization requirements:
 
-- A role-based requirement via <xref:Microsoft.AspNetCore.Authorization.AuthorizationPolicyBuilder.RequireRole%2A> for users with an `admin` role.
-- A claim-based requirement via <xref:Microsoft.AspNetCore.Authorization.AuthorizationPolicyBuilder.RequireClaim%2A> that the user must provide a `greetings_api` scope claim.
+* A role-based requirement via <xref:Microsoft.AspNetCore.Authorization.AuthorizationPolicyBuilder.RequireRole%2A> for users with an `admin` role.
+* A claim-based requirement via <xref:Microsoft.AspNetCore.Authorization.AuthorizationPolicyBuilder.RequireClaim%2A> that the user must provide a `greetings_api` scope claim.
 
 The `admin_greetings` policy is provided as a required policy to the `/hello` endpoint.
 

aspnetcore/fundamentals/openapi/include-metadata.md

@@ -516,9 +516,9 @@ public record Todo(
 In a class, struct, or record, properties with the [`[Required]`](xref:System.ComponentModel.DataAnnotations.RequiredAttribute) attribute or [required](/dotnet/csharp/language-reference/proposals/csharp-11.0/required-members#required-modifier) modifier are always `required` in the corresponding schema.
 
 Other properties may also be required based on the constructors (implicit and explicit) for the class, struct, or record.
-- For a class or record class with a single public constructor, any property with the same type and name (case-insensitive match) as a parameter to the constructor is required in the corresponding schema.
-- For a class or record class with multiple public constructors, no other properties are required.
-- For a struct or record struct, no other properties are required since C# always defines an implicit parameterless constructor for a struct.
+* For a class or record class with a single public constructor, any property with the same type and name (case-insensitive match) as a parameter to the constructor is required in the corresponding schema.
+* For a class or record class with multiple public constructors, no other properties are required.
+* For a struct or record struct, no other properties are required since C# always defines an implicit parameterless constructor for a struct.
 
 #### enum