Merge pull request #7451 from bl-ue/fix-typos

Fix typos

Author: mchammer01

…codespaces/codespaces-commad-palette.png …odespaces/codespaces-command-palette.pngassets/images/help/codespaces/codespaces-commad-palette.png renamed to assets/images/help/codespaces/codespaces-command-palette.png assets/images/help/codespaces/codespaces-commad-palette.png renamed to assets/images/help/codespaces/codespaces-command-palette.png

@@ -39,7 +39,7 @@ We recommend that you have a basic understanding of Xamarin, .NET Core SDK, YAML
 - "[Getting started with .NET](https://dotnet.microsoft.com/learn)"
 - "[Learn Xamarin](https://dotnet.microsoft.com/learn/xamarin)"
 
-## Bulding Xamarin.iOS apps
+## Building Xamarin.iOS apps
 
 The example below demonstrates how to change the default Xamarin SDK versions and build a Xamarin.iOS application.
 
@@ -79,7 +79,7 @@ jobs:
 ```
 {% endraw %}
 
-## Bulding Xamarin.Android apps
+## Building Xamarin.Android apps
 
 The example below demonstrates how to change default Xamarin SDK versions and build a Xamarin.Android application.
 

…ername-with-limited-availibilty-text.png …rname-with-limited-availability-text.pngassets/images/help/profile/username-with-limited-availibilty-text.png renamed to assets/images/help/profile/username-with-limited-availability-text.png assets/images/help/profile/username-with-limited-availibilty-text.png renamed to assets/images/help/profile/username-with-limited-availability-text.png

@@ -110,7 +110,7 @@ We strongly recommend enabling PROXY support for both your instance and the load
 
 {% data reusables.enterprise_clustering.x-forwarded-for %}
 
-To enable the `X-Fowarded-For` header, use this command:
+To enable the `X-Forwarded-For` header, use this command:
 
 ```shell
 $ ghe-config 'loadbalancer.http-forward' 'true' && ghe-cluster-config-apply

content/actions/guides/building-and-testing-xamarin-applications.md

@@ -34,7 +34,7 @@ As a maintainer, it's good practice to clearly indicate how and where you want t
 
 Maintainers should disclose vulnerabilities in a timely manner. If there is a security vulnerability in your repository, we recommend you:
 - Treat the vulnerability as a security issue rather than a simple bug, both in your response and your disclosure. For example, you'll need to explicitly mention that the issue is a security vulnerability in the release notes.
-- Acknowlege receipt of the vulnerability report as quickly as possible, even if no immediate resources are available for investigation. This sends the message that you are quick to respond and act, and it sets a positive tone for the rest of the interaction between you and the vulnerability reporter.
+- Acknowledge receipt of the vulnerability report as quickly as possible, even if no immediate resources are available for investigation. This sends the message that you are quick to respond and act, and it sets a positive tone for the rest of the interaction between you and the vulnerability reporter.
 - Involve the vulnerability reporter when you verify the impact and veracity of the report. It's likely the vulnerability reporter has already spent time considering the vulnerability in a variety of scenarios, some of which you may have not considered yourself.
 - Remediate the issue in a way that you see fit, taking any concerns and advice provided by the vulnerability reporter into careful consideration. Often the vulnerability reporter will have knowledge of certain corner cases and remediation bypasses that are easy to miss without a security research background.
 - Always acknowledge the vulnerability reporter when you credit the discovery.
