diff --git a/content/actions/writing-workflows/choosing-when-your-workflow-runs/events-that-trigger-workflows.md b/content/actions/writing-workflows/choosing-when-your-workflow-runs/events-that-trigger-workflows.md
index e5fc94f31f5c..9247f356e61b 100644
--- a/content/actions/writing-workflows/choosing-when-your-workflow-runs/events-that-trigger-workflows.md
+++ b/content/actions/writing-workflows/choosing-when-your-workflow-runs/events-that-trigger-workflows.md
@@ -838,7 +838,7 @@ jobs:
 > The webhook payload available to GitHub Actions does not include the `added`, `removed`, and `modified` attributes in the `commit` object. You can retrieve the full commit object using the API. For information, see "[AUTOTITLE](/graphql/reference/objects#commit)" in the GraphQL API documentation or "[AUTOTITLE](/rest/commits#get-a-commit)."
 
 > [!NOTE]
-> {% ifversion fpt or ghec or ghes > 3.13 %}Events will not be created if more than 5,000 branches are pushed at once. {% endif %}Events will not be created for tags when more than three tags are pushed at once.
+> {% ifversion fpt or ghec or ghes > 3.14 %}Events will not be created if more than 5,000 branches are pushed at once. {% endif %}Events will not be created for tags when more than three tags are pushed at once.
 
 Runs your workflow when you push a commit or tag, or when you create a repository from a template.
 
diff --git a/content/code-security/secret-scanning/working-with-secret-scanning-and-push-protection/working-with-push-protection-from-the-command-line.md b/content/code-security/secret-scanning/working-with-secret-scanning-and-push-protection/working-with-push-protection-from-the-command-line.md
index ca6a4ea4e8fa..cb5c0eb6b634 100644
--- a/content/code-security/secret-scanning/working-with-secret-scanning-and-push-protection/working-with-push-protection-from-the-command-line.md
+++ b/content/code-security/secret-scanning/working-with-secret-scanning-and-push-protection/working-with-push-protection-from-the-command-line.md
@@ -45,7 +45,7 @@ To resolve a blocked push, you must remove the secret from all of the commits it
 If the blocked secret was introduced by the latest commit on your branch, you can follow the guidance below.
 
 1. Remove the secret from your code.
-1. To commit the changes, run `git commit --amend`. This updates the original commit that introduced the secret instead of creating a new commit.
+1. To commit the changes, run `git commit --amend --all`. This updates the original commit that introduced the secret instead of creating a new commit.
 1. Push your changes with `git push`.
 
 ### Removing a secret introduced by an earlier commit on your branch
@@ -107,6 +107,12 @@ You can also remove the secret if the secret appears in an earlier commit in the
 
 1. Save and close the editor to start the interactive rebase.
 1. Remove the secret from your code.
+1. Add your changes to the staging area using `git add .`.
+
+   >[!NOTE] The full command is `git add .`:
+   > * There is a space between `add` and `.`.
+   > * The period following the space is part of the command.
+
 1. Commit your changes using `git commit --amend`.
 1. Run `git rebase --continue` to finish the rebase.
 1. Push your changes with `git push`.
diff --git a/content/copilot/about-github-copilot/github-copilot-features.md b/content/copilot/about-github-copilot/github-copilot-features.md
index 7cd4b54b8112..c57b1e81e45a 100644
--- a/content/copilot/about-github-copilot/github-copilot-features.md
+++ b/content/copilot/about-github-copilot/github-copilot-features.md
@@ -16,35 +16,43 @@ redirect_from:
 
 ### Code completion
 
-Autocomplete-style suggestions from {% data variables.product.prodname_copilot_short %} in supported IDEs _({% data variables.product.prodname_vscode %}, {% data variables.product.prodname_vs %}, JetBrains IDEs, Azure Data Studio, Xcode, and Vim/Neovim)_.
+Autocomplete-style suggestions from {% data variables.product.prodname_copilot_short %} in supported IDEs _({% data variables.product.prodname_vscode %}, {% data variables.product.prodname_vs %}, JetBrains IDEs, Azure Data Studio, Xcode, and Vim/Neovim)_. For more information, see "[AUTOTITLE](/copilot/using-github-copilot/getting-code-suggestions-in-your-ide-with-github-copilot)."
 
 ### {% data variables.product.prodname_copilot_chat_short %}
 
