converting some bullets to prose

Author: anupras-mohapatra-arm

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

@@ -65,13 +65,9 @@ If the command prints `runtimes/linux-arm64`, the package already carries an Arm
 
 ### Dependency cascade rule
 
-Treat dependencies as a chain, not isolated items:
+Treat dependencies as a chain, not isolated items.
 
-- App depends on library A
-- Library A depends on library B
-- Library B is architecture-sensitive
-
-You must resolve B first, then validate A, then validate the app.
+Assume the app depends on library A, library A depends on library B, library B is architecture-sensitive. In this scenario, you must resolve B first, then validate A, then validate the app.
 
 ## What you've accomplished and what's next
 

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

@@ -25,11 +25,7 @@ Identify endpoints most likely to benefit from Arm tuning.
 Rank them by expected impact and explain why.
 ```
 
-The output should include the following:
-
-- Ranked endpoint list
-- Bottleneck hypotheses per endpoint
-- Instrumentation plan to validate hypotheses
+The output should include a ranked endpoint list, bottleneck hypotheses per endpoint, and an instrumentation plan to validate the hypotheses.
 
 ### Generate and run a targeted endpoint test suite
 
@@ -43,13 +39,7 @@ Use concurrency, iterations, and JSON output.
 Include pass/fail checks for HTTP behavior and error rate.
 ```
 
-The suite should produce the following:
-
-- Per-endpoint latency percentiles
-- Throughput summary
-- Error counts
-- Before/after comparison artifacts
-- The exact route list and request method for each endpoint
+The suite should produce per-endpoint latency percentiles, a throughput summary, and error counts. It should also produce before and after comparison artifacts, and the exact route list and request method for each endpoint.
 
 ### Plan and implement Arm optimizations on Azure Cobalt