chore: update generated Markdown docs

Author: timrogers

docs/actions/createOrUpdateEnvironmentSecret.md

@@ -111,7 +111,7 @@ The unique identifier of the repository.
 </td></tr>
 <tr><td>environment_name</td><td>yes</td><td>
 
-The name of the environment
+The name of the environment.
 
 </td></tr>
 <tr><td>secret_name</td><td>yes</td><td>

docs/actions/deleteEnvironmentSecret.md

@@ -36,7 +36,7 @@ The unique identifier of the repository.
 </td></tr>
 <tr><td>environment_name</td><td>yes</td><td>
 
-The name of the environment
+The name of the environment.
 
 </td></tr>
 <tr><td>secret_name</td><td>yes</td><td>

docs/actions/getEnvironmentPublicKey.md

@@ -35,7 +35,7 @@ The unique identifier of the repository.
 </td></tr>
 <tr><td>environment_name</td><td>yes</td><td>
 
-The name of the environment
+The name of the environment.
 
 </td></tr>
   </tbody>

docs/actions/getEnvironmentSecret.md

@@ -36,7 +36,7 @@ The unique identifier of the repository.
 </td></tr>
 <tr><td>environment_name</td><td>yes</td><td>
 
-The name of the environment
+The name of the environment.
 
 </td></tr>
 <tr><td>secret_name</td><td>yes</td><td>

docs/actions/listEnvironmentSecrets.md

@@ -35,7 +35,7 @@ The unique identifier of the repository.
 </td></tr>
 <tr><td>environment_name</td><td>yes</td><td>
 
-The name of the environment
+The name of the environment.
 
 </td></tr>
 <tr><td>per_page</td><td>no</td><td>

docs/actions/listWorkflowRuns.md

@@ -63,7 +63,7 @@ Returns workflow run triggered by the event you specify. For example, `push`, `p
 </td></tr>
 <tr><td>status</td><td>no</td><td>
 
-Returns workflow runs with the check run `status` or `conclusion` that you specify. For example, a conclusion can be `success` or a status can be `in_progress`. Only GitHub can set a status of `waiting` or `requested`. For a list of the possible `status` and `conclusion` options, see "[Create a check run](https://docs.github.com/rest/reference/checks#create-a-check-run)."
+Returns workflow runs with the check run `status` or `conclusion` that you specify. For example, a conclusion can be `success` or a status can be `in_progress`. Only GitHub can set a status of `waiting` or `requested`.
 
 </td></tr>
 <tr><td>per_page</td><td>no</td><td>

docs/actions/listWorkflowRunsForRepo.md

@@ -57,7 +57,7 @@ Returns workflow run triggered by the event you specify. For example, `push`, `p
 </td></tr>
 <tr><td>status</td><td>no</td><td>
 
-Returns workflow runs with the check run `status` or `conclusion` that you specify. For example, a conclusion can be `success` or a status can be `in_progress`. Only GitHub can set a status of `waiting` or `requested`. For a list of the possible `status` and `conclusion` options, see "[Create a check run](https://docs.github.com/rest/reference/checks#create-a-check-run)."
+Returns workflow runs with the check run `status` or `conclusion` that you specify. For example, a conclusion can be `success` or a status can be `in_progress`. Only GitHub can set a status of `waiting` or `requested`.
 
 </td></tr>
 <tr><td>per_page</td><td>no</td><td>

docs/activity/listNotificationsForAuthenticatedUser.md

@@ -45,14 +45,14 @@ Only show notifications updated after the given time. This is a timestamp in [IS
 Only show notifications updated before the given time. This is a timestamp in [ISO 8601](https://en.wikipedia.org/wiki/ISO_8601) format: `YYYY-MM-DDTHH:MM:SSZ`.
 
 </td></tr>
-<tr><td>per_page</td><td>no</td><td>
+<tr><td>page</td><td>no</td><td>
 
-The number of results per page (max 100).
+Page number of the results to fetch.
 
 </td></tr>
-<tr><td>page</td><td>no</td><td>
+<tr><td>per_page</td><td>no</td><td>
 
-Page number of the results to fetch.
+The number of results per page (max 50).
 
 </td></tr>
   </tbody>

docs/codeScanning/listAlertsForOrg.md

@@ -12,6 +12,8 @@ Lists code scanning alerts for the default branch for all eligible repositories
 
 To use this endpoint, you must be an owner or security manager for the organization, and you must use an access token with the `repo` scope or `security_events` scope.
 
+For public repositories, you may instead use the `public_repo` scope.
+
 GitHub Apps must have the `security_events` read permission to use this endpoint.
 
 ```js

docs/gists/fork.md

@@ -8,8 +8,6 @@ type: API method
 
 # Fork a gist
 
-**Note**: This was previously `/gists/:gist_id/fork`.
-
 ```js
 octokit.rest.gists.fork({
   gist_id,