Update 2-github-actions-automate-development-tasks.md

Author: camihmerhar

learn-pr/github/github-actions-automate-tasks/includes/2-github-actions-automate-development-tasks.md

@@ -168,10 +168,10 @@ Each type of runner has its benefits, but GitHub-hosted runners offer a quicker
 
 GitHub Actions has some usage limits, depending on your GitHub plan and whether your runner is GitHub-hosted or self-hosted. For more information on usage limits, check out [Usage limits, billing, and administration](https://docs.github.com/actions/reference/usage-limits-billing-and-administration) in the GitHub documentation.
 
-## GitHub Hosted Larger Runners
+## GitHub hosted larger runners
 GitHub offers larger runners for workflows that require more resources. These runners are GitHub-hosted and provide increased CPU, memory, and disk space compared to standard runners. They are designed to handle resource-intensive workflows efficiently, ensuring optimal performance for demanding tasks.
 
-### Runner Sizes and Labels
+### Runner sizes and labels
 Larger runners are available in multiple configurations, providing enhanced vCPUs, RAM, and SSD storage to meet diverse workflow requirements. These configurations are ideal for scenarios such as:
 - Compiling large codebases with extensive source files.
 - Running comprehensive test suites, including integration and end-to-end tests.
@@ -196,22 +196,22 @@ These larger runners maintain compatibility with existing workflows by including
 For more details on runner sizes for larger runners, refer to the GitHub documentation [https://docs.github.com/en/actions/using-github-hosted-runners/using-larger-runners/about-larger-runners#machine-sizes-for-larger-runners]
 
 
-### Managing Larger Runners
+### Managing larger runners
 GitHub provides tools to manage larger runners effectively, ensuring optimal resource utilization and cost management. Here are some key aspects of managing larger runners:
 
-#### Monitoring Usage
+#### Monitoring usage
 You can monitor the usage of larger runners through the GitHub Actions usage page in your repository or organization settings. This page provides insights into the number of jobs run, the total runtime, and the associated costs.
 
-#### Managing Access
+#### Managing access
 To control access to larger runners, you can configure repository or organization-level policies. This ensures that only authorized workflows or teams can use these high-resource runners.
 
-#### Cost Management
+#### Cost management
 Larger runners incur additional costs based on their usage. To manage costs, consider the following:
 - Use larger runners only for workflows that require high resources.
 - Optimize workflows to reduce runtime.
 - Monitor billing details regularly to track expenses.
 
-#### Scaling Workflows
+#### Scaling workflows
 If your workflows require frequent use of larger runners, consider scaling strategies such as:
 - Using self-hosted runners for predictable workloads.
 - Splitting workflows into smaller jobs to distribute the load across standard runners.