Split components followup (dotnet#17004)

Author: guardrex

aspnetcore/blazor/advanced-scenarios.md

@@ -74,7 +74,7 @@ In the following example, the loop in the `CreateComponent` method generates thr
 
 ### Sequence numbers relate to code line numbers and not execution order
 
-Razor component files (*.razor*) are always compiled. Compilation is potentially a great advantage over interpreting code because the compile step can be used to inject information that improves app performance at runtime.
+Razor component files (*.razor*) are always compiled. Compilation is a potential advantage over interpreting code because the compile step can be used to inject information that improves app performance at runtime.
 
 A key example of these improvements involves *sequence numbers*. Sequence numbers indicate to the runtime which outputs came from which distinct and ordered lines of code. The runtime uses this information to generate efficient tree diffs in linear time, which is far faster than is normally possible for a general tree diff algorithm.
 

aspnetcore/blazor/event-handling.md

@@ -62,7 +62,7 @@ In the following example, `UpdateHeading` is called asynchronously when the butt
 
 ## Event argument types
 
-For some events, event argument types are permitted. If access to one of these event types isn't necessary, it isn't required in the method call.
+For some events, event argument types are permitted. Specifying an event type in the method call is only necessary if the event type is used in the method.
 
 Supported `EventArgs` are shown in the following table.
 

aspnetcore/blazor/globalization-localization.md

@@ -155,3 +155,7 @@ The following component shows an example of how to perform the initial redirecti
     }
 }
 ```
+
+## Additional resources
+
+* <xref:fundamentals/localization>

aspnetcore/blazor/integrate-components.md

@@ -31,7 +31,7 @@ An existing Razor Pages or MVC app can integrate Razor components into pages and
 
      The *_Layout.cshtml* file is located in the *Pages/Shared* folder in a Razor Pages app or *Views/Shared* folder in an MVC app.
 
-   * Add a `<script>` tag for the *blazor.server.js* script right before of the closing `</body>` tag:
+   * Add a `<script>` tag for the *blazor.server.js* script immediately before of the closing `</body>` tag:
 
      ```html
      <script src="_framework/blazor.server.js"></script>
@@ -41,7 +41,7 @@ An existing Razor Pages or MVC app can integrate Razor components into pages and
 
 1. Add an *_Imports.razor* file to the root folder of the project with the following content (change the last namespace, `MyAppNamespace`, to the namespace of the app):
 
-   ```csharp
+   ```razor
    @using System.Net.Http
    @using Microsoft.AspNetCore.Authorization
    @using Microsoft.AspNetCore.Components.Authorization
@@ -74,7 +74,7 @@ To support routable Razor components in Razor Pages apps:
 
 1. Follow the guidance in the [Prepare the app to use components in pages and views](#prepare-the-app-to-use-components-in-pages-and-views) section.
 
-1. Add an *App.razor* file to the root of the project with the following content:
+1. Add an *App.razor* file to the project root with the following content:
 
    ```razor
    @using Microsoft.AspNetCore.Components.Routing
@@ -205,7 +205,7 @@ When using a custom folder to hold the app's components, add the namespace repre
 * Change `MyAppNamespace` to the app's namespace.
 * If a folder named *Components* isn't used to hold the components, change `Components` to the folder where the components reside.
 
-```csharp
+```cshtml
 @using MyAppNamespace.Components
 ```