Fix typo and add missing backticks for environment names

Co-authored-by: guardrex <1622880+guardrex@users.noreply.github.com>

Author: Copilot

aspnetcore/fundamentals/error-handling.md

@@ -96,7 +96,7 @@ The following example shows how to register an `IExceptionHandler` implementatio
 
 :::code language="csharp" source="~/fundamentals/error-handling/samples/8.x/ErrorHandlingSample/Program.cs" id="snippet_RegisterIExceptionHandler" highlight="7":::
 
-When the preceding code runs in the `Development` environmentnt:
+When the preceding code runs in the `Development` environment:
 
 * The `CustomExceptionHandler` is called first to handle an exception.
 * After logging the exception, the `TryHandleAsync` method returns `false`, so the [developer exception page](#developer-exception-page) is shown.

aspnetcore/fundamentals/static-files.md

@@ -152,7 +152,7 @@ To disable this behavior, set `EnableStaticAssetsDevelopmentCaching` to `true` i
 
 ## Static files in non-`Development` environments
 
-When running an app locally, static web assets are only enabled in the `Development` environment. To enable static files for environments other than Development during local development and testing (for example, in the `Staging` environment), call <xref:Microsoft.AspNetCore.Hosting.WebHostBuilderExtensions.UseStaticWebAssets%2A> on the <xref:Microsoft.AspNetCore.Builder.WebApplicationBuilder>.
+When running an app locally, static web assets are only enabled in the `Development` environment. To enable static files for environments other than `Development` during local development and testing (for example, in the `Staging` environment), call <xref:Microsoft.AspNetCore.Hosting.WebHostBuilderExtensions.UseStaticWebAssets%2A> on the <xref:Microsoft.AspNetCore.Builder.WebApplicationBuilder>.
 
 > [!WARNING]
 > Call <xref:Microsoft.AspNetCore.Hosting.WebHostBuilderExtensions.UseStaticWebAssets%2A> for the ***exact environment*** to prevent activating the feature in production, as it serves files from separate locations on disk *other than from the project*. The example in this section checks for the `Staging` environment with <xref:Microsoft.Extensions.Hosting.HostEnvironmentEnvExtensions.IsStaging%2A>.
@@ -171,7 +171,7 @@ if (builder.Environment.IsStaging())
 When <xref:Microsoft.AspNetCore.Hosting.IWebHostEnvironment.WebRootPath%2A?displayProperty=nameWithType> is set to a folder other than `wwwroot`, the following default behaviors are exhibited:
 
 * In the `Development` environment, static assets are served from `wwwroot` if assets with the same name are in both `wwwroot` and a different folder assigned to <xref:Microsoft.AspNetCore.Hosting.IWebHostEnvironment.WebRootPath%2A>.
-* In any environment other than development, duplicate static assets are served from the <xref:Microsoft.AspNetCore.Hosting.IWebHostEnvironment.WebRootPath%2A> folder.
+* In any environment other than `Development`, duplicate static assets are served from the <xref:Microsoft.AspNetCore.Hosting.IWebHostEnvironment.WebRootPath%2A> folder.
 
 Consider a web app created from the empty web template:
 
@@ -189,7 +189,7 @@ var builder = WebApplication.CreateBuilder(new WebApplicationOptions
 By default, for requests to `/`:
 
 * In the `Development` environment, `wwwroot/Index.html` is returned.
-* In any environment other than development, `wwwroot-custom/Index.html` is returned.
+* In any environment other than `Development`, `wwwroot-custom/Index.html` is returned.
 
 To ensure assets from `wwwroot-custom` are always returned, use ***one*** of the following approaches: