Merge pull request #679 from lucalves/lucalves/spelling-fix

Fixes minor misspellings

Author: janiceilene

content/admin/github-actions/setting-up-the-tool-cache-on-self-hosted-runners-without-internet-access.md

@@ -34,7 +34,7 @@ You can populate the runner tool cache by running a {% data variables.product.pr
 
 ### Populating the tool cache for a self-hosted runner
 
-1. On {% data variables.product.prodname_dotcom_the_website %}, navigate to a repostory that you can use to run a {% data variables.product.prodname_actions %} workflow.
+1. On {% data variables.product.prodname_dotcom_the_website %}, navigate to a repository that you can use to run a {% data variables.product.prodname_actions %} workflow.
 1. Create a new workflow file in the repository's `.github/workflows` folder that uploads an artifact containing the {% data variables.product.prodname_dotcom %}-hosted runner's tool cache.
 
    The following example demonstrates a workflow that uploads the tool cache for an Ubuntu 18.04 environment, using the `setup-node` action with Node.js versions 10 and 12.

content/developers/webhooks-and-events/github-event-types.md

@@ -28,13 +28,13 @@ The event objects returned from the Events API endpoints have the same structure
 | `actor.id` | The unique identifier for the actor. |
 | `actor.login` | The username of the actor. |
 | `actor.display_login` | The specific display format of the username. |
-| `actor.gravatar_id` | The unique indentifier of the Gravatar profile for the actor. |
+| `actor.gravatar_id` | The unique identifier of the Gravatar profile for the actor. |
 | `actor.url` | The REST API URL used to retrieve the user object, which includes additional user information. |
 | `actor.avatar_url` | The URL of the actor's profile image. |
 | `repo` | The repository object where the event occurred.  |
 | `repo.id` | The unique identifier of the repository. |
 | `repo.name` | The name of the repository, which includes the owner and repository name. For example, `octocat/hello-world` is the name of the `hello-world` repository owned by the `octocat` user account. |
-| `repo.url` | The REST API URL used to retrive the repository object, which includes additional repository information. |
+| `repo.url` | The REST API URL used to retrieve the repository object, which includes additional repository information. |
 | `payload` | The event payload object is unique to the event type. See the event type below for the event API `payload` object. |
 
 #### Example WatchEvent event object

content/developers/webhooks-and-events/issue-event-types.md

@@ -229,7 +229,7 @@ Name | Type | Description
 -----|------|--------------
 `actor` | `object` | The person who generated the event.
 `created_at` | `string` | The timestamp indicating when the cross-reference was added.
-`updated_at` | `string` | The timestamp indicating when the cross-refererence was updated or created, if the cross-reference is never updated.
+`updated_at` | `string` | The timestamp indicating when the cross-reference was updated or created, if the cross-reference is never updated.
 `source` | `object` | The issue or pull request that added a cross-reference.
 `source[type]` | `string` | This value will always be `"issue"` because pull requests are of type issue. Only cross-reference events triggered by issues or pull requests are returned in the Timeline Events API. To determine if the issue that triggered the event is a pull request, you can check if the `source[issue][pull_request` object exists.
 `source[issue]` | `object` | The `issue` object that added the cross-reference.

content/developers/webhooks-and-events/webhook-events-and-payloads.md

@@ -617,7 +617,7 @@ For a detailed description of this payload and the payload for each type of `act
 
 ### meta
 
-The webhook this event is configured on was deleted. This event will only listen for changes to the particular hook the event is installed on. Therefore, it must be selected for each hook that you'd like to recieve meta events for.
+The webhook this event is configured on was deleted. This event will only listen for changes to the particular hook the event is installed on. Therefore, it must be selected for each hook that you'd like to receive meta events for.
 
 #### Availability
 

content/github/administering-a-repository/about-required-commit-signing.md

@@ -11,7 +11,7 @@ versions:
 
 If you've enforced branch protections in your repository, you can set up required commit signing. For more information, see "[Configuring protected branches](/articles/configuring-protected-branches/)."
 
-When you enable required commit signing on a branch, contibutors {% if currentVersion == "free-pro-team@latest" %}and bots{% endif %} can only push commits that have been signed and verified to the branch. For more information, see "[About commit signature verification](/articles/about-commit-signature-verification)."
+When you enable required commit signing on a branch, contributors {% if currentVersion == "free-pro-team@latest" %}and bots{% endif %} can only push commits that have been signed and verified to the branch. For more information, see "[About commit signature verification](/articles/about-commit-signature-verification)."
 
 You can always push local commits to the branch if the commits are signed and verified. {% if currentVersion == "free-pro-team@latest" %}You can also merge signed and verified commits into the branch using a pull request on {% data variables.product.product_name %}. However, you cannot squash and merge a pull request into the branch on {% data variables.product.product_name %} unless you are the author of the pull request.{% else %} However, you cannot merge pull requests into the branch on {% data variables.product.product_name %}.{% endif %} You can {% if currentVersion == "free-pro-team@latest" %}squash and {% endif %}merge pull requests locally. For more information, see "[Checking out pull requests locally](/github/collaborating-with-issues-and-pull-requests/checking-out-pull-requests-locally)."{% if currentVersion == "free-pro-team@latest" %} For more information about merge methods, see "[About merge methods on {% data variables.product.prodname_dotcom %}](/github/administering-a-repository/about-merge-methods-on-github)."{% endif %}