-A chat interface that lets you ask coding-related questions. {% data variables.product.prodname_copilot_chat %} is available on the {% data variables.product.github %} website, in {% data variables.product.prodname_mobile %}, in supported IDEs _({% data variables.product.prodname_vscode %}, {% data variables.product.prodname_vs %}, and JetBrains IDEs)_, and in {% data variables.product.prodname_windows_terminal %}. Users can also use skills with {% data variables.product.prodname_copilot_chat_short %}.
+A chat interface that lets you ask coding-related questions. {% data variables.product.prodname_copilot_chat %} is available on the {% data variables.product.github %} website, in {% data variables.product.prodname_mobile %}, in supported IDEs _({% data variables.product.prodname_vscode %}, {% data variables.product.prodname_vs %}, and JetBrains IDEs)_, and in {% data variables.product.prodname_windows_terminal %}. Users can also use skills with {% data variables.product.prodname_copilot_chat_short %}. For more information, see "[AUTOTITLE](/copilot/using-github-copilot/asking-github-copilot-questions-in-github)" and "[AUTOTITLE](/copilot/using-github-copilot/asking-github-copilot-questions-in-your-ide)."
 
 ### {% data variables.product.prodname_copilot_cli_short %}
 
-A chat-like interface in the terminal, where you can ask questions about the command line. You can ask {% data variables.product.prodname_copilot_short %} to provide command suggestions or explanations of commands. Users can also integrate {% data variables.product.prodname_copilot_short %} in {% data variables.product.prodname_windows_terminal %} Canary.
+A chat-like interface in the terminal, where you can ask questions about the command line. You can ask {% data variables.product.prodname_copilot_short %} to provide command suggestions or explanations of commands. Users can also integrate {% data variables.product.prodname_copilot_short %} in {% data variables.product.prodname_windows_terminal %} Canary. For more information, see "[AUTOTITLE](/copilot/using-github-copilot/using-github-copilot-in-the-command-line)."
 
 ### {% data variables.product.prodname_copilot_for_prs %}
 
-AI-generated summaries of the changes that were made in a pull request, which files they impact, and what a reviewer should focus on when they conduct their review.
+AI-generated summaries of the changes that were made in a pull request, which files they impact, and what a reviewer should focus on when they conduct their review. For more information, see "[AUTOTITLE](/copilot/using-github-copilot/using-github-copilot-for-pull-requests/creating-a-pull-request-summary-with-github-copilot)."
+
+### {% data variables.product.prodname_copilot_workspace %} ({% data variables.release-phases.public_preview %})
+
+A {% data variables.product.prodname_copilot_short %}-enabled environment for refining your pull requests, validating changes, and integrating suggestions from reviewers. For more information, see "[AUTOTITLE](/copilot/using-github-copilot/using-github-copilot-for-pull-requests/using-copilot-to-help-you-work-on-a-pull-request)."
 
 ### {% data variables.product.prodname_copilot_autocomplete_pr %} ({% data variables.release-phases.public_preview %})
 
-AI-generated text completion to help you write pull request descriptions quickly and accurately.
+AI-generated text completion to help you write pull request descriptions quickly and accurately. For more information, see "[AUTOTITLE](/copilot/using-github-copilot/using-copilot-text-completion)."
 
 ### {% data variables.product.prodname_copilot_extensions %} ({% data variables.release-phases.public_preview %})
 
-{% data reusables.copilot.copilot-extensions.copilot-extensions-intro %}
+{% data reusables.copilot.copilot-extensions.copilot-extensions-intro %} For more information, see "[AUTOTITLE](/copilot/building-copilot-extensions/about-building-copilot-extensions)."
 
 ### GitHub Models ({% data variables.release-phases.public_preview %})
 
