Added more formatting.

Author: madeline-underwood

content/learning-paths/servers-and-cloud-computing/net-aspire/_index.md

@@ -3,7 +3,7 @@ title: Run a .NET Aspire application on Arm-based VMs on AWS and GCP
 
 minutes_to_complete: 60
 
-who_is_this_for: This is an introductory topic for software developers interested in learning how to deploy .NET Aspire applications on Arm-based Virtual Machines (VMs) on Amazon Web Services (AWS) and Google Cloud Platform (GCP).
+who_is_this_for: This is an introductory topic for software developers interested in learning how to deploy .NET Aspire applications on Arm-based virtual machines (VMs) on Amazon Web Services (AWS) and Google Cloud Platform (GCP).
 
 learning_objectives: 
     - Describe .NET Aspire, including what it can achieve.

content/learning-paths/servers-and-cloud-computing/net-aspire/_review.md

@@ -24,7 +24,7 @@ review:
 
     - questions:
         question: >
-            In Google Cloud Platform, which series should you select to use an Arm64 processor for your VM?
+            In Google Cloud Platform, which series should you select to use an Arm64 processor for the VM?
         answers:
             - T2A (Ampere Altra Arm).
             - E2 (General Purpose).

content/learning-paths/servers-and-cloud-computing/net-aspire/aws.md

@@ -7,7 +7,7 @@ layout: learningpathall
 ---
 
 ### Objective
-In this section, you will learn how to deploy the .NET Aspire application you created on to an AWS Elastic Compute Cloud (EC2) Virtual Machine powered by Arm-based processors, such as AWS Graviton. This allows you to leverage the cost and performance benefits of Arm architecture while benefiting from the seamless deployment of cloud-native applications on modern infrastructure.
+In this section, you will learn how to deploy the .NET Aspire application you created on to an AWS Elastic Compute Cloud (EC2) virtual machine powered by Arm-based processors, such as AWS Graviton. This allows you to leverage the cost and performance benefits of Arm architecture while benefiting from the seamless deployment of cloud-native applications on modern infrastructure.
 
 ### Set up your AWS EC2 Instance
 To set up an Arm-powered EC2 instance, follow these steps:

content/learning-paths/servers-and-cloud-computing/net-aspire/background.md

@@ -31,4 +31,4 @@ With a few helper method calls, you can create local resources, wait for the res
 
 By providing a consistent set of tools and patterns, .NET Aspire streamlines the development process of cloud-native applications. It manages complex applications during the development phase without dealing with low-level implementation details. .NET Aspire easily connects to commonly-used services with standardized interfaces and configurations. There are also various templates and tooling to accelerate project setup and development cycles.
 
-In this Learning Path, you will learn how to create a .NET Aspire application, describe the project, and modify the code on a Windows on Arm development machine. You will then deploy the application firstly, to an AWS Arm-powered virtual machines, and secondly, to a GCP Arm-powered virtual machine.
+In this Learning Path, you will learn how to create a .NET Aspire application, describe the project, and modify the code on a Windows on Arm development machine. You will then deploy the application firstly, to an AWS Arm-powered virtual machine, and secondly, to a GCP Arm-powered virtual machine.

content/learning-paths/servers-and-cloud-computing/net-aspire/gcp.md

@@ -12,20 +12,26 @@ In this section, you will learn how to deploy the .NET Aspire application you cr
 ### Create an Arm64 virtual machine
 To create an Arm64 VM, follow these steps:
 1. Create a Google Cloud Account. If you don’t already have an account, sign up for Google Cloud.
+
 2. Open the Google Cloud Console [here](https://console.cloud.google.com).
-3. Navigate to Compute Engine. In the Google Cloud Console, open the Navigation menu, and go to Compute Engine > VM Instances. Enable any relevant APIs if prompted.
+
+3. Navigate to Compute Engine. In the Google Cloud Console, open the Navigation menu, and go to **Compute Engine** > **VM Instances**. Enable any relevant APIs if prompted.
+
 4. Click **Create Instance**.
+
 5. Configure the VM Instance as follows:
-    * Name: **arm-server**
-    * Region/Zone: choose a region and zone where Arm64 processors are available, for example us-central1.
+    * Name: **arm-server**.
+    * Region/Zone: choose a region and zone where Arm64 processors are available, for example, **us-central1**.
     * Machine Family: select **General-purpose**.
-    * Series: T2A. 
+    * Series: **T2A**. 
     * Machine Type: select **t2a-standard-1**.
+
 The configuration setup should resemble the following:
 
 ![fig14](figures/14.png)
 
 6. Configure the Remaining Settings:
+    
     * Availability Policies: **Standard**.
     * Boot Disk: Click **Change**, then select **Ubuntu** as the operating system.
     * Identity and API Access: keep the default settings.
@@ -37,7 +43,7 @@ The configuration setup should resemble the following:
 
 ### Connecting to VM
 After creating the VM, connect to it as follows:
-1. In Compute Engine, click the SSH drop-down menu next to your VM, and select **Open in browser window**:
+1. In **Compute Engine**, click the SSH drop-down menu next to your VM, and select **Open in browser window**:
 
 ![fig16](figures/16.png)
 
@@ -50,7 +56,8 @@ After creating the VM, connect to it as follows:
 ![fig18](figures/18.png)
 
 ### Installing dependencies and deploying an app
-Once the connection is established, you can install the required dependencies (.NET SDK, Aspire workload, and Git), fetch the application code, and deploy it:
+Once the connection is established, you can install the required dependencies (.NET SDK, Aspire workload, and Git), fetch the application code, and deploy it.
+
 Update the Package List:
 ```console
 sudo apt update && sudo apt upgrade -y
@@ -95,18 +102,19 @@ dotnet run --project NetAspire.Arm.AppHost
 You will see output similar to this:
 ![fig19](figures/19.png)
 
-### Exposing the application to the Public
+### Making your application public
+
 To make your application publicly-accessible, configure the firewall rules:
 1. In the Google Cloud Console, navigate to **VPC Network** > **Firewall**.
 2. Click **Create Firewall Rule** and configure the following:
-    * Name: allow-dotnet-ports.
-    * Target Tags: dotnet-app.
-    * Source IP Ranges: 0.0.0.0/0 (for public access).
-    * Protocols and Ports: allow TCP on ports 7133, 7511, and 17222.
+    * Name: **allow-dotnet-ports**.
+    * Target Tags: **dotnet-app**.
+    * Source IP Ranges: **0.0.0.0/0** (for public access).
+    * Protocols and Ports: **allow TCP on ports 7133, 7511, and 17222**.
     * Click the **Create** button.
 3. Go back to your VM instance.
-4. Click **Edit**, and under Networking find Network Tags, add the tag dotnet-app. 
+4. Click **Edit**, and under **Networking** find **Network Tags**, add the tag **dotnet-app**. 
 5. Click the **Save** button.
 
 ### Summary
-You have successfully deployed the Aspire app onto an Arm-powered GCP Virtual Machine. This deployment demonstrates the compatibility of .NET applications with Arm architecture and GCP, offering high performance and cost-efficiency.
+You have successfully deployed the Aspire app onto an Arm-powered GCP virtual machine. This deployment demonstrates the compatibility of .NET applications with Arm architecture and GCP, offering high performance and cost-efficiency.