Final checks

Author: madeline-underwood

content/learning-paths/servers-and-cloud-computing/dotnet-migration/2-add-shared-c-library.md

@@ -108,7 +108,9 @@ Hello from the C library!
 
 ## Compiling for Arm
 
-If you are compiling for Arm directly on Azure Cobalt, the compiler understands what default processor optimizations it should use, and you can compile as done above. However, if you are cross-compiling in your build pipeline, you should specify `-mcpu=neoverse-n2 -O3` when running the cross-compiler:
+If you are compiling for Arm directly on Azure Cobalt, the compiler understands the default processor optimizations it should use, and you can compile in the same way as above. 
+
+However, if you are cross-compiling in your build pipeline, you should specify `-mcpu=neoverse-n2 -O3` when running the cross-compiler:
 
 ```bash
 aarch64-linux-gnu-gcc -mcpu=neoverse-n2 -O3 -shared -o libmylib.so -fPIC mylib.c

content/learning-paths/servers-and-cloud-computing/dotnet-migration/3-any-cpu.md

@@ -1,5 +1,5 @@
 ---
-title: Configure and run an architecture-agnostic OrchardCore app on Arm and x86 using .NET AnyCPU
+title: Configure and run an OrchardCore app 
 weight: 4
 
 ### FIXED, DO NOT MODIFY

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

@@ -4,7 +4,7 @@ title: Migrate a .NET application to Azure Cobalt 100
 
 minutes_to_complete: 25
 
-who_is_this_for: This is an advanced topic path for .NET developers who want to take advantage of the performance and cost benefits of Azure Cobalt processors.
+who_is_this_for: This is an advanced topic for .NET developers who want to take advantage of the performance and cost benefits of Azure Cobalt processors.
 
 learning_objectives: 
     - Build and run a basic OrchardCore CMS application