-Bringing the power of industry leading large and small language models to users directly on {% data variables.product.github %}.
+Bringing the power of industry leading large and small language models to users directly on {% data variables.product.github %}. For more information, see "[AUTOTITLE](/github-models)."
+
+### {% data variables.product.prodname_copilot %} code review ({% data variables.release-phases.public_preview %})
+
+AI-generated code review suggestions to help you write better code. For more information, see "[AUTOTITLE](/copilot/using-github-copilot/code-review/using-copilot-code-review)."
 
 ### {% data variables.product.prodname_copilot_short %} knowledge bases _({% data variables.product.prodname_copilot_enterprise_short %} only)_
 
-Create and manage collections of documentation to use as context for chatting with {% data variables.product.prodname_copilot_short %}. When you ask a question in {% data variables.product.prodname_copilot_chat_dotcom_short %} or in {% data variables.product.prodname_vscode_shortname %}, you can specify a knowledge base as the context for your question.
+Create and manage collections of documentation to use as context for chatting with {% data variables.product.prodname_copilot_short %}. When you ask a question in {% data variables.product.prodname_copilot_chat_dotcom_short %} or in {% data variables.product.prodname_vscode_shortname %}, you can specify a knowledge base as the context for your question. For more information, see "[AUTOTITLE](/copilot/customizing-copilot/managing-copilot-knowledge-bases)."
 
 ## {% data variables.product.prodname_copilot %} features for administrators
 
@@ -52,23 +60,23 @@ The following features are available to organization and enterprise owners with
 
 ### Policy management
 
-Manage policies for {% data variables.product.prodname_copilot_short %} in your organization or enterprise.
+Manage policies for {% data variables.product.prodname_copilot_short %} in your organization or enterprise. For more information, see "[AUTOTITLE](/copilot/managing-copilot/managing-github-copilot-in-your-organization/setting-policies-for-copilot-in-your-organization/managing-policies-for-copilot-in-your-organization)" and "[AUTOTITLE](/copilot/managing-copilot/managing-copilot-for-your-enterprise/managing-policies-and-features-for-copilot-in-your-enterprise)."
 
 ### Access management
 
-Enterprise owners can specify which organizations in the enterprise can use {% data variables.product.prodname_copilot_short %}, and organization owners can specify which organization members can use Copilot.
+Enterprise owners can specify which organizations in the enterprise can use {% data variables.product.prodname_copilot_short %}, and organization owners can specify which organization members can use Copilot. For more information, see "[AUTOTITLE](/copilot/managing-copilot/managing-github-copilot-in-your-organization/managing-access-to-github-copilot-in-your-organization)" and "[AUTOTITLE](/copilot/managing-copilot/managing-copilot-for-your-enterprise/managing-access-to-copilot-in-your-enterprise)."
 
 ### Usage data
 
-Review {% data variables.product.prodname_copilot_short %} usage data within your organization or enterprise to inform how to manage access and drive adoption of {% data variables.product.prodname_copilot_short %}.
+Review {% data variables.product.prodname_copilot_short %} usage data within your organization or enterprise to inform how to manage access and drive adoption of {% data variables.product.prodname_copilot_short %}. For more information, see "[AUTOTITLE](/copilot/managing-copilot/managing-github-copilot-in-your-organization/reviewing-activity-related-to-github-copilot-in-your-organization/reviewing-user-activity-data-for-copilot-in-your-organization)" and "[AUTOTITLE](/copilot/managing-copilot/managing-copilot-for-your-enterprise/managing-access-to-copilot-in-your-enterprise/viewing-copilot-license-usage-in-your-enterprise)."
 
 ### Audit logs
 
-Review audit logs for {% data variables.product.prodname_copilot_short %} in your organization to understand what actions have been taken and by which users.
+Review audit logs for {% data variables.product.prodname_copilot_short %} in your organization to understand what actions have been taken and by which users. For more information, see "[AUTOTITLE](/copilot/managing-copilot/managing-github-copilot-in-your-organization/reviewing-activity-related-to-github-copilot-in-your-organization/reviewing-audit-logs-for-copilot-business)."
 
 ### Exclude files
 
