Small article improvements (#34919)

Author: guardrex

aspnetcore/blazor/components/render-components-outside-of-aspnetcore.md

@@ -16,17 +16,22 @@ uid: blazor/components/render-outside-of-aspnetcore
 
 In the following example, a Razor component is rendered to an HTML string from a console app:
 
-In a command shell, create a new console app project:
+In a command shell, create a new console app project and change the directory to the `ConsoleApp1` folder:
 
 ```dotnetcli
 dotnet new console -o ConsoleApp1
 cd ConsoleApp1
 ```
 
-In a command shell in the `ConsoleApp1` folder, add package references for <xref:Microsoft.AspNetCore.Components.Web?displayProperty=fullName> and <xref:Microsoft.Extensions.Logging?displayProperty=fullName> to the console app:
+Add a package reference for <xref:Microsoft.AspNetCore.Components.Web?displayProperty=fullName>:
 
 ```dotnetcli
 dotnet add package Microsoft.AspNetCore.Components.Web
+```
+
+Add a package reference for <xref:Microsoft.Extensions.Logging?displayProperty=fullName>:
+
+```dotnetcli
 dotnet add package Microsoft.Extensions.Logging
 ```
 
@@ -48,17 +53,15 @@ Add the following `RenderMessage` component to the project.
 
 @code {
     [Parameter]
-    public string Message { get; set; }
+    public string? Message { get; set; }
 }
 ```
 
-Update the `Program` file:
+Replace the code in the `Program` file with the following code:
 
 * Set up dependency injection (<xref:Microsoft.Extensions.DependencyInjection.IServiceCollection>/<xref:Microsoft.Extensions.DependencyInjection.ServiceCollectionContainerBuilderExtensions.BuildServiceProvider%2A>) and logging (<xref:Microsoft.Extensions.DependencyInjection.LoggingServiceCollectionExtensions.AddLogging%2A>/<xref:Microsoft.Extensions.Logging.ILoggerFactory>).
 * Create an <xref:Microsoft.AspNetCore.Components.Web.HtmlRenderer> and render the `RenderMessage` component by calling <xref:Microsoft.AspNetCore.Components.Web.HtmlRenderer.RenderComponentAsync%2A>.
 
-Any calls to <xref:Microsoft.AspNetCore.Components.Web.HtmlRenderer.RenderComponentAsync%2A> must be made in the context of calling `InvokeAsync` on a component dispatcher. A component dispatcher is available from the <xref:Microsoft.AspNetCore.Components.Web.HtmlRenderer.Dispatcher?displayProperty=nameWithType> property.
-
 ```csharp
 using Microsoft.AspNetCore.Components;
 using Microsoft.AspNetCore.Components.Web;
@@ -93,6 +96,8 @@ Console.WriteLine(html);
 > [!NOTE]
 > Pass <xref:Microsoft.AspNetCore.Components.ParameterView.Empty?displayProperty=nameWithType> to <xref:Microsoft.AspNetCore.Components.Web.HtmlRenderer.RenderComponentAsync%2A> when rendering the component without passing parameters.
 
+Any calls to <xref:Microsoft.AspNetCore.Components.Web.HtmlRenderer.RenderComponentAsync%2A> must be made in the context of calling `InvokeAsync` on a component dispatcher. A component dispatcher is available from the <xref:Microsoft.AspNetCore.Components.Web.HtmlRenderer.Dispatcher?displayProperty=nameWithType> property.
+
 Alternatively, you can write the HTML to a <xref:System.IO.TextWriter> by calling `output.WriteHtmlTo(textWriter)`.
 
 The task returned by <xref:Microsoft.AspNetCore.Components.Web.HtmlRenderer.RenderComponentAsync%2A> completes when the component is fully rendered, including completing any asynchronous lifecycle methods. If you want to observe the rendered HTML earlier, call <xref:Microsoft.AspNetCore.Components.Web.HtmlRenderer.BeginRenderingComponent%2A> instead. Then, wait for the component rendering to complete by awaiting <xref:Microsoft.AspNetCore.Components.Web.HtmlRendering.HtmlRootComponent.QuiescenceTask%2A?displayProperty=nameWithType> on the returned <xref:Microsoft.AspNetCore.Components.Web.HtmlRendering.HtmlRootComponent> instance.