Repo sync

content/code-security/how-tos/secure-at-scale/configure-enterprise-security/configure-specific-tools/setting-dependabot-to-run-on-github-hosted-runners-using-vnet.md

@@ -77,7 +77,7 @@ Now that you've set up private networking with VNET, you can start a {% data var
 
   ![Example of log for a "Dependabot in vnet" workflow. The Dependabot job is highlighted with an orange outline. ](/assets/images/help/dependabot/dependabot-vnet-logs.png)
 
-* You can view the active jobs in the page containing informatuon about the runner. To access that page, click the **Policies** tab for the enterprise, select **Actions** on the left sidebar, click the **Runner group** tab, and select your runner.
+* You can view the active jobs in the page containing information about the runner. To access that page, click the **Policies** tab for the enterprise, select **Actions** on the left sidebar, click the **Runner group** tab, and select your runner.
 
   ![Screenshot showing a Dependabot runner's active jobs.](/assets/images/help/dependabot/dependabot-vnet-active-jobs.png)
 

content/code-security/reference/supply-chain-security/troubleshoot-dependabot/dependabot-errors.md

@@ -88,7 +88,7 @@ If a security vulnerability is released for `B` versions `<2.0.0` and a patch is
 
 ### Can't close pull request for an update that's already been applied
 
-**Error message:** `{% data variables.product.prodname_dependabot %} fails to close a open pull request for an update that has already been applied on the default branch`
+**Error message:** `{% data variables.product.prodname_dependabot %} fails to close an open pull request for an update that has already been applied on the default branch`
 
 {% data variables.product.prodname_dependabot %} will close pull requests for dependency updates, once it detects these updates have been committed to the default branch. However, in rare circumstances, the pull request may remain open.
 

content/code-security/tutorials/adopting-github-advanced-security-at-scale/phase-6-rollout-and-scale-secret-scanning.md

@@ -31,8 +31,8 @@ When you enable {% data variables.product.prodname_secret_scanning %}, you shoul
 
 There are a few approaches for tackling newly committed credentials, but one example approach would be:
 
-1. **Notify:** Use webhooks to ensure that any new secret alerts are seen by the right teams as quickly as possible. A webhook fires when a secret alert is either created, resolved, or reopened. You can then parse the webhook payload, and integrate it into any tools you and your team use such Slack, Teams, Splunk, or email. For more information, see [AUTOTITLE](/webhooks/about-webhooks) and [AUTOTITLE](/webhooks/webhook-events-and-payloads#secret_scanning_alert).
-1. **Follow Up:** Create a high-level remediation process that works for all secret types. For example, you could contact the developer who committed the secret and their technical lead on that project, highlighting the dangers of committing secrets to {% data variables.product.prodname_dotcom %}, and asking the them to revoke, and update the detected secret.
+1. **Notify:** Use webhooks to ensure that any new secret alerts are seen by the right teams as quickly as possible. A webhook fires when a secret alert is either created, resolved, or reopened. You can then parse the webhook payload, and integrate it into any tools you and your team use such as Slack, Teams, Splunk, or email. For more information, see [AUTOTITLE](/webhooks/about-webhooks) and [AUTOTITLE](/webhooks/webhook-events-and-payloads#secret_scanning_alert).
+1. **Follow Up:** Create a high-level remediation process that works for all secret types. For example, you could contact the developer who committed the secret and their technical lead on that project, highlighting the dangers of committing secrets to {% data variables.product.prodname_dotcom %}, and asking them to revoke, and update the detected secret.
 
    > [!NOTE]
    > You can automate this step. For large enterprises and organizations with hundreds of repositories, manually following up is unsustainable. You could incorporate automation into the webhook process defined in the first step. The webhook payload contains repository and organization information about the leaked secret. Using this information, you can contact the current maintainers on the repository and create an email/message to the responsible people or open an issue.

content/organizations/keeping-your-organization-secure/managing-two-factor-authentication-for-your-organization/requiring-two-factor-authentication-in-your-organization.md

@@ -58,9 +58,9 @@ Before you require use of two-factor authentication, we recommend notifying {% i
 
 ### Requiring secure methods of two-factor authentication in your organization
 
-Alongside requiring two-factor authentication, you can require that organization members, billing managers, and outside collaborators use secure methods of 2FA. Secure two-factor methods are passkeys, security keys, authenticator apps, and the GitHub mobile app. Users who do not have a secure method of 2FA configured, or who have any insecure method (such as SMS) configured, will be prevented from accessing organization resources.
+Alongside requiring two-factor authentication, you can require that organization members, billing managers, and outside collaborators use secure methods of 2FA exclusively. Secure two-factor methods are passkeys, security keys, authenticator apps, and the GitHub mobile app. Users who do not have a secure method of 2FA configured, or who have any insecure method (such as SMS) configured, will be prevented from accessing organization resources.
 
-Before you require secure methods of two-factor authentication, we recommend notifying organization members, outside collaborators, and billing managers and asking them to set up secure 2FA for their accounts. You can see if members and outside collaborators already use secure methods of 2FA on each organization's People page. For more information, see [AUTOTITLE](/organizations/keeping-your-organization-secure/managing-two-factor-authentication-for-your-organization/viewing-whether-users-in-your-organization-have-2fa-enabled).
+Before you require secure methods of two-factor authentication, we recommend notifying organization members, outside collaborators, and billing managers: you should instruct them to set up secure 2FA for their accounts and then remove insecure methods of 2FA (including SMS). On each organization's People page, you can see if members and outside collaborators already use secure methods of 2FA exclusively. For more information, see [AUTOTITLE](/organizations/keeping-your-organization-secure/managing-two-factor-authentication-for-your-organization/viewing-whether-users-in-your-organization-have-2fa-enabled).
 
 {% data reusables.organizations.secure_two_factor_authentication %}
 {% data reusables.organizations.secure_two_factor_authentication_confirm %}

content/organizations/managing-saml-single-sign-on-for-your-organization/enabling-and-testing-saml-single-sign-on-for-your-organization.md

@@ -27,7 +27,7 @@ If you enable but don't enforce SAML SSO, organization members who choose not to
 
 ## Enabling and testing SAML single sign-on for your organization
 
-Before your enforce SAML SSO in your organization, ensure that you've prepared the organization. For more information, see [AUTOTITLE](/organizations/managing-saml-single-sign-on-for-your-organization/preparing-to-enforce-saml-single-sign-on-in-your-organization).
+Before you enforce SAML SSO in your organization, ensure that you've prepared the organization. For more information, see [AUTOTITLE](/organizations/managing-saml-single-sign-on-for-your-organization/preparing-to-enforce-saml-single-sign-on-in-your-organization).
 
 For more information about the identity providers (IdPs) that {% data variables.product.company_short %} supports for SAML SSO, see [AUTOTITLE](/organizations/managing-saml-single-sign-on-for-your-organization/connecting-your-identity-provider-to-your-organization).
 

content/repositories/configuring-branches-and-merges-in-your-repository/managing-rulesets/managing-rulesets-for-a-repository.md

@@ -38,7 +38,7 @@ For push rulesets for forked repositories, the "Rulesets" page will indicate tha
 1. Optionally, to filter the results click the tabs or use the "Search branches" search bar.
 1. Click the name of the ruleset you want to view.
 
-You can also view active ruselets:
+You can also view active rulesets:
 
 * By adding the `/rules` slug to the repository's URL. For example, to view the rules of the open source documentation repository at {% data variables.product.github %},  you would go to https://github.com/github/docs/rules.
 

content/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/managing-the-commit-signoff-policy-for-your-repository.md

@@ -23,4 +23,4 @@ Organization owners can also enable compulsory commit signoffs at the organizati
 
 {% data reusables.repositories.navigate-to-repo %}
 {% data reusables.repositories.sidebar-settings %}
-1. Select **Require contributors to sign off on web-based commits**.
+1. Under "Commits", Select **Require contributors to sign off on web-based commits**.

src/graphql/data/fpt/schema-enterprise-admin.json

@@ -12274,7 +12274,7 @@
       "inputFields": [
         {
           "name": "allowListValue",
-          "description": "<p>An IP address or range of addresses in CIDR notation.</p>",
+          "description": "<p>An IP address or range of addresses in CIDR notation. Ranges that cover the\nentire address space, such as <code>0.0.0.0/0</code> or <code>::/0</code>, are not accepted for\norganizations or enterprises.</p>",
           "type": "String!",
           "id": "string",
           "href": "/graphql/reference/other#scalar-string"
@@ -13739,7 +13739,7 @@
       "inputFields": [
         {
           "name": "allowListValue",
-          "description": "<p>An IP address or range of addresses in CIDR notation.</p>",
+          "description": "<p>An IP address or range of addresses in CIDR notation. Ranges that cover the\nentire address space, such as <code>0.0.0.0/0</code> or <code>::/0</code>, are not accepted for\norganizations or enterprises.</p>",
           "type": "String!",
           "id": "string",
           "href": "/graphql/reference/other#scalar-string"

src/graphql/data/fpt/schema.docs.graphql

@@ -8416,7 +8416,9 @@ Autogenerated input type of CreateIpAllowListEntry
 """
 input CreateIpAllowListEntryInput {
   """
-  An IP address or range of addresses in CIDR notation.
+  An IP address or range of addresses in CIDR notation. Ranges that cover the
+  entire address space, such as `0.0.0.0/0` or `::/0`, are not accepted for
+  organizations or enterprises.
   """
   allowListValue: String!
 
@@ -69819,7 +69821,9 @@ Autogenerated input type of UpdateIpAllowListEntry
 """
 input UpdateIpAllowListEntryInput {
   """
-  An IP address or range of addresses in CIDR notation.
+  An IP address or range of addresses in CIDR notation. Ranges that cover the
+  entire address space, such as `0.0.0.0/0` or `::/0`, are not accepted for
+  organizations or enterprises.
   """
   allowListValue: String!
 

src/graphql/data/ghec/schema-enterprise-admin.json

@@ -12274,7 +12274,7 @@
       "inputFields": [
         {
           "name": "allowListValue",
-          "description": "<p>An IP address or range of addresses in CIDR notation.</p>",
+          "description": "<p>An IP address or range of addresses in CIDR notation. Ranges that cover the\nentire address space, such as <code>0.0.0.0/0</code> or <code>::/0</code>, are not accepted for\norganizations or enterprises.</p>",
           "type": "String!",
           "id": "string",
           "href": "/graphql/reference/other#scalar-string"
@@ -13739,7 +13739,7 @@
       "inputFields": [
         {
           "name": "allowListValue",
-          "description": "<p>An IP address or range of addresses in CIDR notation.</p>",
+          "description": "<p>An IP address or range of addresses in CIDR notation. Ranges that cover the\nentire address space, such as <code>0.0.0.0/0</code> or <code>::/0</code>, are not accepted for\norganizations or enterprises.</p>",
           "type": "String!",
           "id": "string",
           "href": "/graphql/reference/other#scalar-string"

src/graphql/data/ghec/schema.docs.graphql

@@ -8416,7 +8416,9 @@ Autogenerated input type of CreateIpAllowListEntry
 """
 input CreateIpAllowListEntryInput {
   """
-  An IP address or range of addresses in CIDR notation.
+  An IP address or range of addresses in CIDR notation. Ranges that cover the
+  entire address space, such as `0.0.0.0/0` or `::/0`, are not accepted for
+  organizations or enterprises.
   """
   allowListValue: String!
 
@@ -69819,7 +69821,9 @@ Autogenerated input type of UpdateIpAllowListEntry
 """
 input UpdateIpAllowListEntryInput {
   """
-  An IP address or range of addresses in CIDR notation.
+  An IP address or range of addresses in CIDR notation. Ranges that cover the
+  entire address space, such as `0.0.0.0/0` or `::/0`, are not accepted for
+  organizations or enterprises.
   """
   allowListValue: String!