-Configure {% data variables.product.prodname_copilot_short %} to ignore certain files. This can be useful if you have files that you don't want to be available to {% data variables.product.prodname_copilot_short %}.
+Configure {% data variables.product.prodname_copilot_short %} to ignore certain files. This can be useful if you have files that you don't want to be available to {% data variables.product.prodname_copilot_short %}. For more information, see "[AUTOTITLE](/copilot/managing-copilot/managing-github-copilot-in-your-organization/setting-policies-for-copilot-in-your-organization/excluding-content-from-github-copilot)."
 
 ## Next steps
 
diff --git a/content/copilot/troubleshooting-github-copilot/viewing-logs-for-github-copilot-in-your-environment.md b/content/copilot/troubleshooting-github-copilot/viewing-logs-for-github-copilot-in-your-environment.md
index a9e1a78a2fa3..879096844d40 100644
--- a/content/copilot/troubleshooting-github-copilot/viewing-logs-for-github-copilot-in-your-environment.md
+++ b/content/copilot/troubleshooting-github-copilot/viewing-logs-for-github-copilot-in-your-environment.md
@@ -157,3 +157,23 @@ To check if GitHub Copilot is operational, run the following command in Vim/Neov
     :Copilot status
 
 {% endvimneovim %}
+
+{% xcode %}
+
+## Collecting log files
+
+The log files for the {% data variables.product.prodname_copilot %} extension for Xcode are stored in `~/Library/Logs/GitHubCopilot/`. The most recent file is named `github-copilot-for-xcode.log`.
+
+1. Open the {% data variables.product.prodname_copilot %} extension application.
+1. At the top of the application window, click **Advanced**.
+1. In the "Logging" section, click **Open Copilot Log Folder**.
+
+## Enabling verbose logs
+
+You can enable verbose logging to help troubleshoot issues with the {% data variables.product.prodname_copilot %} extension for Xcode.
+
+1. Open the {% data variables.product.prodname_copilot %} extension application.
+1. At the top of the application window, click **Advanced**.
+1. In the "Logging" section, next to "Verbose Logging", toggle the switch to the right.
+
+{% endxcode %}
diff --git a/content/issues/planning-and-tracking-with-projects/automating-your-project/automating-projects-using-actions.md b/content/issues/planning-and-tracking-with-projects/automating-your-project/automating-projects-using-actions.md
index 63b63699fec9..c227976f0ff4 100644
--- a/content/issues/planning-and-tracking-with-projects/automating-your-project/automating-projects-using-actions.md
+++ b/content/issues/planning-and-tracking-with-projects/automating-your-project/automating-projects-using-actions.md
@@ -124,7 +124,7 @@ jobs:
           echo 'PROJECT_ID='$(jq '.data.organization.projectV2.id' project_data.json) >> $GITHUB_ENV
           echo 'DATE_FIELD_ID='$(jq '.data.organization.projectV2.fields.nodes[] | select(.name== "Date posted") | .id' project_data.json) >> $GITHUB_ENV
           echo 'STATUS_FIELD_ID='$(jq '.data.organization.projectV2.fields.nodes[] | select(.name== "Status") | .id' project_data.json) >> $GITHUB_ENV
-          echo 'TODO_OPTION_ID='$(jq '.data.organization.projectV2.fields.nodes[] | select(.name== "Todo") | .options[] | select(.name=="Todo") |.id' project_data.json) >> $GITHUB_ENV
+          echo 'TODO_OPTION_ID='$(jq '.data.organization.projectV2.fields.nodes[] | select(.name== "Status") | .options[] | select(.name=="Todo") |.id' project_data.json) >> $GITHUB_ENV
 
 # Sets environment variables for this step. `GH_TOKEN` is the token generated in the first step. `PR_ID` is the ID of the pull request that triggered this workflow.
       - name: Add PR to project
@@ -257,7 +257,7 @@ jobs:
           echo 'PROJECT_ID='$(jq '.data.organization.projectV2.id' project_data.json) >> $GITHUB_ENV
           echo 'DATE_FIELD_ID='$(jq '.data.organization.projectV2.fields.nodes[] | select(.name== "Date posted") | .id' project_data.json) >> $GITHUB_ENV
           echo 'STATUS_FIELD_ID='$(jq '.data.organization.projectV2.fields.nodes[] | select(.name== "Status") | .id' project_data.json) >> $GITHUB_ENV
