diff --git a/content/code-security/secret-scanning/configuring-secret-scanning-for-your-repositories.md b/content/code-security/secret-scanning/configuring-secret-scanning-for-your-repositories.md
index 548d37d0f2..8fa1fef400 100644
--- a/content/code-security/secret-scanning/configuring-secret-scanning-for-your-repositories.md
+++ b/content/code-security/secret-scanning/configuring-secret-scanning-for-your-repositories.md
@@ -62,7 +62,6 @@ You can enable the following additional {% data variables.product.prodname_secre
 
 ### Enabling validity checks for partner patterns
 
-{% data reusables.secret-scanning.validity-check-partner-patterns-beta %}
 {% data reusables.gated-features.partner-pattern-validity-check-ghas %}
 
 You can allow {% data variables.product.prodname_secret_scanning %} to automatically check the validity of a secret found in your repository by sending it to the relevant partner. For more information on validity checks, see "Checking a secret's validity" in "[AUTOTITLE](/code-security/secret-scanning/managing-alerts-from-secret-scanning#checking-a-secrets-validity)."
diff --git a/content/code-security/secret-scanning/managing-alerts-from-secret-scanning.md b/content/code-security/secret-scanning/managing-alerts-from-secret-scanning.md
index e66b2d79c5..4520fef86c 100644
--- a/content/code-security/secret-scanning/managing-alerts-from-secret-scanning.md
+++ b/content/code-security/secret-scanning/managing-alerts-from-secret-scanning.md
@@ -91,12 +91,6 @@ There are some additional features that can help you to evaluate alerts in order
 
 ### Checking a secret's validity
 
-{% ifversion secret-scanning-validity-check-partner-patterns %}
-
-{% data reusables.secret-scanning.validity-check-partner-patterns-beta %}
-
-{% endif %}
-
 Validity checks help you prioritize alerts by telling you which secrets are `active` or `inactive`. An `active` secret is one that could still be exploited, so these alerts should be reviewed and remediated as a priority.
 
 By default, {% data variables.product.company_short %} checks the validity of {% data variables.product.company_short %} tokens and displays the validitation status of the token in the alert view.
diff --git a/content/sponsors/receiving-sponsorships-through-github-sponsors/using-a-fiscal-host-to-receive-github-sponsors-payouts.md b/content/sponsors/receiving-sponsorships-through-github-sponsors/using-a-fiscal-host-to-receive-github-sponsors-payouts.md
index a269fa85ea..e9313f53bc 100644
--- a/content/sponsors/receiving-sponsorships-through-github-sponsors/using-a-fiscal-host-to-receive-github-sponsors-payouts.md
+++ b/content/sponsors/receiving-sponsorships-through-github-sponsors/using-a-fiscal-host-to-receive-github-sponsors-payouts.md
@@ -19,9 +19,12 @@ When you sign up for a {% data variables.product.prodname_sponsors %} profile so
 
 {% data variables.product.prodname_sponsors %} supports these fiscal hosts:
 
-* [Open Source Collective](https://opencollective.com/opensource)
+* [Hack Club](https://hackclub.com/)
 * [NumFOCUS](https://www.numfocus.org/)
 * [Open Collective Europe](https://opencollective.com/europe)
+* [Open Source Collective](https://opencollective.com/opensource)
+* [Python Software Foundation](https://www.python.org/psf-landing/)
+* [Software in the Public Interest](https://www.spi-inc.org/)
 * [Software Underground](https://softwareunderground.org/)
 
 ## Choosing to use a fiscal host
diff --git a/data/reusables/secret-scanning/validity-check-partner-patterns-beta.md b/data/reusables/secret-scanning/validity-check-partner-patterns-beta.md
deleted file mode 100644
index 21be634705..0000000000
--- a/data/reusables/secret-scanning/validity-check-partner-patterns-beta.md
+++ /dev/null
@@ -1,2 +0,0 @@
-> [!NOTE]
-> Validity checks for partner patterns is currently in beta and subject to change.