@@ -65,5 +65,3 @@ The process for reporting and disclosing vulnerabilities for projects on {% data
 
 
  To get started, see "[Creating a security advisory](/github/managing-security-vulnerabilities/creating-a-security-advisory)."
-
-

content/admin/enterprise-management/configuring-clustering/cluster-network-configuration.md

@@ -31,7 +31,7 @@ You can access the Command Palette in a number of ways.
 
 To see all commands related to {% data variables.product.prodname_github_codespaces %} access the Command Palette, then start typing "Codespaces".
 
-![A list of all commands that relate to Codespaces](/assets/images/help/codespaces/codespaces-commad-palette.png)
+![A list of all commands that relate to Codespaces](/assets/images/help/codespaces/codespaces-command-palette.png)
 
 ### Suspending or stopping a codespace
 

content/code-security/security-advisories/about-coordinated-disclosure-of-security-vulnerabilities.md

@@ -26,7 +26,7 @@ Codespaces are associated with a specific branch of a repository and the reposit
 When you create a codespace, a number of steps happen to enable full access to your development environment.
 
 - Resources such as a VM and storage for your container are assigned. A new VM is created every time you create or start a codespace to ensure that you always have the latest versions and security patches.
-- {% data variables.product.prodname_codespaces %} recieves information about your repository, branch, commits, your public dotfiles repository, and any secrets that you have created.
+- {% data variables.product.prodname_codespaces %} receives information about your repository, branch, commits, your public dotfiles repository, and any secrets that you have created.
 - {% data variables.product.prodname_codespaces %} executes a shallow clone of the repository.
 - If you have one in your repository, {% data variables.product.prodname_codespaces %} runs the `devcontainer.json` file. For more information, see "[Configuring {% data variables.product.prodname_codespaces %} for your project](/github/developing-online-with-codespaces/configuring-codespaces-for-your-project)."
 - Your Docker container, `docker-compose`, or other initialization is run.
@@ -56,6 +56,3 @@ When you create a codespace, a number of steps happen to enable full access to y
 4. To create a codespace using a Standard machine type, click {% octicon "plus" aria-label="The plus icon" %} **New codespace**.
 
   ![New codespace button](/assets/images/help/codespaces/new-codespace-button.png)
-
-
-   

content/codespaces/codespaces-reference/using-the-command-palette-in-codespaces.md

@@ -22,7 +22,7 @@ When an application running inside a codespace outputs a port to the console, {%
 
 ![Automatic port forwarding](/assets/images/help/codespaces/automatic-port-forwarding.png)
 
-You can also forward a port manually, label forwarded ports, share fowarded ports publicly, and add forwarded ports to the codespace configuration.
+You can also forward a port manually, label forwarded ports, share forwarded ports publicly, and add forwarded ports to the codespace configuration.
 
 ## Forwarding a port
 
@@ -58,10 +58,9 @@ If you want to share a forwarded port with others, you can make the port public.
 
 You can add a forwarded port to the {% data variables.product.prodname_codespaces %} configuration for the repository, so the port will automatically be forwarded for all codespaces created from the repository. After you update the configuration, any previously created codespaces must be rebuilt for the change to apply. For more information, see "[Configuring {% data variables.product.prodname_codespaces %} for your project](/codespaces/setting-up-your-codespace/configuring-codespaces-for-your-project#applying-changes-to-your-configuration)."
 
-You can manually configure fowarded ports in a `.devcontainer.json` file using the `forwardPorts` property, or you can use the "Ports" panel in your codespace.
+You can manually configure forwarded ports in a `.devcontainer.json` file using the `forwardPorts` property, or you can use the "Ports" panel in your codespace.
 
 {% data reusables.codespaces.navigate-to-ports-tab %}
 1. Right click the port you want to add to the codespace configuration, then click **Set Label and Update devcontainer.json**.
   ![Option to set label and add port to devcontainer.json in the right-click menu](/assets/images/help/codespaces/update-devcontainer-to-add-port-option.png)
 {% data reusables.codespaces.type-port-label %}
-

content/codespaces/developing-in-codespaces/creating-a-codespace.md

@@ -166,7 +166,7 @@ You can use the Dockerfile to add additional container layers to specify OS pack
 
 ## Step 3: Modify your devcontainer.json file 
 
-With your dev container added and a basic understanding of what everything does, you can now make changes to configure it for your environment. In this example, you'll add properties to install extensions and restore your project dependancies when your codespace launches.
+With your dev container added and a basic understanding of what everything does, you can now make changes to configure it for your environment. In this example, you'll add properties to install extensions and restore your project dependencies when your codespace launches.
 
 1. In the Explorer, expand the `.devcontainer` folder and select the `devcontainer.json` file from the tree to open it. 
 

content/codespaces/developing-in-codespaces/forwarding-ports-in-your-codespace.md

@@ -148,7 +148,7 @@ You can use the Dockerfile to add additional container layers to specify OS pack
 
 With your dev container added and a basic understanding of what everything does, you can now make changes to configure it for your environment. In this example, you'll add properties to install extensions and your project dependencies when your codespace launches.
 
-1. In the Explorer, select the `devcontainer.json` file from the tree to open it. You might have to exand the `.devcontainer` folder to see it. 
+1. In the Explorer, select the `devcontainer.json` file from the tree to open it. You might have to expand the `.devcontainer` folder to see it.
 
   !["Codespaces: Rebuild Container" in the command palette](/assets/images/help/codespaces/devcontainers-options.png)