diff --git a/content/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/streaming-the-audit-log-for-your-enterprise.md b/content/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/streaming-the-audit-log-for-your-enterprise.md index 7c39fd68276f..e21f2f319282 100644 --- a/content/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/streaming-the-audit-log-for-your-enterprise.md +++ b/content/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/streaming-the-audit-log-for-your-enterprise.md @@ -319,8 +319,6 @@ To restart streaming, click **Resume stream**. ## Enabling audit log streaming of API requests ->[!NOTE] This feature is currently in {% data variables.release-phases.public_preview %} and subject to change. - {% data reusables.enterprise-accounts.access-enterprise %} {% data reusables.enterprise-accounts.settings-tab %} {% data reusables.enterprise-accounts.audit-log-tab %} diff --git a/content/code-security/codeql-cli/getting-started-with-the-codeql-cli/preparing-your-code-for-codeql-analysis.md b/content/code-security/codeql-cli/getting-started-with-the-codeql-cli/preparing-your-code-for-codeql-analysis.md index 09745f1b5325..3342966ef8aa 100644 --- a/content/code-security/codeql-cli/getting-started-with-the-codeql-cli/preparing-your-code-for-codeql-analysis.md +++ b/content/code-security/codeql-cli/getting-started-with-the-codeql-cli/preparing-your-code-for-codeql-analysis.md @@ -272,7 +272,7 @@ The following examples are designed to give you an idea of some of the build com * Swift project built from an Xcode project or workspace. By default, the largest Swift target is built: - It's a good idea to ensure that the project is in a clean state and that there are no build artefacts available. + It's a good idea to ensure that the project is in a clean state and that there are no build artifacts available. ```shell xcodebuild clean -all diff --git a/content/get-started/writing-on-github/working-with-advanced-formatting/creating-a-permanent-link-to-a-code-snippet.md b/content/get-started/writing-on-github/working-with-advanced-formatting/creating-a-permanent-link-to-a-code-snippet.md index 0907ce36a820..bba719eb3c9e 100644 --- a/content/get-started/writing-on-github/working-with-advanced-formatting/creating-a-permanent-link-to-a-code-snippet.md +++ b/content/get-started/writing-on-github/working-with-advanced-formatting/creating-a-permanent-link-to-a-code-snippet.md @@ -38,9 +38,9 @@ This type of permanent link will render as a code snippet only in the repository ## Linking to Markdown -You can link to specific lines in Markdown files by loading the Markdown file without Markdown rendering. To load a Markdown file without rendering, you can use the `?plain=1` parameter at the end of the url for the file. For example, `github.com///blob//README.md?plain=1`. +You can link to specific lines in Markdown files by loading the Markdown file without Markdown rendering. To load a Markdown file without rendering, you can use the `?plain=1` parameter at the end of the URL for the file. For example, `github.com///blob//README.md?plain=1`. -You can link to a specific line in the Markdown file the same way you can in code. Append `#L` with the line number or numbers at the end of the url. For example, `github.com///blob//README.md?plain=1#L14` will highlight line 14 in the plain README.md file. +You can link to a specific line in the Markdown file the same way you can in code. Append `#L` with the line number or numbers at the end of the URL. For example, `github.com///blob//README.md?plain=1#L14` will highlight line 14 in the plain README.md file. ## Further reading diff --git a/content/rest/orgs/bypass-requests.md b/content/rest/orgs/bypass-requests.md index 3b3674476326..158acb1432b2 100644 --- a/content/rest/orgs/bypass-requests.md +++ b/content/rest/orgs/bypass-requests.md @@ -1,7 +1,8 @@ --- -title: TODOCS -shortTitle: TODOCS -intro: TODOCS +title: REST API endpoints for organization push rule bypass requests +shortTitle: Bypass requests +intro: >- + Use the REST API to manage organization push rule bypass requests. versions: # DO NOT MANUALLY EDIT. CHANGES WILL BE OVERWRITTEN BY A 🤖 ghec: '*' topics: diff --git a/data/reusables/gated-features/attestations.md b/data/reusables/gated-features/attestations.md index d84e777be5cb..693860b344da 100644 --- a/data/reusables/gated-features/attestations.md +++ b/data/reusables/gated-features/attestations.md @@ -1 +1 @@ -Artifact attestations are available in public repositories for all current {% data variables.product.prodname_dotcom %} plans. They are not available on legacy plans, such as Bronze, Silver, or Gold. {% ifversion fpt %}If you are on a {% data variables.product.prodname_free_user %}, {% data variables.product.prodname_pro %}, or {% data variables.product.prodname_team %} plan, artefact attestations are only available for public repositories. To use artifact attestations in private or internal repositories, you must be on a {% data variables.product.prodname_ghe_cloud %} plan. {% endif %} +Artifact attestations are available in public repositories for all current {% data variables.product.prodname_dotcom %} plans. They are not available on legacy plans, such as Bronze, Silver, or Gold. {% ifversion fpt %}If you are on a {% data variables.product.prodname_free_user %}, {% data variables.product.prodname_pro %}, or {% data variables.product.prodname_team %} plan, artifact attestations are only available for public repositories. To use artifact attestations in private or internal repositories, you must be on a {% data variables.product.prodname_ghe_cloud %} plan. {% endif %}