docs(links): update stale section anchors

Point five documentation references at the current destination headings so readers land on the intended sections instead of the top of each article.

Changes:
- content/code-security/tutorials/secret-scanning-partner-program.md
  - Link conditional-request guidance to its current section anchor.

- content/repositories/configuring-branches-and-merges-in-your-repository/managing-rulesets/troubleshooting-rules.md
  - Link Evaluate-mode guidance to the current enforcement-status anchor.

- content/repositories/configuring-branches-and-merges-in-your-repository/managing-rulesets/available-rules-for-rulesets.md
  - Link ruleset workflow guidance to the current enforcement-status anchor.

- content/organizations/managing-programmatic-access-to-your-organization/about-programmatic-access-in-your-organization.md
  - Link SAML credentials guidance to the single-member section.

- data/reusables/enterprise-accounts/invite-organization.md
  - Link enterprise invitations to the current invitation section.

- content/admin/managing-your-enterprise-account/deleting-an-enterprise-account.md
  - Link organization transfer guidance to the current transfer section.

Validation:
- npm run lint-content -- --paths <six changed files>
- npm run check-links-internal -- --version free-pro-team@latest
- npm run check-links-internal -- --version enterprise-cloud@latest
- npm run check-links-internal -- --version enterprise-server@3.22
- git diff --staged --check

Author: raulkolaric

content/admin/managing-your-enterprise-account/deleting-an-enterprise-account.md

@@ -14,7 +14,7 @@ category:
 
 ## Prerequisites
 
-Before you can delete an enterprise account, you must remove, transfer, or delete all organizations in the enterprise. For more information, see [AUTOTITLE](/admin/managing-accounts-and-repositories/managing-organizations-in-your-enterprise/adding-organizations-to-your-enterprise#transferring-an-organization-between-enterprise-accounts) and [AUTOTITLE](/admin/managing-accounts-and-repositories/managing-organizations-in-your-enterprise/removing-organizations-from-your-enterprise).
+Before you can delete an enterprise account, you must remove, transfer, or delete all organizations in the enterprise. For more information, see [AUTOTITLE](/admin/managing-accounts-and-repositories/managing-organizations-in-your-enterprise/adding-organizations-to-your-enterprise#transferring-an-existing-organization) and [AUTOTITLE](/admin/managing-accounts-and-repositories/managing-organizations-in-your-enterprise/removing-organizations-from-your-enterprise).
 
 After removing organizations, check the "People" tab in your enterprise settings and remove any unaffiliated members who remain in the enterprise. Unaffiliated members are users who are not part of any organization within the enterprise.
 

content/code-security/tutorials/secret-scanning-partner-program.md

@@ -125,7 +125,7 @@ will provide several `key_identifier` and public keys. You can determine which p
 key to use based on the value of `Github-Public-Key-Identifier`.
 
 > [!NOTE]
-> When you send a request to the public key endpoint above, you may hit rate limits. To avoid hitting rate limits, you can use a {% data variables.product.pat_v1 %} (no scopes required) or a {% data variables.product.pat_v2 %} (only the automatic public repositories read access required) as suggested in the samples below, or use a conditional request. For more information, see [AUTOTITLE](/rest/using-the-rest-api/best-practices-for-using-the-rest-api#use-conditional-requests-if-appropriate).
+> When you send a request to the public key endpoint above, you may hit rate limits. To avoid hitting rate limits, you can use a {% data variables.product.pat_v1 %} (no scopes required) or a {% data variables.product.pat_v2 %} (only the automatic public repositories read access required) as suggested in the samples below, or use a conditional request. For more information, see [AUTOTITLE](/rest/using-the-rest-api/best-practices-for-using-the-rest-api#use-conditional-requests).
 
 > [!NOTE]
 > The signature was generated using the raw message body. So it's important you also use the raw message body for signature validation, instead of parsing and stringifying the JSON, to avoid rearranging the message or changing spacing.

content/organizations/managing-programmatic-access-to-your-organization/about-programmatic-access-in-your-organization.md

@@ -43,7 +43,7 @@ Organization owners can view all {% data variables.product.pat_v2 %}s that can a
 
 {% ifversion ghec %}
 
-If their organization uses SAML, organization owners can see each {% data variables.product.pat_generic %} that a member of their organization authorized. For more information, see [AUTOTITLE](/organizations/granting-access-to-your-organization-with-saml-single-sign-on/viewing-and-managing-a-members-saml-access-to-your-organization#viewing-and-revoking-authorized-credentials).
+If their organization uses SAML, organization owners can see each {% data variables.product.pat_generic %} that a member of their organization authorized. For more information, see [AUTOTITLE](/organizations/granting-access-to-your-organization-with-saml-single-sign-on/viewing-and-managing-a-members-saml-access-to-your-organization#viewing-and-revoking-authorized-credentials-for-a-single-member).
 
 {% endif %}
 

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

@@ -271,7 +271,7 @@ If a ruleset workflow runs in "Evaluate" mode and passes, you can set the rulese
 
 If you open a pull request before you create the ruleset in "Evaluate" mode, you can still merge the pull request since the ruleset is not enforced.
 
-For more information about enforcement statuses, see [AUTOTITLE](/repositories/configuring-branches-and-merges-in-your-repository/managing-rulesets/creating-rulesets-for-a-repository#about-using-enforcement-statuses).
+For more information about enforcement statuses, see [AUTOTITLE](/repositories/configuring-branches-and-merges-in-your-repository/managing-rulesets/creating-rulesets-for-a-repository#using-ruleset-enforcement-statuses).
 
 ### Supported event triggers
 

content/repositories/configuring-branches-and-merges-in-your-repository/managing-rulesets/troubleshooting-rules.md

@@ -68,7 +68,7 @@ Ruleset workflows do not run on events triggered by the `GITHUB_TOKEN`. For more
 
 A required workflow can block people from creating a repository, since a workflow can't run against a repository that's being initialized. To get around this, the ruleset either needs to have "Evaluate" as the enforcement status, or someone with bypass permissions needs to create the repository and bypass the branch protection.
 
-For more information about enforcement statuses and "Evaluate" mode, see [AUTOTITLE](/repositories/configuring-branches-and-merges-in-your-repository/managing-rulesets/creating-rulesets-for-a-repository#about-using-enforcement-statuses).
+For more information about enforcement statuses and "Evaluate" mode, see [AUTOTITLE](/repositories/configuring-branches-and-merges-in-your-repository/managing-rulesets/creating-rulesets-for-a-repository#using-ruleset-enforcement-statuses).
 
 For more information about bypass permissions, see [AUTOTITLE](/repositories/configuring-branches-and-merges-in-your-repository/managing-protected-branches/about-protected-branches).
 

data/reusables/enterprise-accounts/invite-organization.md

@@ -1 +1 @@
-Enterprise account owners can invite existing organization accounts to join their enterprise. For more information, see [AUTOTITLE](/enterprise-cloud@latest/admin/managing-accounts-and-repositories/managing-organizations-in-your-enterprise/adding-organizations-to-your-enterprise#inviting-an-organization-to-join-your-enterprise-account).
+Enterprise account owners can invite existing organization accounts to join their enterprise. For more information, see [AUTOTITLE](/enterprise-cloud@latest/admin/managing-accounts-and-repositories/managing-organizations-in-your-enterprise/adding-organizations-to-your-enterprise#inviting-an-existing-organization).