-          echo 'TODO_OPTION_ID='$(jq '.data.organization.projectV2.fields.nodes[] | select(.name== "Todo") | .options[] | select(.name=="Todo") |.id' project_data.json) >> $GITHUB_ENV
+          echo 'TODO_OPTION_ID='$(jq '.data.organization.projectV2.fields.nodes[] | select(.name== "Status") | .options[] | select(.name=="Todo") |.id' project_data.json) >> $GITHUB_ENV
 
 # Sets environment variables for this step. Replace `YOUR_TOKEN` with the name of the secret that contains your {% data variables.product.pat_generic %}.
       - name: Add PR to project
diff --git a/content/organizations/managing-peoples-access-to-your-organization-with-roles/about-custom-organization-roles.md b/content/organizations/managing-peoples-access-to-your-organization-with-roles/about-custom-organization-roles.md
index c5907d60feb5..2e644b046b46 100644
--- a/content/organizations/managing-peoples-access-to-your-organization-with-roles/about-custom-organization-roles.md
+++ b/content/organizations/managing-peoples-access-to-your-organization-with-roles/about-custom-organization-roles.md
@@ -1,6 +1,6 @@
 ---
 title: About custom organization roles
-intro: "You can control access to your {% ifversion org-custom-role-with-repo-permissions %}organization and repository's{% else %} organization's{% endif %} settings with custom organization roles."
+intro: "You can control access to your {% ifversion org-custom-role-with-repo-permissions %}organization's settings and repositories{% else %}organization's settings{% endif %} with custom organization roles."
 versions:
   feature: 'custom-org-roles'
 topics:
@@ -16,9 +16,14 @@ You can create and assign custom organization roles in your organization's setti
 
 {% ifversion org-custom-role-with-repo-permissions %}
 
-You can also create a custom organization role that includes permissions for repositories. Repository permissions grant access to all current and future repositories in the organization. There are several ways to combine permissions for repositories and organizations. You can create a custom organization role with:
+You can also create a custom organization role that includes permissions for repositories. Repository permissions grant access to all current and future repositories in the organization.
 
-You can create a role that includes permissions for organization settings, a base role for repository access, or both. If you add a base role for repository access, you can also include additional repository permissions. You can't create a role with repository permissions unless it includes a base repository role. Without repository permissions or a base repository role, the organization role doesn't grant access to any repositories.
+There are several ways to combine permissions for repositories and organizations.
+
+* You can create a role that includes permissions for organization settings, a base role for repository access, or both.
+* If you add a base role for repository access, you can also include additional repository permissions. You can't add repository permissions without a base repository role.
+
+Without repository permissions or a base repository role, the organization role doesn't grant access to any repositories.
 
 >[!NOTE] Adding repository permissions to a custom organization role is currently in {% data variables.release-phases.public_preview %} and subject to change.
 
diff --git a/content/repositories/viewing-activity-and-data-for-your-repository/understanding-connections-between-repositories.md b/content/repositories/viewing-activity-and-data-for-your-repository/understanding-connections-between-repositories.md
index a62789ce29cc..7354abf15004 100644
--- a/content/repositories/viewing-activity-and-data-for-your-repository/understanding-connections-between-repositories.md
+++ b/content/repositories/viewing-activity-and-data-for-your-repository/understanding-connections-between-repositories.md
@@ -41,13 +41,14 @@ The network graph displays the branch history of the entire repository network,
 
 ## Listing the forks of a repository
 
-The{% ifversion repositories-forks-page-improvement %} forks page {% else %} Members graph {% endif %} lists the forks of a repository. {% ifversion repositories-forks-page-improvement %}For each fork, you can see:
-* how many times the fork has been starred
-* the number of direct forks (of the fork)
-* the number of open issues
-* the number of open pull requests
-* when the fork was last updated (that is, the last push to any branch)
-* when the fork was created
+The {% ifversion repositories-forks-page-improvement %} forks page {% else %} Members graph {% endif %} lists the forks of a repository. {% ifversion repositories-forks-page-improvement %} For each fork, you can see:
+
+* How many times the fork has been starred
+* The number of direct forks (of the fork)
+* The number of open issues
+* The number of open pull requests
+* When the fork was last updated (that is, the last push to any branch)
+* When the fork was created
 
 You can filter the list of forks to display active, inactive, starred, or archived forks, or to only display forks that have been updated within a specified time period (up to a period of five years). To view the most useful or most active forks, you can sort the list of forks by most starred forks or most recently updated forks, or by the number of open issues or open pull requests.
 
