Clarification in Blazor WASM section (#20237)

Author: guardrex

aspnetcore/migration/31-to-50.md

@@ -4,7 +4,7 @@ author: scottaddie
 description: Learn how to migrate an ASP.NET Core 3.1 project to ASP.NET Core 5.0.
 ms.author: scaddie
 ms.custom: mvc
-ms.date: 10/16/2020
+ms.date: 10/20/2020
 no-loc: ["ASP.NET Core Identity", cookie, Cookie, Blazor, "Blazor Server", "Blazor WebAssembly", "Identity", "Let's Encrypt", Razor, SignalR]
 uid: migration/31-to-50
 ---
@@ -63,7 +63,7 @@ If updating a Blazor WebAssembly project, skip to the [Update Blazor WebAssembly
 
 ## Update Blazor WebAssembly projects
 
-For Blazor WebAssembly projects, apply the following changes in the project file:
+For Blazor WebAssembly projects, including the *`Client`* project of a hosted Blazor solution, apply the following changes to the project file:
 
 1. Update the SDK from `Microsoft.NET.Sdk.Web` to `Microsoft.NET.Sdk.BlazorWebAssembly`:
 
@@ -90,6 +90,9 @@ For Blazor WebAssembly projects, apply the following changes in the project file
     <ItemGroup>
     -    <PackageReference Include="Microsoft.AspNetCore.Components.WebAssembly.Build" Version="3.2.1" PrivateAssets="all" />
     ```
+    
+> [!NOTE]
+> Update the *`Server`* project of a hosted Blazor solution as an ASP.NET Core app following the general guidance in this article.
 
 ## Update package references