diff --git a/blazor-features/BlazorSections/BlazorWasmApp/BlazorWasmApp.csproj b/blazor-features/BlazorSections/BlazorWasmApp/BlazorWasmApp.csproj
index a7dbcaa5bd..82d74552ed 100644
--- a/blazor-features/BlazorSections/BlazorWasmApp/BlazorWasmApp.csproj
+++ b/blazor-features/BlazorSections/BlazorWasmApp/BlazorWasmApp.csproj
@@ -1,14 +1,14 @@
 <Project Sdk="Microsoft.NET.Sdk.BlazorWebAssembly">
 
     <PropertyGroup>
-        <TargetFramework>net8.0</TargetFramework>
+        <TargetFramework>net10.0</TargetFramework>
         <Nullable>enable</Nullable>
         <ImplicitUsings>enable</ImplicitUsings>
     </PropertyGroup>
 
     <ItemGroup>
-        <PackageReference Include="Microsoft.AspNetCore.Components.WebAssembly" Version="8.0.0"/>
-        <PackageReference Include="Microsoft.AspNetCore.Components.WebAssembly.DevServer" Version="8.0.0" PrivateAssets="all"/>
+        <PackageReference Include="Microsoft.AspNetCore.Components.WebAssembly" Version="10.0.10"/>
+        <PackageReference Include="Microsoft.AspNetCore.Components.WebAssembly.DevServer" Version="10.0.10" PrivateAssets="all"/>
     </ItemGroup>
 
 </Project>
diff --git a/blazor-features/BlazorSections/README.md b/blazor-features/BlazorSections/README.md
new file mode 100644
index 0000000000..f12c328374
--- /dev/null
+++ b/blazor-features/BlazorSections/README.md
@@ -0,0 +1,9 @@
+# Blazor Sections
+
+Sample project for the "Blazor Sections: SectionOutlet and SectionContent" article.
+
+Standard Blazor WebAssembly Standalone App template (`net10.0`). The app has no server-rendering
+component, so it runs entirely in the browser under `InteractiveWebAssembly`-equivalent
+client-side rendering — there is only one render mode in play, which is why `SectionOutlet` and
+`SectionContent` resolve without the layout/page render-mode mismatch the article's "Interactive
+Render Modes" section describes for Blazor Web Apps.