diff --git a/content/repositories/working-with-files/managing-files/renaming-a-file.md b/content/repositories/working-with-files/managing-files/renaming-a-file.md
index 00096d16931c..fff230aeb09d 100644
--- a/content/repositories/working-with-files/managing-files/renaming-a-file.md
+++ b/content/repositories/working-with-files/managing-files/renaming-a-file.md
@@ -18,7 +18,7 @@ topics:
 
 ## Renaming a file on {% data variables.product.product_name %}
 
-Renaming a file also gives you the opportunity to [move the file to a new location](/repositories/working-with-files/managing-files/moving-a-file-to-a-new-location)
+Renaming a file also gives you the opportunity to [move the file to a new location](/repositories/working-with-files/managing-files/moving-a-file-to-a-new-location).
 
 > [!TIP]
 > * If you try to rename a file in a repository that you don’t have access to, we will fork the project to your personal account and help you send [a pull request](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests) to the original repository after you commit your change.
diff --git a/content/search-github/github-code-search/understanding-github-code-search-syntax.md b/content/search-github/github-code-search/understanding-github-code-search-syntax.md
index 5a2ad92cbba1..9c8cf017f5ed 100644
--- a/content/search-github/github-code-search/understanding-github-code-search-syntax.md
+++ b/content/search-github/github-code-search/understanding-github-code-search-syntax.md
@@ -311,4 +311,8 @@ If code search guesses wrong, you can always get the search you wanted by using
 
 ## Case sensitivity
 
-By default, code search is case-insensitive. Searching for `True` will include results for _uppercase_ `TRUE` and _lowercase_ `true`. You can do case-sensitive searches by using a regular expression with case insensitivity turned off, for example `(?-i)True`.
+By default, code search is case-insensitive, and results will include both uppercase and lowercase results. You can do case-sensitive searches by using a regular expression with case insensitivity turned off. For example, to search for the string "True", you would use:
+
+```text
+/(?-i)True/
+```
diff --git a/data/release-notes/enterprise-server/3-14/0.yml b/data/release-notes/enterprise-server/3-14/0.yml
index aebcfe34f7a9..f7e1af5654c2 100644
--- a/data/release-notes/enterprise-server/3-14/0.yml
+++ b/data/release-notes/enterprise-server/3-14/0.yml
@@ -168,11 +168,6 @@ sections:
         - |
           When using a JSON Web Token (JWT) to authenticate or request an installation token, developers of GitHub Apps can use the app's client ID for the JWT's `iss` claim. The application ID remains valid, but is considered deprecated.
 
