updating transitions

Author: anupras-mohapatra-arm

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

@@ -79,6 +79,6 @@ The `docker exec` command should print `CREATE EXTENSION`. If it prints `NOTICE:
 
 ## What you've accomplished and what's next
 
-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. 
+You've set up an Arm-based environment by creating a Microsoft Azure VM powered by Cobalt 100 with Docker, .NET 9, and PostgreSQL ready for nopCommerce validation. 
 
 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

@@ -236,7 +236,7 @@ This baseline process becomes the control for every later tuning or code-change
 
 ## What you've accomplished and what's next
 
-You've now created a baseline before migrating the application. 
+You've now pinned the nopCommerce source, verified the build, installed the app, and captured `arm_before.json` as your endpoint baseline.
 
 Next, you'll audit dependencies before migration. 
 

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

@@ -71,6 +71,6 @@ Assume the app depends on library A, library A depends on library B, library B i
 
 ## What you've accomplished and what's next
 
-You've reviewed application dependencies to understand what can change when you migrate to Arm.
+You've now mapped direct and transitive dependencies, generated an SBOM, and checked packages for native payloads that could affect Arm deployment.
 
 Next, you'll explore options to containerize and migrate the application.

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

@@ -96,6 +96,6 @@ Multi-RID container publishing starts with .NET SDK versions `8.0.405`, `9.0.102
 
 ## What you've accomplished and what's next
 
-You've learned about different containerization paths for the .NET application. 
+You've now compared the Dockerfile and .NET SDK publish paths and identified which container workflow to validate first for nopCommerce.
 
 Next, you'll tune application performance.