Update OpenAPI 3.0 Descriptions

github · Sep 16, 2024 · b50b528 · b50b528
1 parent 4615979
commit b50b528
Show file tree

Hide file tree

Showing 16 changed files with 24 additions and 24 deletions.
diff --git a/descriptions/api.github.com/api.gitpro.ttaallkk.top.2022-11-28.json b/descriptions/api.github.com/api.gitpro.ttaallkk.top.2022-11-28.json
@@ -26812,7 +26812,7 @@
     "/repos/{owner}/{repo}/attestations": {
       "post": {
         "summary": "Create an attestation",
-        "description": "Store an artifact attestation and associate it with a repository.\n\nThe authenticated user must have write permission to the repository and, if using a fine-grained access token the `attestations:write` permission is required.\n\nArtifact attestations are meant to be created using the [attest action](https://github.com/actions/attest). For amore information, see our guide on [using artifact attestations to establish a build's provenance](https://docs.github.com/actions/security-guides/using-artifact-attestations-to-establish-provenance-for-builds).",
+        "description": "Store an artifact attestation and associate it with a repository.\n\nThe authenticated user must have write permission to the repository and, if using a fine-grained access token, the `attestations:write` permission is required.\n\nArtifact attestations are meant to be created using the [attest action](https://github.com/actions/attest). For more information, see our guide on [using artifact attestations to establish a build's provenance](https://docs.github.com/actions/security-guides/using-artifact-attestations-to-establish-provenance-for-builds).",
         "tags": [
           "repos"
         ],

diff --git a/descriptions/api.github.com/api.gitpro.ttaallkk.top.2022-11-28.yaml b/descriptions/api.github.com/api.gitpro.ttaallkk.top.2022-11-28.yaml
@@ -19435,9 +19435,9 @@ paths:
       description: |-
         Store an artifact attestation and associate it with a repository.
 
-        The authenticated user must have write permission to the repository and, if using a fine-grained access token the `attestations:write` permission is required.
+        The authenticated user must have write permission to the repository and, if using a fine-grained access token, the `attestations:write` permission is required.
 
-        Artifact attestations are meant to be created using the [attest action](https://github.com/actions/attest). For amore information, see our guide on [using artifact attestations to establish a build's provenance](https://docs.github.com/actions/security-guides/using-artifact-attestations-to-establish-provenance-for-builds).
+        Artifact attestations are meant to be created using the [attest action](https://github.com/actions/attest). For more information, see our guide on [using artifact attestations to establish a build's provenance](https://docs.github.com/actions/security-guides/using-artifact-attestations-to-establish-provenance-for-builds).
       tags:
       - repos
       operationId: repos/create-attestation