-  changes:
-    # https://github.com/github/releases/issues/3927
-    - |
-      Pushes that update over 5,000 branches no longer trigger webhooks or GitHub Actions workflows.
-
   known_issues:
     - |
       Complete SCIM payloads are written to the audit log, including SCIM attributes that are not required or supported per [API docs](/rest/enterprise-admin/scim?apiVersion=2022-11-28#supported-scim-user-attributes). Customers using Okta with SCIM may notice that a placeholder password attribute is among the data passed to audit logs in its current configuration. This placeholder data is associated with Okta’s password synchronization feature that is not expected or required by GitHub. See [okta-scim](https://developer.okta.com/docs/api/openapi/okta-scim/guides/scim-20/#create-the-user) for more information.
@@ -233,3 +228,5 @@ sections:
       The fix for this problem was already included prior to the release of GitHub Enterprise Server 3.14.0. [Updated: 2024-09-16]
     - |
       These release notes did not include a note for support of the `directories` key in `dependabot.yml` files. [Updated: 2024-10-07]
+    - |
+      The "Changes" section indicated that "Pushes that update over 5,000 branches no longer trigger webhooks or GitHub Actions workflows." The change instead affects GitHub Enterprise Server version 3.15. [Updated: 2024-10-30]
diff --git a/data/reusables/actions/about-workflows-long.md b/data/reusables/actions/about-workflows-long.md
index da8ec0972437..88826cbbe06a 100644
--- a/data/reusables/actions/about-workflows-long.md
+++ b/data/reusables/actions/about-workflows-long.md
@@ -1,6 +1,6 @@
 A **workflow** is a configurable automated process that will run one or more jobs. Workflows are defined by a YAML file checked in to your repository and will run when triggered by an event in your repository, or they can be triggered manually, or at a defined schedule.
 
-Workflows are defined in the `.github/workflows` directory in a repository. A repository can have multiple workflows, each which can perform a different set of tasks such as:
+Workflows are defined in the `.github/workflows` directory in a repository. A repository can have multiple workflows, each of which can perform a different set of tasks such as:
 * Building and testing pull requests.
 * Deploying your application every time a release is created.
 * Adding a label whenever a new issue is opened.
diff --git a/data/reusables/organizations/pre-defined-organization-roles.md b/data/reusables/organizations/pre-defined-organization-roles.md
index 232a4d31d2ac..d608e5d29bda 100644
--- a/data/reusables/organizations/pre-defined-organization-roles.md
+++ b/data/reusables/organizations/pre-defined-organization-roles.md
@@ -1,4 +1,4 @@
-Pre-defined organization roles are roles that are available by default in every organization - no need to create them yourself. They can include both organization permissions that let the recipient manage the organization, as well as repository permissions that apply to all of the repositories in the organization. The following pre-defined roles are built into every organization based on common patterns of permissions organizations usually need.
+Pre-defined organization roles are roles that are available by default in every organization. You don't need to create them yourself. They can include both organization permissions that let the recipient manage the organization, as well as repository permissions that apply to all of the repositories in the organization. The following pre-defined roles are built into every organization based on common patterns of permissions organizations usually need.
 
 The current set of pre-defined roles are:
 
@@ -7,4 +7,6 @@ The current set of pre-defined roles are:
 * **All-repository triage**: Grants triage access to all repositories in the organization.
 * **All-repository maintain**: Grants maintenance access to all repositories in the organization.
 * **All-repository admin**: Grants admin access to all repositories in the organization.
+{%- ifversion ghes > 3.15 %}
 * **CI/CD admin**: Grants admin access to manage Actions policies, runners, runner groups, hosted compute network configurations, secrets, variables, and usage metrics for an organization.
+{%- endif %}
diff --git a/data/reusables/repositories/rulesets-bypass-step.md b/data/reusables/repositories/rulesets-bypass-step.md
index cb963054bdf0..95feb1b89b41 100644
--- a/data/reusables/repositories/rulesets-bypass-step.md
+++ b/data/reusables/repositories/rulesets-bypass-step.md
@@ -1,6 +1,6 @@
 You can grant certain roles, teams, or apps bypass permissions {% ifversion push-rule-delegated-bypass %} as well as the ability to approve bypass requests {% endif %} for your ruleset. The following are eligible for bypass access:
 
-* Repository admins, organization owners, and enterprise owners.
+* Repository admins, organization owners, and enterprise owners
 * The maintain or write role, or custom repository roles based on the write role
 * Teams
 * Deploy keys
diff --git a/src/audit-logs/lib/config.json b/src/audit-logs/lib/config.json
index 20134b17fe53..3f6272bdc2cf 100644
--- a/src/audit-logs/lib/config.json
+++ b/src/audit-logs/lib/config.json
@@ -3,5 +3,5 @@
     "apiOnlyEvents": "This event is not available in the web interface, only via the REST API, audit log streaming, or JSON/CSV exports.",
     "apiRequestEvent": "This event is only available via audit log streaming."
   },
-  "sha": "5d970b28488c7feadf83faa4a426b5ce21fe3e0a"
+  "sha": "799eb5c9bf3a5c8963dd18327718f21e302f1c41"
 }
\ No newline at end of file