adding per-page metadata descriptions

Author: anupras-mohapatra-arm

content/learning-paths/servers-and-cloud-computing/dotnet-migration-nopcommerce/2-environment-setup.md

@@ -1,5 +1,6 @@
 ---
 title: Set up an Arm-based environment
+description: Set up an Ubuntu Azure Cobalt VM with Docker, .NET 9, and PostgreSQL so you can build and validate nopCommerce on Arm.
 weight: 2
 
 ### FIXED, DO NOT MODIFY
@@ -79,4 +80,4 @@ The `docker exec` command should print `CREATE EXTENSION`. If it prints `NOTICE:
 
 You've set up an Arm-based environment by creating a Microsoft Azure VM powered by Cobalt 100 and installing the toolchain necessary for migration. 
 
-Next, you'll create a reproducible baseline to use for benchmarking.
+Next, you'll create a reproducible baseline to use for benchmarking.

content/learning-paths/servers-and-cloud-computing/dotnet-migration-nopcommerce/3-checkout-build-baseline.md

@@ -1,5 +1,6 @@
 ---
 title: Create a nopCommerce endpoint benchmark baseline on Arm
+description: Build a pinned nopCommerce release on Arm and run a repeatable endpoint benchmark to create a baseline for later tuning.
 weight: 3
 
 ### FIXED, DO NOT MODIFY
@@ -237,4 +238,3 @@ You've now created a baseline before migrating the application.
 
 Next, you'll audit dependencies before migration. 
 
-

content/learning-paths/servers-and-cloud-computing/dotnet-migration-nopcommerce/4-dependency-mapping-manifests.md

@@ -1,5 +1,6 @@
 ---
 title: Generate an SBOM and run .NET dependency discovery before migration
+description: Audit .NET dependencies, generate a CycloneDX SBOM, and inspect native package payloads before migrating nopCommerce to Arm.
 weight: 4
 
 ### FIXED, DO NOT MODIFY
@@ -71,4 +72,4 @@ You must resolve B first, then validate A, then validate the app.
 
 You've reviewed application dependencies to understand what can change when you migrate to Arm.
 
-Next, you'll explore options to containerize the application. 
+Next, you'll explore options to containerize the application.

content/learning-paths/servers-and-cloud-computing/dotnet-migration-nopcommerce/5-containerization.md

@@ -1,5 +1,6 @@
 ---
 title: Choose a containerization path for the nopCommerce application
+description: Compare Dockerfile and .NET SDK container publish workflows so you can choose a reproducible arm64 container path for nopCommerce.
 weight: 5
 
 ### FIXED, DO NOT MODIFY

content/learning-paths/servers-and-cloud-computing/dotnet-migration-nopcommerce/6-deploy-verify-cobalt.md

@@ -1,5 +1,6 @@
 ---
 title: Tune the performance of the .NET application on Azure
+description: Apply .NET runtime tuning on Azure Cobalt and compare endpoint benchmark results to decide whether a profile improves nopCommerce performance.
 weight: 6
 
 ### FIXED, DO NOT MODIFY
@@ -99,4 +100,3 @@ When interpreting metric improvements, consider the following:
 You've applied performance tuning changes to the .NET application. 
 
 Next, you'll use the Arm MCP Server to optimize application performance.
-

content/learning-paths/servers-and-cloud-computing/dotnet-migration-nopcommerce/7-arm-mcp-server.md

@@ -1,5 +1,6 @@
 ---
 title: Use the Arm MCP Server to optimize .NET performance
+description: Use the Arm MCP Server to rank endpoints, generate targeted tests, and plan evidence-based .NET performance optimizations on Azure Cobalt.
 weight: 7
 
 ### FIXED, DO NOT MODIFY

content/learning-paths/servers-and-cloud-computing/dotnet-migration-nopcommerce/_index.md

@@ -1,5 +1,6 @@
 ---
 title: Migrate and optimize a .NET nopCommerce application on Microsoft Azure
+description: Migrate, containerize, benchmark, and tune a .NET nopCommerce application on Azure Cobalt so you can validate Arm-based performance before rollout.
 
 minutes_to_complete: 75