Updates

Author: madeline-underwood

content/learning-paths/servers-and-cloud-computing/dotnet-migration/1-create-orchardcore-app.md

@@ -1,5 +1,5 @@
 ---
-title: Build and run an OrchardCore CMS app on Azure Cobalt
+title: Build and run an OrchardCore CMS app on Azure Cobalt (Arm64)
 weight: 2
 
 ### FIXED, DO NOT MODIFY
@@ -12,7 +12,7 @@ In this section, you'll build and run a basic [OrchardCore](https://github.com/O
 
 ## Set up your development environment
 
-First, launch an Azure Cobalt 100 instance running Ubuntu 24.04, and open port 8080 to the internet. 
+First, launch an Azure Cobalt 100 instance (Arm-based VM) running Ubuntu 24.04, and open port 8080 to the internet. 
 
 For setup instructions, see the [Create an Azure Cobalt 100 VM](../../cobalt) Learning Path.
 

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

@@ -5,13 +5,10 @@ weight: 3
 ### FIXED, DO NOT MODIFY
 layout: learningpathall
 ---
-
-## Introduction
+## Create a C shared library
 
 In this section, you’ll integrate a simple C shared library into your .NET OrchardCore application. You’ll create the library, compile it, and call it from your .NET code. This allows you to reuse existing C code and improve performance by accessing native functionality.
 
-## Create a C shared library
-
 First, create a simple C shared library that defines a function you’ll call from your .NET application.
 
 Create a new file named `mylib.c` with the following content:
@@ -115,4 +112,4 @@ aarch64-linux-gnu-gcc -mcpu=neoverse-n2 -O3 -shared -o libmylib.so -fPIC mylib.c
 
 The `-mcpu=neoverse-n2` flag specifies the Cobalt architecture, and `-O3` ensures that maximum optimizations are completed (including SIMD optimizations).
 
-In the next section, you’ll make your native interop cross-platform by using the `anyCPU` feature and runtime dispatch strategies.
+In the next section, you’ll make your native interop cross-platform by using the AnyCPU feature and runtime dispatch strategies.