From d60e025d8b3b7665d3d44a2cbe732630bf0c6012 Mon Sep 17 00:00:00 2001 From: Michael Robertson Date: Wed, 24 Aug 2022 09:47:42 +0200 Subject: [PATCH] Cleaned up a bit of grammar. --- content/rest/deployments/deployments.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/rest/deployments/deployments.md b/content/rest/deployments/deployments.md index c371a1c819..0cd2b42859 100644 --- a/content/rest/deployments/deployments.md +++ b/content/rest/deployments/deployments.md @@ -20,7 +20,7 @@ Deployment statuses allow external services to mark deployments with an `error`, Deployment statuses can also include an optional `description` and `log_url`, which are highly recommended because they make deployment statuses more useful. The `log_url` is the full URL to the deployment output, and the `description` is a high-level summary of what happened with the deployment. -GitHub dispatches `deployment` and `deployment_status` events when new deployments and deployment statuses are created. These events allows third-party integrations to receive respond to deployment requests and update the status of a deployment as progress is made. +GitHub dispatches `deployment` and `deployment_status` events when new deployments and deployment statuses are created. These events allow third-party integrations to receive and respond to deployment requests, and update the status of a deployment as progress is made. Below is a simple sequence diagram for how these interactions would work.