@@ -14,7 +14,7 @@ building around it.
1414
1515Deployments are a new model in the GitHub ecosystem. We don't have any UI
1616components currently, and deployments are intended to be used exclusively by
17- tooling. Much like the status API, we won't be doing the actual deployment for
17+ tooling. Much like the Status API, we won't be doing the actual deployment for
1818you. We're hoping to provide consistency across the various type of release
1919processes regardless of what's involved with getting it built or on your
2020servers.
@@ -55,16 +55,16 @@ whether or not to actually deploy the repository that the event was created for.
5555
5656We're making this new API available today for developers to preview. We think
5757developers and existing integrations are going to love it, but we want to get
58- your feedback before we declare the Deployment API "final" and "unchangeable."
58+ your feedback before we declare the Deployments API "final" and "unchangeable."
5959We expect the preview period to last for roughly 60-90 days.
6060
6161As we discover opportunities to improve the API during the preview period, we
6262may ship changes that break clients using the preview version of the API. We
6363want to iterate quickly. To do so, we will announce any changes here (on the
6464developer blog), but we will not provide any advance notice.
6565
66- At the end of preview period, the Deployment API will become an official
67- component of GitHub API v3. At that point, the new Deployment API will be
66+ At the end of preview period, the Deployments API will become an official
67+ component of GitHub API v3. At that point, the new Deployments API will be
6868stable and suitable for production use.
6969
7070We're really excited to see what people come up with.
0 commit comments