More improvements.

Author: madeline-underwood

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

@@ -5,13 +5,13 @@ weight: 6
 ### FIXED, DO NOT MODIFY
 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.
 
 ### Set up your AWS EC2 Instance
 To set up an Arm-powered EC2 instance, follow these steps:
 1. Log in to the [AWS Management Console](http://console.aws.amazon.com).
+
 2. Navigate to the EC2 Service. 
 
    As Figure 5 shows, in the search box, type "EC2". 
@@ -69,7 +69,9 @@ The configuration should look like:
 
 ### Deploy the application
 Once the EC2 instance is ready, you can connect to it, and deploy the application. Follow these steps to connect:
+
 1. Locate the instance public IP (here this is 98.83.137.101).
+
 2. Use an SSH client to connect:
 * Open the terminal.
 * Set the appropriate permissions for the key pair file, using your own IP address:

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

@@ -31,4 +31,7 @@ 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 machine, 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.
+* Secondly, to a GCP Arm-powered virtual machine.

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

@@ -106,14 +106,18 @@ You will see output similar to this:
 
 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**.
     * 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**. 
+
 5. Click the **Save** button.
 
 ### Summary

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

@@ -68,14 +68,22 @@ This command generates a solution with the following structure:
     * Standard health check implementations.
     * Logging configurations to ensure consistent and efficient monitoring and debugging.
 
-The structure of this project is designed to enhance efficiency, and simplify the development of cloud-native applications. At its core, it incorporates features to ensure seamless service interactions, robust monitoring, and an exceptional development experience.
+The structure of this project is designed to enhance efficiency and simplify the development of cloud-native applications. At its core, it incorporates features to ensure seamless service interactions, robust monitoring, and an exceptional development experience.
+
+#### Service discovery
 
 One of the foundational elements is service discovery, which enables automatic service registration, dynamic endpoint resolution, and load balancing. These features ensure that services communicate effectively and handle traffic efficiently, even in complex, distributed environments.
 
+#### Monitoring and telemetry
+
 For monitoring and telemetry, the architecture integrates tools like built-in health checks, OpenTelemetry for monitoring, and metrics collection with distributed tracing. These features provide developers with deep insights into application performance, helping to maintain reliability and optimize system operations.
 
+#### Configuration management
+
 Configuration management offers environment-based settings that make deploying applications across different stages straightforward. Secure secrets management safeguards sensitive information, while standardized service-to-service communication simplifies interactions between microservices.
 
+#### Improved development experience
+
 The architecture is also tailored to improve the development experience. Developers can benefit from local debugging support and a powerful monitoring dashboard. This dashboard provides a detailed view of the following:
 
 * Service health.