Introduce new variables for release phase terminology (#52375)

Co-authored-by: Sunbrye Ly <56200261+sunbrye@users.noreply.github.com>

content/account-and-profile/setting-up-and-managing-your-github-profile/customizing-your-profile/personalizing-your-profile.md

@@ -212,7 +212,7 @@ To stop private contributions from counting toward your Achievements, or to turn
 
 {% note %}
 
-**Note:** This feature is currently in beta and subject to change.
+**Note:** This feature is currently in {% data variables.release-phases.public_preview %} and subject to change.
 
 {% endnote %}
 

content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-user-account-settings/about-your-personal-dashboard.md

@@ -51,7 +51,7 @@ You can also find a list of your recently visited repositories, teams, and proje
 
 {% note %}
 
-**Note:** The new feed is currently in public beta and subject to change.
+**Note:** The new feed is currently in {% data variables.release-phases.public_preview %} and subject to change.
 
 {% endnote %}
 
@@ -91,7 +91,7 @@ For more information about following people and starring repositories, see "[AUT
 
 {% note %}
 
-**Note:** This new tab is currently in public beta and subject to change.
+**Note:** This new tab is currently in {% data variables.release-phases.public_preview %} and subject to change.
 
 {% endnote %}
 

content/actions/hosting-your-own-runners/managing-self-hosted-runners/about-self-hosted-runners.md

@@ -117,7 +117,7 @@ The following operating systems are supported for the self-hosted runner applica
 The following processor architectures are supported for the self-hosted runner application.
 
 * `x64` - Linux, macOS, Windows.
-* `ARM64` - Linux, macOS{% ifversion actions-windows-arm %}, Windows (currently in beta){% endif %}.
+* `ARM64` - Linux, macOS{% ifversion actions-windows-arm %}, Windows (currently in {% data variables.release-phases.public_preview %}){% endif %}.
 * `ARM32` - Linux.
 
 {% ifversion ghes %}

content/actions/hosting-your-own-runners/managing-self-hosted-runners/customizing-the-containers-used-by-jobs.md

@@ -11,7 +11,7 @@ shortTitle: Customize containers used by jobs
 
 {% note %}
 
-**Note**: This feature is currently in beta and is subject to change.
+**Note**: This feature is currently in {% data variables.release-phases.public_preview %} and is subject to change.
 
 {% endnote %}
 

content/actions/sharing-automations/creating-actions/metadata-syntax-for-github-actions.md

@@ -88,7 +88,7 @@ For example, if a workflow defined the `num-octocats` and `octocat-eye-color` in
 
 ### `inputs.<input_id>.deprecationMessage`
 
-**Optional** If the input parameter is used, this `string` is logged as a warning message. You can use this warning to notify users that the input is deprecated and mention any alternatives.
+**Optional** If the input parameter is used, this `string` is logged as a warning message. You can use this warning to notify users that the input is {% data variables.release-phases.closing_down %} and mention any alternatives.
 
 ## `outputs` for Docker container and JavaScript actions
 

content/actions/using-github-hosted-runners/using-larger-runners/running-jobs-on-larger-runners.md

@@ -199,7 +199,7 @@ Because macOS arm64 does not support Node 12, macOS {% data variables.actions.ho
 
 {% note %}
 
-**Note:** ARM-powered runners are currently in beta and are subject to change.
+**Note:** ARM-powered runners are currently in {% data variables.release-phases.public_preview %} and are subject to change.
 
 {% endnote %}
 

content/admin/administering-your-instance/administering-your-instance-from-the-command-line/command-line-utilities.md

@@ -210,7 +210,7 @@ $ ghe-es-index-status -do | column -ts,
 
 ### ghe-legacy-github-services-report
 
-This utility lists repositories on your appliance that use {% data variables.product.prodname_dotcom %} Services, an integration method that will be discontinued on October 1, 2018. Users on your appliance may have set up {% data variables.product.prodname_dotcom %} Services to create notifications for pushes to certain repositories. For more information, see "[Announcing the deprecation of {% data variables.product.prodname_dotcom %} Services](https://developer.github.com/changes/2018-04-25-github-services-deprecation/)" on {% data variables.product.prodname_blog %}. For more information about this command or for additional options, use the `-h` flag.
+This utility lists repositories on your appliance that use {% data variables.product.prodname_dotcom %} Services, an integration that was discontinued on October 1, 2018. Users on your appliance may have set up {% data variables.product.prodname_dotcom %} Services to create notifications for pushes to certain repositories. For more information, see "[Announcing the deprecation of {% data variables.product.prodname_dotcom %} Services](https://developer.github.com/changes/2018-04-25-github-services-deprecation/)" on {% data variables.product.prodname_blog %}. For more information about this command or for additional options, use the `-h` flag.
 
 ```shell
 ghe-legacy-github-services-report

content/admin/all-releases.md

@@ -1,6 +1,6 @@
 ---
 title: GitHub Enterprise Server releases
-intro: "Review information for each version of {% data variables.product.prodname_ghe_server %}: deprecation dates, links to documentation, and minimum recommended versions of supporting applications."
+intro: "Review information for each version of {% data variables.product.prodname_ghe_server %}: {% data variables.release-phases.closing_down %} dates, links to documentation, and minimum recommended versions of supporting applications."
 allowTitleToDifferFromFilename: true
 versions:
   ghes: '*'
@@ -16,11 +16,11 @@ shortTitle: Releases
 
 {% data variables.product.company_short %} supports the **four** most recent feature releases.
 
-We provide documentation for both supported and deprecated versions of {% data variables.product.product_name %}. We do not maintain or update the documentation for deprecated versions.
+We provide documentation for both supported and unsupported versions of {% data variables.product.product_name %}. We do not maintain or update the documentation for unsupported versions.
 
 For information about the latest release, see the [{% data variables.product.prodname_enterprise %}](https://github.com/enterprise) website.
 
-| Version | Release | Deprecation | Supported | Release notes | Documentation |
+| Version | Release | {% data variables.release-phases.closing_down_caps %} date | Supported | Release notes | Documentation |
 | :- | :- | :- | :-: | :- | :- |
 {%- for version in enterpriseServerReleases.supported %}
 {%- assign currentDate = 'now' | date: '%s' %}
@@ -34,11 +34,11 @@ For information about the latest release, see the [{% data variables.product.pro
 | {{version}} | {{enterpriseServerReleases.dates[version].releaseDate}} | {{enterpriseServerReleases.dates[version].deprecationDate}} | {% octicon "x" aria-label="Not supported" %} | [{{version}} release notes](https://enterprise.github.com/releases/series/{{version}}) | [{{version}} documentation](/enterprise/{{version}}) |
 {%- endfor %}
 
-### Deprecated developer documentation
+### Developer documentation that is {% data variables.release-phases.closing_down %}
 
 We hosted developer documentation for {% data variables.product.product_name %} on a separate site until the 2.17 release. We provide developer documentation for version 2.16 and earlier, but do not maintain or update the documentation.
 
-| Version | Release | Deprecation | Developer documentation |
+| Version | Release | {% data variables.release-phases.closing_down_caps %} date | Developer documentation |
 | :- | :- | :- | :- |
 {%- for version in enterpriseServerReleases.deprecatedReleasesOnDeveloperSite %}
 | {{version}} | {{enterpriseServerReleases.dates[version].releaseDate}} | {{enterpriseServerReleases.dates[version].deprecationDate}} | [{{version}} developer documentation](https://developer.github.com/enterprise/{{version}}) |

content/admin/configuring-settings/configuring-user-applications-for-your-enterprise/configuring-interactive-maps.md

@@ -23,7 +23,7 @@ To enable interactive maps, you must provide authentication credentials for Azur
 
 {% warning %}
 
-**Warning**: Authentication with Azure Maps using an API token is deprecated in {% data variables.product.product_name %} {{ allVersions[currentVersion].currentRelease }}.{% ifversion ghes = 3.10 %}4{% elsif ghes = 3.11 %}1{% endif %} and later. If you upgrade to the latest release of {% data variables.product.product_name %} on an instance already configured to authenticate with an API token, interactive maps will be disabled. You must reconfigure authentication using role-based access control (RBAC) for an application on a Microsoft Entra ID (previously known as Azure AD) tenant. {% data reusables.enterprise.azure-maps-auth-deprecation-link %}
+**Warning**: Authentication with Azure Maps using an API token is {% data variables.release-phases.retired %} in {% data variables.product.product_name %} {{ allVersions[currentVersion].currentRelease }}.{% ifversion ghes = 3.10 %}4{% elsif ghes = 3.11 %}1{% endif %} and later. If you upgrade to the latest release of {% data variables.product.product_name %} on an instance already configured to authenticate with an API token, interactive maps will be disabled. You must reconfigure authentication using role-based access control (RBAC) for an application on a Microsoft Entra ID (previously known as Azure AD) tenant. {% data reusables.enterprise.azure-maps-auth-deprecation-link %}
 
 {% endwarning %}
 

content/admin/enforcing-policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-personal-access-tokens-in-your-enterprise.md

@@ -12,7 +12,7 @@ redirect_from:
 
 **Note**: {% data reusables.user-settings.pat-v2-beta %}
 
-During the beta, enterprises must opt in to {% data variables.product.pat_v2 %}s. If your enterprise has not already opted-in, then you will be prompted to opt-in and set policies when you follow the steps below.
+During the {% data variables.release-phases.public_preview %}, enterprises must opt in to {% data variables.product.pat_v2 %}s. If your enterprise has not already opted-in, then you will be prompted to opt-in and set policies when you follow the steps below.
 
 Even if an enterprise has not opted in to {% data variables.product.pat_v2 %}s, organizations owned by the enterprise can still opt in. All users, including {% data variables.product.prodname_emus %}, can create {% data variables.product.pat_v2 %}s that can access resources owned by the user (such as repositories created under their account) even if the enterprise has not opted in to {% data variables.product.pat_v2 %}s.
 

content/admin/managing-accounts-and-repositories/managing-repositories-in-your-enterprise/accessing-user-owned-repositories-in-your-enterprise.md

@@ -15,7 +15,7 @@ redirect_from:
 
 {% note %}
 
-**Note:** Temporarily accessing user-owned repositories is currently in beta for {% data variables.product.prodname_emus %} and subject to change.
+**Note:** Temporarily accessing user-owned repositories is currently in {% data variables.release-phases.public_preview %} for {% data variables.product.prodname_emus %} and subject to change.
 
 {% endnote %}
 

content/admin/managing-accounts-and-repositories/managing-repositories-in-your-enterprise/viewing-user-owned-repositories-in-your-enterprise.md

@@ -15,7 +15,7 @@ redirect_from:
 
 {% note %}
 
-**Note:** Viewing user-owned repositories is currently in beta for {% data variables.product.prodname_emus %} and subject to change.
+**Note:** Viewing user-owned repositories is currently in {% data variables.release-phases.public_preview %} for {% data variables.product.prodname_emus %} and subject to change.
 
 {% endnote %}
 

content/admin/managing-github-actions-for-your-enterprise/enabling-github-actions-for-github-enterprise-server/enabling-github-actions-with-google-cloud-storage.md

@@ -17,7 +17,7 @@ redirect_from:
 
 {% note %}
 
-**Note:** {% data variables.product.prodname_actions %} support for Google Cloud Storage is currently in beta and subject to change.
+**Note:** {% data variables.product.prodname_actions %} support for Google Cloud Storage is currently in {% data variables.release-phases.public_preview %} and subject to change.
 
 {% endnote %}
 

content/admin/managing-iam/provisioning-user-accounts-with-scim/configuring-authentication-and-provisioning-with-pingfederate.md

@@ -24,7 +24,7 @@ This guide will help you to set up both SAML authentication and SCIM provisionin
 
 Before you start, please note the following:
 
-* The use of PingFederate as an IdP for {% data variables.product.prodname_ghe_server %} is in beta. Please contact your account team to provide feedback.
+* The use of PingFederate as an IdP for {% data variables.product.prodname_ghe_server %} is in {% data variables.release-phases.public_preview %}. Please contact your account team to provide feedback.
 * This guide is based on PingFederate version 12.1. Instructions may vary for other versions.
 * This guide assumes that you are using an LDAP server as the backing data store. JDBC data stores should work, but the instructions may vary slightly.
 * This guide provides the minimal steps to configure a working setup. Because your identity directory may be connected to PingFederate differently, you’ll need to pick the correct data attributes for SAML and SCIM based on what is available from your backing data store.

content/admin/managing-iam/provisioning-user-accounts-with-scim/configuring-scim-provisioning-for-users.md

@@ -31,13 +31,13 @@ If you use a partner IdP, you can simplify the configuration of SCIM provisionin
 
 ## Who needs to follow these instructions?
 
-Even if your instance already uses SAML authentication, or if you were enrolled in the SCIM private beta on a previous {% data variables.product.prodname_ghe_server %} version, you must ensure you have followed **all instructions in this guide** to enable SCIM in version 3.14 and later.
+Even if your instance already uses SAML authentication, or if you were enrolled in the SCIM {% data variables.release-phases.private_preview %} on a previous {% data variables.product.prodname_ghe_server %} version, you must ensure you have followed **all instructions in this guide** to enable SCIM in version 3.14 and later.
 
 This guide applies in any of the following situations.
 
 * You're **setting up SAML and SCIM for the first time**: you'll follow these instructions to get started.
 * You **already use SAML authentication**: you'll need to enable SCIM on your instance, plus either reconfigure SAML with an IdP application that supports automated provisioning or set up a SCIM integration with the REST API.
-* You were **enrolled in the SCIM private beta**: you'll need to reenable SCIM on your instance and, if you're using a partner IdP, reconfigure your settings on an updated IdP application.
+* You were **enrolled in the SCIM {% data variables.release-phases.private_preview %}**: you'll need to reenable SCIM on your instance and, if you're using a partner IdP, reconfigure your settings on an updated IdP application.
 
 {% endif %}
 
@@ -100,7 +100,7 @@ To ensure you can continue to sign in and configure settings when SCIM is enable
 
 > [!NOTE] Complete this section if either of the following situations applies:
 > * If you have **not already enabled SAML authentication**, you will need to do so before you can enable SCIM.
-> * If you already use SAML authentication and want to use a **partner IdP for both authentication and provisioning**, or if you're **upgrading from the SCIM private beta**, you must reconfigure SAML using a new application.
+> * If you already use SAML authentication and want to use a **partner IdP for both authentication and provisioning**, or if you're **upgrading from the SCIM {% data variables.release-phases.private_preview %}**, you must reconfigure SAML using a new application.
 
 1. Sign in to your instance as a user with access to the Management Console.
 1. Go to the "Authentication" section of the Management Console. For instructions, see "[AUTOTITLE](/admin/managing-iam/using-saml-for-enterprise-iam/configuring-saml-single-sign-on-for-your-enterprise#configuring-saml-sso)."
@@ -171,7 +171,7 @@ To use a partner IdP's application for both authentication and provisioning, rev
 
 ### Configuring provisioning for other identity management systems
 
-If you don't use a partner IdP, or if you only use a partner IdP for authentication, you can manage the lifecycle of user accounts using {% data variables.product.company_short %}'s REST API endpoints for SCIM provisioning. These endpoints are in beta and subject to change. See "[AUTOTITLE](/admin/identity-and-access-management/provisioning-user-accounts-for-enterprise-managed-users/provisioning-users-and-groups-with-scim-using-the-rest-api)."
+If you don't use a partner IdP, or if you only use a partner IdP for authentication, you can manage the lifecycle of user accounts using {% data variables.product.company_short %}'s REST API endpoints for SCIM provisioning. These endpoints are in {% data variables.release-phases.public_preview %} and subject to change. See "[AUTOTITLE](/admin/identity-and-access-management/provisioning-user-accounts-for-enterprise-managed-users/provisioning-users-and-groups-with-scim-using-the-rest-api)."
 
 {% ifversion emu-public-scim-schema %}
 

content/admin/managing-iam/provisioning-user-accounts-with-scim/configuring-scim-provisioning-with-okta.md

@@ -84,7 +84,7 @@ After your {% data variables.enterprise.prodname_emu_enterprise %} has been crea
 
 ## 1. Configure SAML
 
-During the public beta of SCIM on {% data variables.product.prodname_ghe_server %}, you will use the **GitHub AE** application in Okta to configure SAML authentication and SCIM provisioning. Do **not** use the "{% data variables.product.prodname_ghe_server %}" application, which is incompatible with {% data variables.product.prodname_dotcom %}'s latest SCIM API endpoints.
+During the {% data variables.release-phases.public_preview %} of SCIM on {% data variables.product.prodname_ghe_server %}, you will use the **GitHub AE** application in Okta to configure SAML authentication and SCIM provisioning. Do **not** use the "{% data variables.product.prodname_ghe_server %}" application, which is incompatible with {% data variables.product.prodname_dotcom %}'s latest SCIM API endpoints.
 
 Before starting this section, ensure you have followed steps **1 and 2** in "[AUTOTITLE](/admin/managing-iam/provisioning-user-accounts-with-scim/configuring-scim-provisioning-for-users)."
 

content/admin/managing-iam/provisioning-user-accounts-with-scim/user-provisioning-with-scim-on-ghes.md

@@ -45,7 +45,7 @@ The following IdPs are partner IdPs. They offer an application that you can use
 * Okta
 * PingFederate (beta)
 
-When you use a single partner IdP for both authentication and provisioning, {% data variables.product.company_short %} provides support for the application on the partner IdP and the IdP's integration with {% data variables.product.prodname_dotcom %}. Support for PingFederate is in beta.
+When you use a single partner IdP for both authentication and provisioning, {% data variables.product.company_short %} provides support for the application on the partner IdP and the IdP's integration with {% data variables.product.prodname_dotcom %}. Support for PingFederate is in {% data variables.release-phases.public_preview %}.
 
 ### Other identity management systems
 
@@ -57,7 +57,7 @@ If you cannot use a single partner IdP for both authentication and provisioning,
 
 {% else %}
 
-During the private beta, your account team will provide documentation for the configuration of SCIM for {% data variables.product.product_name %} on a supported IdP.
+During the {% data variables.release-phases.private_preview %}, your account team will provide documentation for the configuration of SCIM for {% data variables.product.product_name %} on a supported IdP.
 
 {% endif %}
 

content/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/streaming-the-audit-log-for-your-enterprise.md

@@ -309,7 +309,7 @@ To restart streaming, click **Resume stream**.
 
 ## Enabling audit log streaming of API requests
 
->[!NOTE] This feature is currently in public beta and subject to change.
+>[!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 %}

content/admin/monitoring-and-managing-your-instance/configuring-clustering/deferring-database-seeding.md

@@ -19,7 +19,7 @@ redirect_from:
 {%- ifversion ghes = 3.12 %} 3.12.1{%- endif %}
 {%- ifversion ghes = 3.11 %} 3.11.7{%- endif %}
 {%- ifversion ghes = 3.10 %} 3.10.10{%- endif %}
- and{% endif %} is available as a public beta.
+ and{% endif %} is available as a {% data variables.release-phases.public_preview %}.
 
 Adding a new MySQL replica node to your cluster when your primary node has more than seven days of data will normally trigger database seeding which can take several hours depending on the amount of data. You can choose to defer database seeding, allowing the config apply run to complete sooner, resulting in being able to open your appliance to traffic sooner.
 

content/admin/monitoring-and-managing-your-instance/monitoring-your-instance/generating-a-health-check-for-your-enterprise.md

@@ -19,7 +19,7 @@ redirect_from:
 
 {% note %}
 
-**Note:** Generating a Health Check is currently in beta for {% data variables.product.prodname_ghe_server %} and subject to change.
+**Note:** Generating a Health Check is currently in {% data variables.release-phases.public_preview %} for {% data variables.product.prodname_ghe_server %} and subject to change.
 
 {% endnote %}
 

content/apps/creating-github-apps/authenticating-with-a-github-app/generating-a-user-access-token-for-a-github-app.md

@@ -61,7 +61,7 @@ If your app runs in the browser, you should use the web application flow to gene
 
 {% note %}
 
-**Note:** The device flow is in public beta and subject to change.
+**Note:** The device flow is in {% data variables.release-phases.public_preview %} and subject to change.
 
 {% endnote %}
 

content/apps/github-marketplace/creating-apps-for-github-marketplace/requirements-for-listing-an-app.md

@@ -38,7 +38,7 @@ All listings should meet the following requirements, regardless of whether they
 * Listings must have a relevant description of the application.
 * Listings must specify a pricing plan.
 * Apps must provide value to customers and integrate with the platform in some way beyond authentication.
-* Apps must be publicly available in {% data variables.product.prodname_marketplace %} and cannot be in beta or available by invite only, with the exception of {% data variables.product.prodname_copilot_extensions_short %}.
+* Apps must be publicly available in {% data variables.product.prodname_marketplace %} and cannot be in {% data variables.release-phases.public_preview %} or available by invite only, with the exception of {% data variables.product.prodname_copilot_extensions_short %}.
 * Apps must have webhook events set up to notify the publisher of any plan changes or cancellations using the {% data variables.product.prodname_marketplace %} API. For more information, see "[AUTOTITLE](/apps/github-marketplace/using-the-github-marketplace-api-in-your-app)."
 
 For more information on providing a good customer experience, see "[AUTOTITLE](/apps/github-marketplace/creating-apps-for-github-marketplace/customer-experience-best-practices-for-apps)."
@@ -63,7 +63,7 @@ To publish an extension, it must be owned by an organization account with Verifi
 
 The requirements to publish a {% data variables.product.prodname_copilot_extension_short %} are the same as the requirements for free apps, with the following exceptions:
 * Your extension must provide a clear and descriptive response to a prompt like "What can you do?" or "List your capabilities".
-* Your extension can be in beta as long as that is clearly communicated in the listing description. If you are using a waitlist, you must also include a link to sign up at the top of the description. Someone from the {% data variables.product.github %} review team will join the waitlist and email your technical lead requesting access for testing.
+* Your extension can be in {% data variables.release-phases.public_preview %} as long as that is clearly communicated in the listing description. If you are using a waitlist, you must also include a link to sign up at the top of the description. Someone from the {% data variables.product.github %} review team will join the waitlist and email your technical lead requesting access for testing.
 * You must include links to two videos that demonstrate the following:
     * A few example prompts and responses from your extension
     * A net new user installing, authenticating, and sending their first prompt to your extension. These videos are private to {% data variables.product.github %} and are used solely for reviewing your listing submission. It's okay if the videos are brief and unedited.

content/billing/managing-billing-for-git-large-file-storage/viewing-your-git-large-file-storage-usage.md

@@ -37,7 +37,7 @@ shortTitle: View Git LFS usage
 {% ifversion billing-beta-enterprise %}
 {% note %}
 
-**Note:** If your organization belongs to an enterprise enrolled in the Billing private beta for {% data variables.large_files.product_name_short %}, you will not see {% data variables.large_files.product_name_short %} usage on the existing billing pages.
+**Note:** If your organization belongs to an enterprise enrolled in the Billing {% data variables.release-phases.private_preview %} for {% data variables.large_files.product_name_short %}, you will not see {% data variables.large_files.product_name_short %} usage on the existing billing pages.
 
 {% endnote %}
 {% endif %}
@@ -54,7 +54,7 @@ shortTitle: View Git LFS usage
 {% ifversion billing-beta-enterprise %}
 {% note %}
 
-**Note:** If your enterprise is enrolled in the Billing private beta for {% data variables.large_files.product_name_short %}, you will not see {% data variables.large_files.product_name_short %} usage on the existing billing pages.
+**Note:** If your enterprise is enrolled in the Billing {% data variables.release-phases.private_preview %} for {% data variables.large_files.product_name_short %}, you will not see {% data variables.large_files.product_name_short %} usage on the existing billing pages.
 
 {% endnote %}
 {% endif %}

content/billing/managing-billing-for-github-actions/viewing-your-github-actions-usage.md

@@ -39,7 +39,7 @@ Anyone can view {% data variables.product.prodname_actions %} usage for their ow
 {% ifversion billing-beta-enterprise %}
 {% note %}
 
-**Note:** If your organization belongs to an enterprise enrolled in the Billing private beta for {% data variables.product.prodname_actions %}, you will not see {% data variables.product.prodname_actions %} usage on the existing billing pages.
+**Note:** If your organization belongs to an enterprise enrolled in the Billing {% data variables.release-phases.private_preview %} for {% data variables.product.prodname_actions %}, you will not see {% data variables.product.prodname_actions %} usage on the existing billing pages.
 
 {% endnote %}
 {% endif %}
@@ -58,7 +58,7 @@ Organization owners and billing managers can view {% data variables.product.prod
 {% ifversion billing-beta-enterprise %}
 {% note %}
 
-**Note:** If your enterprise is enrolled in the Billing private beta for {% data variables.product.prodname_actions %}, you will not see {% data variables.product.prodname_actions %} usage on the existing billing pages.
+**Note:** If your enterprise is enrolled in the Billing {% data variables.release-phases.private_preview %} for {% data variables.product.prodname_actions %}, you will not see {% data variables.product.prodname_actions %} usage on the existing billing pages.
 
 {% endnote %}
 {% endif %}

content/billing/using-the-enhanced-billing-platform-for-enterprises/about-enhanced-billing-for-git-large-file-storage.md

@@ -9,7 +9,7 @@ topics:
   - LFS
   - Enterprise
 shortTitle: About Git LFS billing
-permissions: The enhanced billing platform is available to all enterprise accounts, and organizations owned by enterprise accounts, created after June 2, 2024. Enterprises that participated in the beta program also have access to the enhanced billing platform.
+permissions: The enhanced billing platform is available to all enterprise accounts, and organizations owned by enterprise accounts, created after June 2, 2024. Enterprises that participated in the {% data variables.release-phases.public_preview %} program also have access to the enhanced billing platform.
 ---
 
 ## About billing for {% data variables.large_files.product_name_long %}

content/billing/using-the-enhanced-billing-platform-for-enterprises/about-the-billing-cycle.md

@@ -6,7 +6,7 @@ versions:
 type: overview
 topics:
   - Enterprise
-permissions: The enhanced billing platform is available to all enterprise accounts, and organizations owned by enterprise accounts, created after June 2, 2024. Enterprises that participated in the beta program also have access to the enhanced billing platform.
+permissions: The enhanced billing platform is available to all enterprise accounts, and organizations owned by enterprise accounts, created after June 2, 2024. Enterprises that participated in the {% data variables.release-phases.public_preview %} program also have access to the enhanced billing platform.
 ---
 
 >[!IMPORTANT] If you are on not on the new billing platform, this article does not apply to you. To check if you are on the new billing platform, see "[How do I know if I can access the enhanced billing platform?](/billing/using-the-enhanced-billing-platform-for-enterprises/about-the-enhanced-billing-platform-for-enterprises#how-do-i-know-if-i-can-access-the-enhanced-billing-platform)." For more information about the billing cycle for your enterprise account, see "[AUTOTITLE](/billing/managing-your-github-billing-settings/changing-the-duration-of-your-billing-cycle#changing-the-duration-of-your-enterprise-accounts-billing-cycle)."

content/billing/using-the-enhanced-billing-platform-for-enterprises/about-the-enhanced-billing-platform-for-enterprises.md

@@ -6,7 +6,7 @@ versions:
 type: overview
 topics:
   - Enterprise
-permissions: The enhanced billing platform is available to all enterprise accounts, and organizations owned by enterprise accounts, created after June 2, 2024. Enterprises that participated in the beta program also have access to the enhanced billing platform.
+permissions: The enhanced billing platform is available to all enterprise accounts, and organizations owned by enterprise accounts, created after June 2, 2024. Enterprises that participated in the {% data variables.release-phases.public_preview %} program also have access to the enhanced billing platform.
 shortTitle: About the enhanced billing platform
 ---
 
@@ -42,7 +42,7 @@ With the enhanced billing platform, you can:
 
 ## How do I know if I can access the enhanced billing platform?
 
-You have access to the enhanced billing platform if you have an enterprise account, or if you are part of an organization owned by an enterprise account, created after June 2, 2024. Enterprises that participated in the beta program also have access to the enhanced billing platform. To check if you have access:
+You have access to the enhanced billing platform if you have an enterprise account, or if you are part of an organization owned by an enterprise account, created after June 2, 2024. Enterprises that participated in the {% data variables.release-phases.public_preview %} program also have access to the enhanced billing platform. To check if you have access:
 
 {% data reusables.enterprise-accounts.access-enterprise %}
 

content/billing/using-the-enhanced-billing-platform-for-enterprises/adding-seats-to-your-enterprise-account.md

@@ -6,7 +6,7 @@ versions:
 type: overview
 topics:
   - Enterprise
-permissions: The enhanced billing platform is available to all enterprise accounts, and organizations owned by enterprise accounts, created after June 2, 2024. Enterprises that participated in the beta program also have access to the enhanced billing platform.
+permissions: The enhanced billing platform is available to all enterprise accounts, and organizations owned by enterprise accounts, created after June 2, 2024. Enterprises that participated in the {% data variables.release-phases.public_preview %} program also have access to the enhanced billing platform.
 shortTitle: Add seats to your enterprise
 ---
 

content/billing/using-the-enhanced-billing-platform-for-enterprises/charging-business-units.md

@@ -6,7 +6,7 @@ versions:
 type: how_to
 topics:
   - Enterprise
-permissions: The enhanced billing platform is available to all enterprise accounts, and organizations owned by enterprise accounts, created after June 2, 2024. Enterprises that participated in the beta program also have access to the enhanced billing platform.
+permissions: The enhanced billing platform is available to all enterprise accounts, and organizations owned by enterprise accounts, created after June 2, 2024. Enterprises that participated in the {% data variables.release-phases.public_preview %} program also have access to the enhanced billing platform.
 shortTitle: Charge business units
 ---
 

content/billing/using-the-enhanced-billing-platform-for-enterprises/estimating-spending-for-your-enterprise.md

@@ -6,7 +6,7 @@ versions:
 type: how_to
 topics:
   - Enterprise
-permissions: The enhanced billing platform is available to all enterprise accounts, and organizations owned by enterprise accounts, created after June 2, 2024. Enterprises that participated in the beta program also have access to the enhanced billing platform.
+permissions: The enhanced billing platform is available to all enterprise accounts, and organizations owned by enterprise accounts, created after June 2, 2024. Enterprises that participated in the {% data variables.release-phases.public_preview %} program also have access to the enhanced billing platform.
 shortTitle: Estimate spending
 ---
 

content/billing/using-the-enhanced-billing-platform-for-enterprises/gathering-insights-on-your-spending.md

@@ -6,7 +6,7 @@ versions:
 type: how_to
 topics:
   - Enterprise
-permissions: The enhanced billing platform is available to all enterprise accounts, and organizations owned by enterprise accounts, created after June 2, 2024. Enterprises that participated in the beta program also have access to the enhanced billing platform.<br><br> As an enterprise owner or billing manager you can view and download your enterprise's usage. As an organization owner, you can view and download usage for the organizations you manage
+permissions: The enhanced billing platform is available to all enterprise accounts, and organizations owned by enterprise accounts, created after June 2, 2024. Enterprises that participated in the {% data variables.release-phases.public_preview %} program also have access to the enhanced billing platform.<br><br> As an enterprise owner or billing manager you can view and download your enterprise's usage. As an organization owner, you can view and download usage for the organizations you manage
 shortTitle: Gather insights
 ---
 

content/billing/using-the-enhanced-billing-platform-for-enterprises/index.md

@@ -4,7 +4,7 @@ shortTitle: Enhanced billing platform
 intro: 'The enhanced billing platform offers better spending control and detailed visibility to help you understand your usage with more granular controls.'
 redirect_from:
   - /early-access/billing/billing-private-beta
-permissions: The enhanced billing platform is available to all enterprise accounts, and organizations owned by enterprise accounts, created after June 2, 2024. Enterprises that participated in the beta program also have access to the enhanced billing platform.
+permissions: The enhanced billing platform is available to all enterprise accounts, and organizations owned by enterprise accounts, created after June 2, 2024. Enterprises that participated in the {% data variables.release-phases.public_preview %} program also have access to the enhanced billing platform.
 versions:
   feature: enhanced-billing-platform
 children:

content/billing/using-the-enhanced-billing-platform-for-enterprises/managing-your-payment-and-billing-information.md

@@ -6,7 +6,7 @@ versions:
 type: how_to
 topics:
   - Enterprise
-permissions: The enhanced billing platform is available to all enterprise accounts, and organizations owned by enterprise accounts, created after June 2, 2024. Enterprises that participated in the beta program also have access to the enhanced billing platform.
+permissions: The enhanced billing platform is available to all enterprise accounts, and organizations owned by enterprise accounts, created after June 2, 2024. Enterprises that participated in the {% data variables.release-phases.public_preview %} program also have access to the enhanced billing platform.
 shortTitle: Manage your payment information
 ---
 

content/billing/using-the-enhanced-billing-platform-for-enterprises/preventing-overspending.md

@@ -6,7 +6,7 @@ versions:
 type: how_to
 topics:
   - Enterprise
-permissions: The enhanced billing platform is available to all enterprise accounts, and organizations owned by enterprise accounts, created after June 2, 2024. Enterprises that participated in the beta program also have access to the enhanced billing platform.
+permissions: The enhanced billing platform is available to all enterprise accounts, and organizations owned by enterprise accounts, created after June 2, 2024. Enterprises that participated in the {% data variables.release-phases.public_preview %} program also have access to the enhanced billing platform.
 shortTitle: Prevent overspending
 ---
 

content/billing/using-the-enhanced-billing-platform-for-enterprises/roles-for-the-enhanced-billing-platform.md

@@ -6,7 +6,7 @@ versions:
 type: reference
 topics:
   - Enterprise
-permissions: The enhanced billing platform is available to all enterprise accounts, and organizations owned by enterprise accounts, created after June 2, 2024. Enterprises that participated in the beta program also have access to the enhanced billing platform.
+permissions: The enhanced billing platform is available to all enterprise accounts, and organizations owned by enterprise accounts, created after June 2, 2024. Enterprises that participated in the {% data variables.release-phases.public_preview %} program also have access to the enhanced billing platform.
 ---
 
 Three roles have access to the enhanced billing platform: enterprise owners, billing managers, and organization owners. See "[AUTOTITLE](/admin/managing-accounts-and-repositories/managing-users-in-your-enterprise/roles-in-an-enterprise)."

content/code-security/code-scanning/managing-code-scanning-alerts/about-code-scanning-alerts.md

@@ -86,7 +86,7 @@ When you click through to see details for the alert, you can see that the file p
 
 {% note %}
 
-**Note:** Experimental alerts for {% data variables.product.prodname_code_scanning %} were available a beta release for JavaScript using experimental technology in the {% data variables.product.prodname_codeql %} action. This feature was deprecated and sunset. For more information, see [{% data variables.product.prodname_codeql %} {% data variables.product.prodname_code_scanning %} deprecates ML-powered alerts](https://github.blog/changelog/2023-09-29-codeql-code-scanning-deprecates-ml-powered-alerts/).
+**Note:** Experimental alerts for {% data variables.product.prodname_code_scanning %} were available a {% data variables.release-phases.public_preview %} release for JavaScript using experimental technology in the {% data variables.product.prodname_codeql %} action. This feature was {% data variables.release-phases.retired %}. For more information, see [{% data variables.product.prodname_codeql %} {% data variables.product.prodname_code_scanning %} deprecates ML-powered alerts](https://github.blog/changelog/2023-09-29-codeql-code-scanning-deprecates-ml-powered-alerts/).
 
 {% endnote %}
 

content/code-security/code-scanning/managing-your-code-scanning-configuration/editing-your-configuration-of-default-setup.md

@@ -18,7 +18,7 @@ topics:
 After running an initial analysis of your code with default setup, you may need to make changes to your configuration to better meet your code security needs. For existing configurations of default setup, you can edit:
 * Which languages default setup will analyze.
 * The query suite run during analysis. For more information on the available query suites, see "[AUTOTITLE](/code-security/code-scanning/managing-your-code-scanning-configuration/codeql-query-suites)."{% ifversion codeql-threat-models %}
-* The threat models (beta) to use for analysis. Your choice of threat model determines which sources of tainted data are treated as a risk to your application. During the beta, threat models are supported only for analysis of {% data variables.code-scanning.code_scanning_threat_model_support %}. For more information about threat models, see "[Including local sources of tainted data in default setup](#including-local-sources-of-tainted-data-in-default-setup)."
+* The threat models (beta) to use for analysis. Your choice of threat model determines which sources of tainted data are treated as a risk to your application. During the {% data variables.release-phases.public_preview %}, threat models are supported only for analysis of {% data variables.code-scanning.code_scanning_threat_model_support %}. For more information about threat models, see "[Including local sources of tainted data in default setup](#including-local-sources-of-tainted-data-in-default-setup)."
 {% endif %}
 
 {% ifversion codeql-model-packs %}
@@ -70,7 +70,7 @@ For more information, see "[AUTOTITLE](/code-security/code-scanning/managing-you
 
 {% data reusables.code-scanning.beta-threat-models %}
 
-If your codebase only considers remote network requests to be potential sources of tainted data, then we recommend using the default threat model. If your codebase considers sources other than network requests to potentially contain tainted data, then you can use threat models to add these additional sources to your {% data variables.product.prodname_codeql %} analysis. During the beta, you can add local sources (for example: command-line arguments, environment variables, file systems, and databases) that your codebase may consider to be additional sources of tainted data.
+If your codebase only considers remote network requests to be potential sources of tainted data, then we recommend using the default threat model. If your codebase considers sources other than network requests to potentially contain tainted data, then you can use threat models to add these additional sources to your {% data variables.product.prodname_codeql %} analysis. During the {% data variables.release-phases.public_preview %}, you can add local sources (for example: command-line arguments, environment variables, file systems, and databases) that your codebase may consider to be additional sources of tainted data.
 
 You can edit the threat model used in a default setup configuration. For more information, see "[Customizing your existing configuration of default setup](#customizing-your-existing-configuration-of-default-setup)."
 

content/code-security/code-scanning/managing-your-code-scanning-configuration/set-code-scanning-merge-protection.md

@@ -17,7 +17,7 @@ topics:
 
 **Notes:**
 
-* This feature is currently in beta and subject to change.
+* This feature is currently in {% data variables.release-phases.public_preview %} and subject to change.
 * Merge protection with rulesets is not related to status checks. For more information about status checks, see "[AUTOTITLE](/pull-requests/collaborating-with-pull-requests/collaborating-on-repositories-with-code-quality-features/about-status-checks)."
 * Merge protection with rulesets will not apply to merge queue groups or {% data variables.product.prodname_dependabot %} pull requests analyzed by default setup.
 

content/code-security/codeql-cli/getting-started-with-the-codeql-cli/analyzing-your-code-with-codeql-queries.md

@@ -74,7 +74,7 @@ You must specify `<database>`, `--format`, and `--output`. You can specify addit
 | <code><span style="white-space: nowrap;">--download</span></code> | {% octicon "x" aria-label="Optional" %}  | Use if some of your {% data variables.product.prodname_codeql %} query packs are not yet on disk and need to be downloaded before running queries. |
 | <code><span style="white-space: nowrap;">--threads</span></code> | {% octicon "x" aria-label="Optional" %}  | Use if you want to use more than one thread to run queries. The default value is `1`. You can specify more threads to speed up query execution. To set the number of threads to the number of logical processors, specify `0`. |
 | <code><span style="white-space: nowrap;">--verbose</span></code> | {% octicon "x" aria-label="Optional" %}  | Use to get more detailed information about the analysis process and diagnostic data from the database creation process. |
-| <code><span style="white-space: nowrap;">--threat-model</span></code> | {% octicon "x" aria-label="Optional" %}  | (Beta) Use to add threat models to configure additional sources in your {% data variables.product.prodname_codeql %} analysis. During the beta, threat models are supported only by Java analysis. For more information, see "[AUTOTITLE](/code-security/codeql-cli/codeql-cli-manual/database-analyze#--threat-modelname)." |
+| <code><span style="white-space: nowrap;">--threat-model</span></code> | {% octicon "x" aria-label="Optional" %}  | (Beta) Use to add threat models to configure additional sources in your {% data variables.product.prodname_codeql %} analysis. During the {% data variables.release-phases.public_preview %}, threat models are supported only by Java analysis. For more information, see "[AUTOTITLE](/code-security/codeql-cli/codeql-cli-manual/database-analyze#--threat-modelname)." |
 
 {% note %}
 

content/code-security/codeql-cli/getting-started-with-the-codeql-cli/customizing-analysis-with-codeql-packs.md

@@ -28,7 +28,7 @@ There are{% ifversion codeql-model-packs %} three{% else %} two{% endif %} types
 
 * Library packs are designed to be used by query packs (or other library packs) and do not contain queries themselves. The libraries are not compiled separately.{% ifversion codeql-model-packs %}
 
-* Model packs can be used to expand {% data variables.product.prodname_code_scanning %} analysis to recognize libraries and frameworks that are not supported by default. Model packs are currently in beta and subject to change. During the beta, model packs are available for {% data variables.code-scanning.codeql_model_packs_support %} analysis. For more information about creating your own model packs, see "[AUTOTITLE](/code-security/codeql-cli/using-the-advanced-functionality-of-the-codeql-cli/creating-and-working-with-codeql-packs#creating-a-codeql-model-pack)."
+* Model packs can be used to expand {% data variables.product.prodname_code_scanning %} analysis to recognize libraries and frameworks that are not supported by default. Model packs are currently in {% data variables.release-phases.public_preview %} and subject to change. During the {% data variables.release-phases.public_preview %}, model packs are available for {% data variables.code-scanning.codeql_model_packs_support %} analysis. For more information about creating your own model packs, see "[AUTOTITLE](/code-security/codeql-cli/using-the-advanced-functionality-of-the-codeql-cli/creating-and-working-with-codeql-packs#creating-a-codeql-model-pack)."
 
 {% endif %}
 

content/code-security/codeql-cli/using-the-advanced-functionality-of-the-codeql-cli/creating-and-working-with-codeql-packs.md

@@ -27,7 +27,7 @@ There are{% ifversion codeql-model-packs %} three{% else %} two{% endif %} types
 
 * Library packs are designed to be used by query packs (or other library packs) and do not contain queries themselves. The libraries are not compiled separately.{% ifversion codeql-model-packs %}
 
-* Model packs can be used to expand {% data variables.product.prodname_code_scanning %} analysis to include dependencies that are not supported by default. Model packs are currently in beta and subject to change. During the beta, model packs are available for {% data variables.code-scanning.codeql_model_packs_support %} analysis. For more information about creating your own model packs, see "[Creating a {% data variables.product.prodname_codeql %} model pack](#creating-a-codeql-model-pack)."{% endif %}
+* Model packs can be used to expand {% data variables.product.prodname_code_scanning %} analysis to include dependencies that are not supported by default. Model packs are currently in {% data variables.release-phases.public_preview %} and subject to change. During the {% data variables.release-phases.public_preview %}, model packs are available for {% data variables.code-scanning.codeql_model_packs_support %} analysis. For more information about creating your own model packs, see "[Creating a {% data variables.product.prodname_codeql %} model pack](#creating-a-codeql-model-pack)."{% endif %}
 
 You can use the `pack` command in the {% data variables.product.prodname_codeql_cli %} to create {% data variables.product.prodname_codeql %} packs, add dependencies to packs, and install or update dependencies. You can also publish and download {% data variables.product.prodname_codeql %} packs using the `pack` command. For more information, see "[AUTOTITLE](/code-security/codeql-cli/using-the-advanced-functionality-of-the-codeql-cli/publishing-and-using-codeql-packs)."
 

content/code-security/codeql-for-vs-code/using-the-advanced-functionality-of-the-codeql-for-vs-code-extension/using-the-codeql-model-editor.md

@@ -35,7 +35,7 @@ The rest of this article covers the practical aspects of modelling dependencies
 
 {% note %}
 
-**Note:** To use this beta functionality, install the latest version of the {% data variables.product.prodname_codeql %} extension for {% data variables.product.prodname_vscode %}.
+**Note:** To use this {% data variables.release-phases.public_preview %} functionality, install the latest version of the {% data variables.product.prodname_codeql %} extension for {% data variables.product.prodname_vscode %}.
 
 {% endnote %}
 

content/code-security/dependabot/dependabot-alerts/viewing-and-updating-dependabot-alerts.md

@@ -79,7 +79,7 @@ For supported languages, {% data variables.product.prodname_dependabot %} automa
 
 {% note %}
 
-**Note:** During the beta release, this feature is available only for new Python advisories created _after_ April 14, 2022, and for a subset of historical Python advisories. {% data variables.product.prodname_dotcom %} is working to backfill data across additional historical Python advisories, which are added on a rolling basis. Vulnerable calls are highlighted only on the {% data variables.product.prodname_dependabot_alerts %} pages.
+**Note:** During the {% data variables.release-phases.public_preview %} release, this feature is available only for new Python advisories created _after_ April 14, 2022, and for a subset of historical Python advisories. {% data variables.product.prodname_dotcom %} is working to backfill data across additional historical Python advisories, which are added on a rolling basis. Vulnerable calls are highlighted only on the {% data variables.product.prodname_dependabot_alerts %} pages.
 
 {% endnote %}
 

content/code-security/dependabot/dependabot-auto-triage-rules/customizing-auto-triage-rules-to-prioritize-dependabot-alerts.md

@@ -60,7 +60,7 @@ For more information about enabling or disabling {% data variables.product.prodn
 
 {% note %}
 
-**Note:** During the public beta, you can create up to 10 {% data variables.dependabot.custom_rules %} for a repository.
+**Note:** During the {% data variables.release-phases.public_preview %}, you can create up to 10 {% data variables.dependabot.custom_rules %} for a repository.
 
 {% endnote %}
 
@@ -85,7 +85,7 @@ For more information about enabling or disabling {% data variables.product.prodn
 
 {% note %}
 
-**Note:** During the public beta, you can create up to 25 {% data variables.dependabot.custom_rules %} for your organization.
+**Note:** During the {% data variables.release-phases.public_preview %}, you can create up to 25 {% data variables.dependabot.custom_rules %} for your organization.
 
 {% endnote %}
 

content/code-security/dependabot/dependabot-version-updates/configuration-options-for-the-dependabot.yml-file.md

@@ -1403,17 +1403,17 @@ registries:
 
 {% endraw %}
 
-## Enabling support for beta-level ecosystems
+## Enabling support for {% data variables.release-phases.public_preview %}-level ecosystems
 
 ### `enable-beta-ecosystems`
 
 By default, {% data variables.product.prodname_dependabot %} updates the dependency manifests and lock files only for fully supported ecosystems. Use the `enable-beta-ecosystems` flag to opt in to updates for ecosystems that are not yet generally available.
 
-<!-- add list here once we get ecosystems released in beta -->
+<!-- add list here once we get ecosystems released in {% data variables.release-phases.public_preview %} -->
-There are currently no ecosystems in beta.
+There are currently no ecosystems in {% data variables.release-phases.public_preview %}.
 
 ```yaml
-# Configure beta ecosystem
+# Configure {% data variables.release-phases.public_preview %} ecosystem
 
 version: 2
 enable-beta-ecosystems: true

content/code-security/secret-scanning/managing-alerts-from-secret-scanning/evaluating-alerts.md

@@ -71,7 +71,7 @@ Once you have enabled validity checks for partner patterns for your repository,
 ## Reviewing {% data variables.product.company_short %} token metadata
 
 > [!NOTE]
-> Metadata for {% data variables.product.company_short %} tokens is currently in public beta and subject to change.
+> Metadata for {% data variables.product.company_short %} tokens is currently in {% data variables.release-phases.public_preview %} and subject to change.
 
 In the view for an active {% data variables.product.company_short %} token alert, you can review certain metadata about the token. This metadata may help you identify the token and decide what remediation steps to take.
 

content/code-security/secret-scanning/using-advanced-secret-scanning-and-push-protection-features/custom-patterns/metrics-for-custom-patterns.md

@@ -15,7 +15,7 @@ topics:
 
 Organization owners and people with admin permission for a repository can see an overview of the activity for custom patterns. The overview includes alert and push protection activity for the custom pattern during the last 30 days.
 
-> [!NOTE] Metrics for custom patterns are in public beta and subject to change.
+> [!NOTE] Metrics for custom patterns are in {% data variables.release-phases.public_preview %} and subject to change.
 
 ## Viewing metrics for custom patterns
 

content/code-security/secret-scanning/using-advanced-secret-scanning-and-push-protection-features/generic-secret-detection/about-the-detection-of-generic-secrets-with-secret-scanning.md

@@ -50,7 +50,7 @@ Since AI-powered generic secret detection may generate more false positives than
 
 ### Provide feedback
 
-Generic secret detection is currently in beta. If you encounter any issues or limitations with the feature, we recommend that you provide feedback through the **Give feedback** button listed under each detected secret in the list of alerts for the repository, organization, or enterprise. This can help the developers improve the tool and address any concerns or limitations.
+Generic secret detection is currently in {% data variables.release-phases.public_preview %}. If you encounter any issues or limitations with the feature, we recommend that you provide feedback through the **Give feedback** button listed under each detected secret in the list of alerts for the repository, organization, or enterprise. This can help the developers improve the tool and address any concerns or limitations.
 
 ## Limitations of generic secret detection
 

content/code-security/security-advisories/guidance-on-reporting-and-writing-information-about-vulnerabilities/best-practices-for-writing-repository-security-advisories.md

@@ -132,7 +132,7 @@ This is because, if a fixed version is ever released, users of the fixed version
 ### Specifying only one affected version
 
 * `= n` for the single affected version
-* Keep in mind that the `=` will not automatically include any pre-releases, alpha, or beta versions, _only_ the version specified.
+* Keep in mind that the `=` will not automatically include any public or private previews, _only_ the version specified.
 
 ### Common errors
 

content/code-security/security-overview/about-security-overview.md

@@ -84,7 +84,7 @@ For more information about these views, see {% ifversion security-overview-dashb
 
 ![Screenshot of security overview for an organization.](/assets/images/help/security-overview/security-overview-org-legacy.png)
 
-Each repository is shown in security overview with an indicator for each type of security feature and how many alerts there are of each type. If a security feature is not enabled for a repository, the indicator for that feature will be grayed out. In addition, a risk score is calculated for each repository based on its {% data variables.product.prodname_code_scanning %}, {% data variables.product.prodname_dependabot %} and {% data variables.secret-scanning.alerts %}. This score is in beta and should be used with caution. Its algorithm and approach is subject to change.
+Each repository is shown in security overview with an indicator for each type of security feature and how many alerts there are of each type. If a security feature is not enabled for a repository, the indicator for that feature will be grayed out. In addition, a risk score is calculated for each repository based on its {% data variables.product.prodname_code_scanning %}, {% data variables.product.prodname_dependabot %} and {% data variables.secret-scanning.alerts %}. This score is in {% data variables.release-phases.public_preview %} and should be used with caution. Its algorithm and approach is subject to change.
 
 | Indicator | Meaning |
 | -------- | -------- |

content/code-security/security-overview/assessing-adoption-code-security.md

@@ -84,7 +84,7 @@ In the enterprise-level view, you can view data about the enablement of features
 
 {% ifversion ghes < 3.15 %}
 
-> [!NOTE] The "Enablement trends" view is currently in beta and is subject to change.
+> [!NOTE] The "Enablement trends" view is currently in {% data variables.release-phases.public_preview %} and is subject to change.
 
 {% endif %}
 
@@ -108,7 +108,7 @@ You can view data to assess the enablement status and enablement status trends o
 
 {% ifversion ghes < 3.15 %}
 
-> [!NOTE] The "Enablement trends" view is currently in beta and is subject to change.
+> [!NOTE] The "Enablement trends" view is currently in {% data variables.release-phases.public_preview %} and is subject to change.
 
 {% endif %}
 

content/code-security/security-overview/filtering-alerts-in-security-overview.md

@@ -78,7 +78,7 @@ These qualifiers are available in all views.
 
 {% note %}
 
-**Note:** Repository properties are in public beta and subject to change.
+**Note:** Repository properties are in {% data variables.release-phases.public_preview %} and subject to change.
 
 {% endnote %}
 

content/codespaces/developing-in-a-codespace/connecting-to-a-private-network.md

@@ -27,7 +27,7 @@ There are currently two methods of accessing resources on a private network with
 
 {% warning %}
 
-**Warning**: The {% data variables.product.prodname_cli %} extension is deprecated and no longer supported.
+**Warning**: The {% data variables.product.prodname_cli %} extension is {% data variables.release-phases.closing_down %} and is no longer supported.
 
 {% endwarning %}
 

content/codespaces/developing-in-a-codespace/using-github-codespaces-with-github-cli.md

@@ -256,7 +256,7 @@ You can use the {% data variables.product.prodname_cli %} extension to create a
 
 {% note %}
 
-**Note**: The {% data variables.product.prodname_cli %} extension is currently in beta and subject to change.
+**Note**: The {% data variables.product.prodname_cli %} extension is currently in {% data variables.release-phases.public_preview %} and subject to change.
 
 {% endnote %}
 

content/codespaces/getting-started/deep-dive.md

@@ -40,7 +40,7 @@ When you create a codespace, various steps happen in the background before the c
 
 ### Step 1: VM and storage are assigned to your codespace
 
-When you create a codespace, a virtual machine (VM) is created using either the stable or beta release of the VM host image. For more information, see "[AUTOTITLE](/codespaces/setting-your-user-preferences/choosing-the-stable-or-beta-host-image)." The host image defines the version of Linux that is used for the VM. The VM is both dedicated and private to you. Having a dedicated VM ensures that you have the entire set of compute resources from that machine available to you. If necessary, this also allows you to have full root access to your container.
+When you create a codespace, a virtual machine (VM) is created using either the stable or {% data variables.release-phases.public_preview %} release of the VM host image. For more information, see "[AUTOTITLE](/codespaces/setting-your-user-preferences/choosing-the-stable-or-beta-host-image)." The host image defines the version of Linux that is used for the VM. The VM is both dedicated and private to you. Having a dedicated VM ensures that you have the entire set of compute resources from that machine available to you. If necessary, this also allows you to have full root access to your container.
 
 A [shallow clone](https://github.blog/2020-12-21-get-up-to-speed-with-partial-clone-and-shallow-clone/) is then made of your repository, or of the template repository if you're creating a codespace from a template. This is cloned into the `/workspaces` directory of the VM and subsequently mounted into the dev container. For more information, see "[About the directory structure of a codespace](#about-the-directory-structure-of-a-codespace)" below.
 

content/codespaces/the-githubdev-web-based-editor.md

@@ -15,7 +15,7 @@ redirect_from:
 
 {% note %}
 
-**Note:** The {% data variables.codespaces.serverless %} editor is currently in beta preview. You can provide feedback [in our Discussions](https://github.com/community/community/discussions/categories/codespaces).
+**Note:** The {% data variables.codespaces.serverless %} editor is currently in {% data variables.release-phases.public_preview %}. You can provide feedback [in our Discussions](https://github.com/community/community/discussions/categories/codespaces).
 
 {% endnote %}
 

content/communities/using-templates-to-encourage-useful-issues-and-pull-requests/syntax-for-githubs-form-schema.md

@@ -11,7 +11,7 @@ topics:
 
 {% note %}
 
-**Note:** {% data variables.product.company_short %}'s form schema is currently in beta and subject to change.
+**Note:** {% data variables.product.company_short %}'s form schema is currently in {% data variables.release-phases.public_preview %} and subject to change.
 
 {% endnote %}
 

content/contributing/collaborating-on-github-docs/using-the-content-linter.md

@@ -139,7 +139,7 @@ Note, if you are placing the expired tags in an HTML `table` element, make sure
 macOS
 </td>
 <td>
-The <code>macos-11</code> label has been deprecated and will no longer be available after 28 June 2024.
+The <code>macos-11</code> label is {% data variables.release-phases.closing_down %} and will no longer be available after 28 June 2024.
 </td>
 </tr>
 <!-- end expires 2024-06-28 -->

content/contributing/style-guide-and-content-model/style-guide.md

@@ -52,12 +52,12 @@ Provides additional context that users may need to take into account. Tasks can
 
 Notes are particularly useful for communicating parenthetical information that is not central to the process being described:
 * Caveats that might affect the outcome of a process, such as specific user settings.
-* Products and features that are subject to changes in availability, such as those in beta or being deprecated.
+* Products and features that are subject to changes in availability, such as those in {% data variables.release-phases.public_preview %} or {% data variables.release-phases.closing_down %}.
 
-For example, "[AUTOTITLE](/code-security/secret-scanning/managing-alerts-from-secret-scanning/evaluating-alerts#reviewing-github-token-metadata)" uses a note to inform users that metadata for {% data variables.product.prodname_dotcom %} tokens is currently in beta.
+For example, "[AUTOTITLE](/code-security/secret-scanning/managing-alerts-from-secret-scanning/evaluating-alerts#reviewing-github-token-metadata)" uses a note to inform users that metadata for {% data variables.product.prodname_dotcom %} tokens is currently in {% data variables.release-phases.public_preview %}.
 
 > [!NOTE]
-> Metadata for {% data variables.product.prodname_dotcom %} tokens is currently in public beta and subject to change.
+> Metadata for {% data variables.product.prodname_dotcom %} tokens is currently in {% data variables.release-phases.public_preview %} and subject to change.
 
 #### Tip
 

content/contributing/writing-for-github-docs/creating-screenshots.md

@@ -172,7 +172,7 @@ When replacing an existing image, best practice is to retain the image's filenam
 
 If you must change an image filename, search the repository for other references to that image and update all references to the original filename.
 
-If the image is used in deprecated versions of {% data variables.product.prodname_ghe_server %} documentation, don't change the filename.
+If the image is used in documentation for versions of {% data variables.product.prodname_ghe_server %} that are {% data variables.release-phases.closing_down %}, don't change the filename.
 
 ## Versioning images in Markdown content
 
@@ -220,6 +220,6 @@ Your Liquid conditional would look like this:
 {% endif %}{% endraw %}
 ```
 
-When the 3.10 release is deprecated, the `/assets/images/enterprise/3.10` directory will be removed.
+When the 3.10 release is {% data variables.release-phases.closing_down %}, the `/assets/images/enterprise/3.10` directory will be removed.
 
 The numbered release directory should contain images that apply to that release number only or to that release number and earlier. For example, images in `/assets/images/enterprise/2.22` should contain images that apply to 2.22 only or 2.22 and earlier.

content/contributing/writing-for-github-docs/versioning-documentation.md

@@ -66,7 +66,7 @@ For {% data variables.product.prodname_ghe_cloud %}, use `enterprise-cloud@lates
 
 ### {% data variables.product.prodname_ghe_server %}
 
-Documentation for {% data variables.product.prodname_ghe_server %} has multiple versions and can be divided into two types: documentation for _supported releases_ (we support four at any one time), and documentation for _deprecated releases_ (we do not link to these on the Docs site but we support a "frozen" snapshot of these docs in perpetuity, so they can still be accessed if you know the URLs). See [`lib/enterprise-server-releases.js`](https://github.com/github/docs/blob/main/src/versions/lib/enterprise-server-releases.js) for a list.
+Documentation for {% data variables.product.prodname_ghe_server %} has multiple versions and can be divided into two types: documentation for _supported releases_ (we support four at any one time), and documentation for _{% data variables.release-phases.closing_down %} releases_ (we do not link to these on the Docs site but we support a "frozen" snapshot of these docs in perpetuity, so they can still be accessed if you know the URLs). See [`lib/enterprise-server-releases.js`](https://github.com/github/docs/blob/main/src/versions/lib/enterprise-server-releases.js) for a list.
 
 The versions are named `enterprise-server@<release>`. The short name is `ghes`. In Liquid conditionals, we can specify ranges, like `ghes > 3.0`. For more information, see "[Versioning with Liquid conditional operators](#versioning-with-liquid-conditional-operators)."
 

content/copilot/building-copilot-extensions/about-building-copilot-extensions.md

@@ -59,7 +59,7 @@ Before creating your own {% data variables.product.prodname_copilot_extension_sh
 * **Blackbeard**: A simple {% data variables.product.prodname_copilot_agent_short %} that responds to requests like a pirate, using {% data variables.product.prodname_copilot_short %}'s LLM API and special system prompts. It is a good starting point for learning how to build a {% data variables.product.prodname_copilot_extension_short %}. For more information, see the [Blackbeard {% data variables.product.prodname_copilot_extension_short %}](https://github.com/copilot-extensions/blackbeard-extension).
 * **{% data variables.product.prodname_github_models %}**: A more complex {% data variables.product.prodname_copilot_agent_short %} that lets you ask about and interact with various LLMs listed on the {% data variables.product.prodname_marketplace %} from within {% data variables.product.prodname_copilot_chat_short %}. For more information, see the [{% data variables.product.prodname_github_models %} {% data variables.product.prodname_copilot_extension_short %}](https://github.com/copilot-extensions/github-models-extension).
 
-    > [!NOTE] {% data variables.product.prodname_github_models %} are in public beta and subject to change. To request access, join the [waitlist](https://github.com/marketplace/models/waitlist).
+    > [!NOTE] {% data variables.product.prodname_github_models %} are in {% data variables.release-phases.public_preview %} and subject to change. To request access, join the [waitlist](https://github.com/marketplace/models/waitlist).
 * **Function calling**: an example agent written in Go that demonstrates function calling and confirmation dialogues. For more information, see the [Function calling extension](https://github.com/copilot-extensions/function-calling-extension).
 * **RAG extension**: an example agent written in Go that demonstrates a simple implementation of retrieval augmented generation. For more information, see the [RAG extension](https://github.com/copilot-extensions/rag-extension).
 * **Preview SDK**: An SDK that simplifies the process of building {% data variables.product.prodname_copilot_extensions_short %} by handling request verification, response formatting, and API interactions. It allows builders to focus on their extension's core functionality rather than boilerplate, by streamlining the integration of tools, APIs, and data sources into {% data variables.product.prodname_copilot_chat_short %}. For more information, see the [Preview SDK](https://github.com/copilot-extensions/preview-sdk.js).

content/copilot/building-copilot-extensions/copilot-extensions-glossary.md

@@ -59,7 +59,7 @@ A piece of code that retrieves context or executes an action in response to a us
 
 #### Tool/Function Calling
 
-A capability of {% data variables.product.prodname_copilot_short %}'s LLM (as well as Open AI’s) that allows them to invoke specific tools or functions. Extension builders can define available tools with parameters, enabling the LLM to select and call appropriate tools to fulfill a user’s request. “Functions” are a subset of “tools” and the “function calling” term will eventually be deprecated.
+A capability of {% data variables.product.prodname_copilot_short %}'s LLM (as well as Open AI’s) that allows them to invoke specific tools or functions. Extension builders can define available tools with parameters, enabling the LLM to select and call appropriate tools to fulfill a user’s request. “Functions” are a subset of “tools” and the “function calling” term will be {% data variables.release-phases.closing_down %}.
 
 #### Unlisted Extension
 

content/copilot/building-copilot-extensions/managing-the-availability-of-your-copilot-extension.md

@@ -40,7 +40,7 @@ If you make your app public, you can choose to publish it on the {% data variabl
 
 App managers cannot create, edit, or publish extensions on the {% data variables.product.prodname_marketplace %}. To manage a listing, you should be an organization owner for the publishing organization.
 
-> [!NOTE] Paid plans are not supported for {% data variables.product.prodname_copilot_extensions_short %} during public beta. Any requests to publish with a paid plan attached will not be approved.
+> [!NOTE] Paid plans are not supported for {% data variables.product.prodname_copilot_extensions_short %} during {% data variables.release-phases.public_preview %}. Any requests to publish with a paid plan attached will not be approved.
 
 {% data reusables.profile.access_org %}
 {% data reusables.organizations.org-list %}

content/copilot/managing-copilot/managing-copilot-for-your-enterprise/managing-policies-and-features-for-copilot-in-your-enterprise.md

@@ -69,7 +69,7 @@ You can chat with {% data variables.product.prodname_copilot %} in your IDE to g
 
 ### Give {% data variables.product.prodname_copilot_short %} access to Bing
 
-> [!NOTE] Bing search integration into {% data variables.product.prodname_copilot_chat_dotcom_short %}, {% data variables.product.prodname_vscode_shortname %}, and {% data variables.product.prodname_vs %} is currently in beta and is subject to change.
+> [!NOTE] Bing search integration into {% data variables.product.prodname_copilot_chat_dotcom_short %}, {% data variables.product.prodname_vscode_shortname %}, and {% data variables.product.prodname_vs %} is currently in {% data variables.release-phases.public_preview %} and is subject to change.
 
 {% data variables.product.prodname_copilot_chat %} can use Bing to provide enhanced responses by searching the internet for information related to a question. Bing search is particularly helpful when discussing new technologies or highly specific subjects.
 

content/copilot/managing-copilot/managing-github-copilot-in-your-organization/customizing-copilot-for-your-organization/creating-a-custom-model-for-github-copilot.md

@@ -2,7 +2,7 @@
 title: Creating a custom model for GitHub Copilot
 shortTitle: Create a custom model
 intro: "You can fine-tune {% data variables.product.prodname_copilot_short %} code completion by creating a custom model based on code in your organization's repositories."
-permissions: "Owners of organizations enrolled in the limited public beta."
+permissions: "Owners of organizations enrolled in the {% data variables.release-phases.public_preview %}."
 product: "The organization must belong to an enterprise with a {% data variables.product.prodname_copilot_enterprise_short %} subscription."
 versions:
   feature: copilot-custom-models
@@ -12,7 +12,7 @@ redirect_from:
   - /copilot/managing-copilot/managing-github-copilot-in-your-organization/enhancing-copilot-for-your-organization/creating-a-custom-model-for-github-copilot
 ---
 
-> [!NOTE] Custom models for {% data variables.product.prodname_copilot_enterprise %} is in limited public beta and is subject to change. During the limited public beta, there is no additional cost to {% data variables.product.prodname_copilot_enterprise_short %} customers enrolled on the beta for creating or using a custom model.
+> [!NOTE] Custom models for {% data variables.product.prodname_copilot_enterprise %} is in {% data variables.release-phases.public_preview %} and is subject to change. During the {% data variables.release-phases.public_preview %}, there is no additional cost to {% data variables.product.prodname_copilot_enterprise_short %} customers enrolled on the {% data variables.release-phases.public_preview %} for creating or using a custom model.
 
 ## Prerequisite
 
@@ -20,7 +20,7 @@ The code on which you want to train a custom model must be hosted in repositorie
 
 ## Limitations
 
-* For the limited public beta, an enterprise can deploy one custom model in a single organization.
+* For the {% data variables.release-phases.public_preview %}, an enterprise can deploy one custom model in a single organization.
 * Code completion suggestions based on the custom model are only available to managed users who get a {% data variables.product.prodname_copilot_enterprise_short %} subscription from the organization in which the custom model is deployed. For more information, see "[AUTOTITLE](/enterprise-cloud@latest/admin/managing-iam/understanding-iam-for-enterprises/about-enterprise-managed-users)."
 * The custom model is not used for code suggested in responses by {% data variables.product.prodname_copilot_chat %}.
 
@@ -42,7 +42,7 @@ This provides:
 
 ### About model creation
 
-Currently, in the limited public beta, only one organization in an enterprise is permitted to create a custom model.
+Currently, in the {% data variables.release-phases.public_preview %}, only one organization in an enterprise is permitted to create a custom model.
 
 As an owner of the organization that's permitted to create a custom model, you can choose which of your organization's repositories to use to train the model. You can train the model on one, several, or all of the repositories in the organization. The model is trained on the content of the default branches of the selected repositories. Optionally, you can specify that only code written in certain programming languages should be used for training. The custom model will be used for generating code completion suggestions in all file types, irrespective of whether that type of file was used for training.
 

content/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.md

@@ -42,7 +42,7 @@ You can use {% data variables.product.prodname_dotcom %}'s REST API to get detai
 
 ## Understanding the `last_activity_at` calculation
 
-> [!NOTE] This data is in public beta and subject to change.
+> [!NOTE] This data is in {% data variables.release-phases.public_preview %} and subject to change.
 
 To align the `last_activity_at` data point with _actual usage_, the system returns the timestamp of a user's most recent interaction with Copilot functionality. These interactions are:
 

content/copilot/using-github-copilot/asking-github-copilot-questions-in-githubcom.md

@@ -63,7 +63,7 @@ The skills you can use in {% data variables.product.prodname_copilot_chat_dotcom
 
 | Skill                                                          | Description                                                                                                                                                                                                                                                                                                                                                                                                                                                                 | Enabled by default?                                                                                                                                                            | Example question                                                                                                                                      |
 |----------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------|
-| **Bing web search** (in beta and subject to change)            | Searches the web using the Bing search engine. This skill is useful for teaching {% data variables.product.prodname_copilot_short %} about recent events, new developments, trends, technologies, or extremely specific, detailed, or niche subjects. **Available for {% data variables.product.prodname_copilot_business_short %} and {% data variables.product.prodname_copilot_enterprise_short %}**.                                                                    | No (requires admin approval - see "[AUTOTITLE](/copilot/managing-copilot/managing-copilot-for-your-enterprise/managing-policies-and-features-for-copilot-in-your-enterprise)") | _What are some recent articles about SAT tokens securing against vulnerabilities in Node?_                                                            |
+| **Bing web search** (in {% data variables.release-phases.public_preview %} and subject to change)            | Searches the web using the Bing search engine. This skill is useful for teaching {% data variables.product.prodname_copilot_short %} about recent events, new developments, trends, technologies, or extremely specific, detailed, or niche subjects. **Available for {% data variables.product.prodname_copilot_business_short %} and {% data variables.product.prodname_copilot_enterprise_short %}**.                                                                    | No (requires admin approval - see "[AUTOTITLE](/copilot/managing-copilot/managing-copilot-for-your-enterprise/managing-policies-and-features-for-copilot-in-your-enterprise)") | _What are some recent articles about SAT tokens securing against vulnerabilities in Node?_                                                            |
 | **Code search**                                                | Natural language code search in the default branch of the Git repository. This skill is useful when you want to know where or how certain functionality has been implemented in the code. Note: this requires indexing to be enabled for the repository (see "[AUTOTITLE](/enterprise-cloud@latest/copilot/managing-copilot/managing-github-copilot-in-your-organization/managing-github-copilot-features-in-your-organization/indexing-repositories-for-copilot-chat)").   | Yes                                                                                                                                                                            | _Where is the logic that controls the user session management, and how does it work?_                                                                 |
 | **Commit details**                                             | Retrieves a list of commits, or the contents of a specific commit, to provide answers to commit-related questions.                                                                                                                                                                                                                                                                                                                                                          | Yes                                                                                                                                                                            | _Explain the changes in the code of this commit_                                                                                                      |
 | **Discussion details**                                         | Retrieves a specific {% data variables.product.prodname_dotcom %} discussion. This is useful for quickly getting the gist of the conversation in a discussion.                                                                                                                                                                                                                                                                                                              | Yes                                                                                                                                                                            | _Summarize this discussion_                                                                                                                           |
@@ -104,7 +104,7 @@ You can ask a general question about software development that is not focused on
 
 Depending on the question you ask, and your enterprise and organization settings, {% data variables.product.prodname_copilot_short %} may respond using information based on the results of a Bing search. By using Bing search, {% data variables.product.prodname_copilot_short %} can answer a broad range of tech-related questions with up-to-date details based on information currently available on the internet. For information on how to enable or disable Bing search integration, see "[AUTOTITLE](/copilot/managing-copilot/managing-copilot-for-your-enterprise/managing-policies-and-features-for-copilot-in-your-enterprise)."
 
-> [!NOTE] Bing search integration into {% data variables.product.prodname_copilot_chat_dotcom_short %} is currently in beta and is subject to change.
+> [!NOTE] Bing search integration into {% data variables.product.prodname_copilot_chat_dotcom_short %} is currently in {% data variables.release-phases.public_preview %} and is subject to change.
 
 {% data reusables.copilot.go-to-copilot-page %}
 
@@ -379,7 +379,7 @@ You can ask {% data variables.product.prodname_copilot_short %} to summarize a p
 
 ### Ask why a workflow has failed
 
-> [!NOTE]This feature is currently in beta and subject to change.
+> [!NOTE]This feature is currently in {% data variables.release-phases.public_preview %} and subject to change.
 
 1. On {% data variables.product.prodname_dotcom_the_website %}, navigate to a pull request in a repository.
 1. Scroll to the bottom of the page, then, next to one of the failing checks, click **Details**.

content/copilot/using-github-copilot/asking-github-copilot-questions-in-your-ide.md

@@ -110,7 +110,7 @@ To see all available chat variables, type `#` in the chat prompt box. See also [
 
 > [!NOTE]
 > * This feature is only available if you have a {% data variables.product.prodname_copilot_enterprise_short %} subscription.
-> * The `@github` chat participant is currently in beta and is subject to change.
+> * The `@github` chat participant is currently in {% data variables.release-phases.public_preview %} and is subject to change.
 
 {% data variables.product.prodname_copilot_short %} has a collection of {% data variables.product.prodname_dotcom %}-specific skills that it can use to answer your questions. To access these skills in {% data variables.product.prodname_copilot_chat_short %} in {% data variables.product.prodname_vscode_shortname %}, include `@github` in your question.
 

content/copilot/using-github-copilot/finding-public-code-that-matches-github-copilot-suggestions.md

@@ -10,7 +10,7 @@ versions:
   feature: copilot
 ---
 
-> [!NOTE] {% data variables.product.prodname_copilot %} code referencing is in public beta and is subject to change.
+> [!NOTE] {% data variables.product.prodname_copilot %} code referencing is in {% data variables.release-phases.public_preview %} and is subject to change.
 
 ## About code referencing in {% data variables.product.prodname_copilot %}
 

content/copilot/using-github-copilot/using-copilot-text-completion.md

@@ -10,7 +10,7 @@ topics:
 ---
 
 >[!NOTE]
-> {% data variables.product.prodname_copilot_autocomplete_pr %} is currently in beta and subject to change. To participate in the beta, an administrator of your enterprise must opt in to the use of previews of {% data variables.product.prodname_copilot_short %} features.
+> {% data variables.product.prodname_copilot_autocomplete_pr %} is currently in {% data variables.release-phases.public_preview %} and subject to change. To participate in the {% data variables.release-phases.public_preview %}, an administrator of your enterprise must opt in to the use of previews of {% data variables.product.prodname_copilot_short %} features.
 
 ## About {% data variables.product.prodname_copilot_autocomplete_pr %}
 

content/education/manage-coursework-with-github-classroom/integrate-github-classroom-with-an-ide/using-github-codespaces-with-github-classroom.md

@@ -45,7 +45,7 @@ After you have confirmation that you are a verified teacher, visit [{% data vari
 
 If you are eligible for the {% data variables.product.prodname_codespaces %} Education benefit, when you enable {% data variables.product.prodname_github_codespaces %} in {% data variables.product.prodname_classroom %} for your organization, GitHub automatically adds a Codespace policy to restrict machine types for all codespaces in the organization to 2 core machines. This helps you make the most of the free {% data variables.product.prodname_github_codespaces %} usage. However, you can change or remove these policies in your organization settings. For more information, see "[AUTOTITLE](/codespaces/managing-codespaces-for-your-organization/restricting-access-to-machine-types)."
 
-When the {% data variables.product.prodname_codespaces %} Education benefit moves out of beta, if your organization exceeds their free allowance for {% data variables.product.prodname_github_codespaces %} usage, your organization will be billed for additional usage. For more information, see "[AUTOTITLE](/billing/managing-billing-for-github-codespaces/about-billing-for-github-codespaces)."
+When the {% data variables.product.prodname_codespaces %} Education benefit moves out of {% data variables.release-phases.public_preview %}, if your organization exceeds their free allowance for {% data variables.product.prodname_github_codespaces %} usage, your organization will be billed for additional usage. For more information, see "[AUTOTITLE](/billing/managing-billing-for-github-codespaces/about-billing-for-github-codespaces)."
 
 ## Enabling {% data variables.product.prodname_codespaces %} for your organization
 

content/get-started/accessibility/managing-your-theme-settings.md

@@ -35,7 +35,7 @@ If you have low vision, you may benefit from a high contrast theme, with greater
     * If you chose a single theme, click a theme.
 
     * If you chose to follow your system settings, click a day theme and a night theme.{% ifversion fpt or ghec %}
-    * If you would like to choose a theme which is currently in public beta, you will first need to enable it with feature preview. For more information, see "[AUTOTITLE](/get-started/using-github/exploring-early-access-releases-with-feature-preview)."{% endif %}
+    * If you would like to choose a theme which is currently in {% data variables.release-phases.public_preview %}, you will first need to enable it with feature preview. For more information, see "[AUTOTITLE](/get-started/using-github/exploring-early-access-releases-with-feature-preview)."{% endif %}
 
 {% ifversion command-palette %}
 

content/get-started/exploring-projects-on-github/saving-repositories-with-stars.md

@@ -51,7 +51,7 @@ To view everyone who has starred a repository, add `/stargazers` to the end of t
 
 {% note %}
 
-**Note:** Lists are currently in public beta and subject to change.
+**Note:** Lists are currently in {% data variables.release-phases.public_preview %} and subject to change.
 
 {% endnote %}
 

content/get-started/using-github/exploring-early-access-releases-with-feature-preview.md

@@ -1,6 +1,6 @@
 ---
 title: Exploring early access releases with feature preview
-intro: You can use feature preview to see products or features that are available in beta and to enable or disable each feature for your personal account.
+intro: You can use feature preview to see products or features that are available in {% data variables.release-phases.public_preview %} and to enable or disable each feature for your personal account.
 redirect_from:
   - /articles/exploring-early-access-releases-with-feature-preview
   - /github/getting-started-with-github/exploring-early-access-releases-with-feature-preview
@@ -18,13 +18,13 @@ shortTitle: Feature preview
 
 | Phase | Description |
 |-------|-------------|
-| Alpha | The product or feature is under heavy development and often has changing requirements and scope. The feature is available for demonstration and test purposes but may not be documented. Alpha releases are not necessarily feature complete, no service level agreements (SLAs) are provided, and there are no technical support obligations. <br><br> **Note**: A product or feature released as a "Technology Preview" is considered to be in the alpha release stage. Technology Preview releases share the same characteristics of alpha releases as described above.|
+| {% data variables.release-phases.private_preview_caps %} | The product or feature is under heavy development and often has changing requirements and scope. The feature is available for demonstration and test purposes but may not be documented. {% data variables.release-phases.private_preview_caps %} releases are not necessarily feature complete, no service level agreements (SLAs) are provided, and there are no technical support obligations. <br><br> **Note**: A product or feature released as a "Technology Preview" is considered to be in the {% data variables.release-phases.private_preview %} release stage. Technology Preview releases share the same characteristics of {% data variables.release-phases.private_preview %} releases as described above.|
-| Beta | The product or feature is ready for broader distribution. Beta releases can be public or private, are documented, but do not have any SLAs or technical support obligations. |
+| {% data variables.release-phases.public_preview_caps %} | The product or feature is ready for broader distribution. {% data variables.release-phases.public_preview_caps %} releases can be public or private, are documented, but do not have any SLAs or technical support obligations. |
 | General availability (GA) | The product or feature is fully tested and open publicly to all users. GA releases are ready for production use, and associated SLA and technical support obligations apply. |
 
-## Exploring beta releases with feature preview
+## Exploring {% data variables.release-phases.public_preview %} releases with feature preview
 
-You can see a list of features that are available in beta and a brief description for each feature. Each feature includes a link to give feedback.
+You can see a list of features that are available in {% data variables.release-phases.public_preview %} and a brief description for each feature. Each feature includes a link to give feedback.
 
 {% data reusables.feature-preview.feature-preview-setting  %}
 1. To view details for a feature, in the left sidebar, click the feature's name.

content/get-started/using-github/github-mobile.md

@@ -56,7 +56,7 @@ You must install {% data variables.product.prodname_mobile %} 1.4 or later on yo
 
 To use {% data variables.product.prodname_mobile %} with {% data variables.product.prodname_ghe_server %}, {% data variables.product.prodname_dotcom %} must be version 3.0 or greater, and your enterprise owner must enable mobile support for your enterprise. For more information, see {% ifversion ghes %}"[AUTOTITLE](/admin/release-notes)" and {% endif %}"[Managing {% data variables.product.prodname_mobile %} for your enterprise]({% ifversion not ghes %}/enterprise-server@latest{% endif %}/admin/configuration/configuring-your-enterprise/managing-github-mobile-for-your-enterprise){% ifversion not ghes %}" in the {% data variables.product.prodname_ghe_server %} documentation.{% else %}."{% endif %}
 
-During the beta for {% data variables.product.prodname_mobile %} with {% data variables.product.prodname_ghe_server %}, you must be signed in with a personal account on {% data variables.product.prodname_dotcom_the_website %}.
+During the {% data variables.release-phases.public_preview %} for {% data variables.product.prodname_mobile %} with {% data variables.product.prodname_ghe_server %}, you must be signed in with a personal account on {% data variables.product.prodname_dotcom_the_website %}.
 
 ### Adding, switching, or signing out of accounts
 
@@ -94,9 +94,9 @@ To re-enable Universal Links, long-press any {% data variables.product.product_n
 
 You can submit feature requests or other feedback for {% data variables.product.prodname_mobile %} on [{% data variables.product.prodname_github_community %}](https://github.com/orgs/community/discussions/categories/mobile).
 
-## Opting out of beta releases for iOS
+## Opting out of {% data variables.release-phases.public_preview %} releases for iOS
 
-If you're testing a beta release of {% data variables.product.prodname_mobile %} for iOS using TestFlight, you can leave the beta at any time.
+If you're testing a {% data variables.release-phases.public_preview %} release of {% data variables.product.prodname_mobile %} for iOS using TestFlight, you can leave the {% data variables.release-phases.public_preview %} at any time.
 
 1. On your iOS device, open the TestFlight app.
 1. Under "Apps", tap **{% data variables.product.prodname_dotcom %}**.

content/get-started/using-github/supported-browsers.md

@@ -36,6 +36,6 @@ Some browser vendors provide extended support releases. We do our best to ensure
 
 In earlier extended support releases, {% data variables.product.product_name %} may not work as you expect, and some features may not be available.
 
-## Beta and developer builds
+## {% data variables.release-phases.public_preview_caps %} and developer builds
 
-You may encounter unexpected bugs in beta and developer builds of our supported browsers. If you encounter a bug on {% data variables.product.product_name %} in one of these unreleased builds, please verify that it also exists in the stable version of the same browser. If the bug only exists in the unstable version, consider reporting the bug to the browser developer.
+You may encounter unexpected bugs in {% data variables.release-phases.public_preview %} and developer builds of our supported browsers. If you encounter a bug on {% data variables.product.product_name %} in one of these unreleased builds, please verify that it also exists in the stable version of the same browser. If the bug only exists in the unstable version, consider reporting the bug to the browser developer.

content/get-started/writing-on-github/getting-started-with-writing-and-formatting-on-github/basic-writing-and-formatting-syntax.md

@@ -137,7 +137,7 @@ For more detailed information on the requirements of URI fragments, see [RFC 398
 The code block below demonstrates the basic rules used to generate anchors from headings in rendered content.
 
 ```markdown
-# Example headings 
+# Example headings
 
 ## Sample Section
 
@@ -233,7 +233,7 @@ For example, the following code displays a sun image for light themes and a moon
 
 {% data reusables.getting-started.picture-element-example %}
 
-The old method of specifying images based on the theme, by using a fragment appended to the URL (`#gh-dark-mode-only` or `#gh-light-mode-only`), is deprecated and will be removed in favor of the new method described above.
+The old method of specifying images based on the theme, by using a fragment appended to the URL (`#gh-dark-mode-only` or `#gh-light-mode-only`), is {% data variables.release-phases.closing_down %} and will be removed in favor of the new method described above.
 
 ## Lists
 

content/github-models/prototyping-with-ai-models.md

@@ -15,13 +15,13 @@ To find AI models, go to [{% data variables.product.prodname_marketplace %}](htt
 
 To view details about a model, click on the model's name.
 
-> [!NOTE] Access to OpenAI's `o1` models is in public beta and subject to change. To request access, join the [waitlist](https://github.com/o1-waitlist-signup).
+> [!NOTE] Access to OpenAI's `o1` models is in {% data variables.release-phases.public_preview %} and subject to change. To request access, join the [waitlist](https://github.com/o1-waitlist-signup).
 
 ## Experimenting with AI models in the playground
 
 >[!NOTE]
 >
-> The playground is in limited public beta and subject to change. To request access, [join the waitlist](https://github.com/marketplace/models/waitlist).
+> The playground is in {% data variables.release-phases.public_preview %} and subject to change. To request access, [join the waitlist](https://github.com/marketplace/models/waitlist).
 
 {% data variables.product.prodname_marketplace %} provides a free playground where you can adjust model parameters and submit prompts to see how the model responds.
 
@@ -35,7 +35,7 @@ The playground is rate limited. See [Rate limits](#rate-limits) below.
 
 >[!NOTE]
 >
-> The free API usage is in limited public beta and subject to change. To request access, [join the waitlist](https://github.com/marketplace/models/waitlist).
+> The free API usage is in {% data variables.release-phases.public_preview %} and subject to change. To request access, [join the waitlist](https://github.com/marketplace/models/waitlist).
 
 {% data variables.product.company_short %} provides free API usage so that you can experiment with AI models in your own application.
 

content/graphql/guides/migrating-graphql-global-node-ids.md

@@ -11,11 +11,11 @@ shortTitle: Migrating global node IDs
 
 ## Background
 
-The {% data variables.product.product_name %} GraphQL API currently supports two types of global node ID formats. The legacy format will be deprecated and replaced with a new format.  This guide shows you how to migrate to the new format, if necessary.
+The {% data variables.product.product_name %} GraphQL API currently supports two types of global node ID formats. The legacy format will be {% data variables.release-phases.closing_down %} and replaced with a new format.  This guide shows you how to migrate to the new format, if necessary.
 
-By migrating to the new format, you ensure that the response times of your requests remain consistent and small. You also ensure that your application continues to work once the legacy IDs are fully deprecated.
+By migrating to the new format, you ensure that the response times of your requests remain consistent and small. You also ensure that your application continues to work once the legacy IDs are {% data variables.release-phases.closing_down %}.
 
-To learn more about why the legacy global node ID format will be deprecated, see "[New global ID format coming to GraphQL](https://github.blog/2021-02-10-new-global-id-format-coming-to-graphql)."
+To learn more about why the legacy global node ID format will be {% data variables.release-phases.closing_down %}, see "[New global ID format coming to GraphQL](https://github.blog/2021-02-10-new-global-id-format-coming-to-graphql)."
 
 ## Determining if you need to take action
 

content/graphql/guides/using-the-explorer.md

@@ -37,7 +37,7 @@ You can use query autocompletion to help you build queries. In the main pane, wi
 
 ## Accessing the sidebar docs
 
-All types in a GraphQL schema include a `description` field compiled into documentation. The collapsible **Docs** pane on the right side of the Explorer page allows you to browse documentation about the type system. The docs are automatically updated and will drop deprecated fields.
+All types in a GraphQL schema include a `description` field compiled into documentation. The collapsible **Docs** pane on the right side of the Explorer page allows you to browse documentation about the type system. The docs are automatically updated and will drop fields that are {% data variables.release-phases.closing_down %}.
 
 {% note %}
 

content/issues/planning-and-tracking-with-projects/customizing-views-in-your-project/filtering-projects.md

@@ -192,8 +192,8 @@ You can filter by specific text fields or use a general text filter across all t
 
 | Qualifier  | Example
 | ---------- | -------------
-| <code>field:"<em>TEXT</em>"    | **title:"API deprecation"** will show items with titles that exactly match "API deprecation."
+| <code>field:"<em>TEXT</em>"    | **title:"Bug fix"** will show items with titles that exactly match "Bug fix".
-| <code>field:<em>TEXT</em>      | **note:complete** will show items with a note text field that exactly match "complete."
+| <code>field:<em>TEXT</em>      | **note:complete** will show items with a note text field that exactly match "complete".
 | <code><em>TEXT</em></code>     | **API** will show items with "API" in the title or any other text field.
 | <code>field:<em>TEXT</em> TEXT | **label:bug rendering** will show items with the "bug" label and with "rendering" in the title or any other text field.
 

content/issues/planning-and-tracking-with-projects/managing-items-in-your-project/adding-items-to-your-project.md

@@ -24,7 +24,7 @@ You have several options for adding issues and pull requests to your project. Yo
 
 {% note %}
 
-**Note:** Timeline events for Projects is currently in beta and subject to change.
+**Note:** Timeline events for Projects is currently in {% data variables.release-phases.public_preview %} and subject to change.
 
 {% endnote %}
 

content/issues/tracking-your-work-with-issues/using-issues/about-slash-commands.md

@@ -10,7 +10,7 @@ redirect_from:
 
 {% note %}
 
-**Note:** Slash commands are currently in public beta and subject to change.
+**Note:** Slash commands are currently in {% data variables.release-phases.public_preview %} and subject to change.
 
 {% endnote %}
 

content/issues/tracking-your-work-with-issues/using-issues/creating-a-branch-for-an-issue.md

@@ -15,7 +15,7 @@ redirect_from:
 
 {% note %}
 
-**Note:** The ability to create a branch for an issue is currently in public beta and subject to change.
+**Note:** The ability to create a branch for an issue is currently in {% data variables.release-phases.public_preview %} and subject to change.
 
 {% endnote %}
 

content/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/displaying-ip-addresses-in-the-audit-log-for-your-organization.md

@@ -15,7 +15,7 @@ topics:
 
 {% note %}
 
-**Note:** Displaying IP addresses in the audit log for an organization is in public beta and subject to change.
+**Note:** Displaying IP addresses in the audit log for an organization is in {% data variables.release-phases.public_preview %} and subject to change.
 
 {% endnote %}
 

content/organizations/managing-peoples-access-to-your-organization-with-roles/about-custom-organization-roles.md

@@ -20,7 +20,7 @@ You can also create a custom organization role that includes permissions for rep
 
 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.
 
->[!NOTE] Adding repository permissions to a custom organization role is currently in public beta and subject to change.
+>[!NOTE] Adding repository permissions to a custom organization role is currently in {% data variables.release-phases.public_preview %} and subject to change.
 
 {% endif %}
 

content/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/reviewing-dependency-changes-in-a-pull-request.md

@@ -19,7 +19,7 @@ redirect_from:
   - /github/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/reviewing-dependency-changes-in-a-pull-request
 shortTitle: Review dependency changes
 ---
-<!--Marketing-LINK: From /features/security/software-supply-chain page "Sign up for the dependency review beta" and "Reviewing dependency changes in a pull request".-->
+<!--Marketing-LINK: From /features/security/software-supply-chain page "Sign up for the dependency review {% data variables.release-phases.public_preview %}" and "Reviewing dependency changes in a pull request".-->
 
 ## About dependency review
 

content/repositories/configuring-branches-and-merges-in-your-repository/managing-branches-in-your-repository/renaming-a-branch.md

@@ -22,7 +22,7 @@ If a repository's default branch is renamed, {% data variables.product.prodname_
 
 Although file URLs are automatically redirected, raw file URLs are not redirected. Also, {% data variables.product.prodname_dotcom %} does not perform any redirects if users perform a `git pull` for the previous branch name.
 
-{% data variables.product.prodname_actions %} workflows do not follow renames, so if your repository publishes an action, anyone using that action with `@{old-branch-name}` will break. You should consider adding a new branch with the original content plus an additional commit reporting that the branch name is deprecated and suggesting that users migrate to the new branch name.
+{% data variables.product.prodname_actions %} workflows do not follow renames, so if your repository publishes an action, anyone using that action with `@{old-branch-name}` will break. You should consider adding a new branch with the original content plus an additional commit reporting that the branch name is {% data variables.release-phases.closing_down %} and suggesting that users migrate to the new branch name.
 
 Organizational rulesets that apply to branches of a repository will no longer allow the repository administrator to rename branches of the targeted repository or change the default branch to another branch. Repository administrators may create and delete branches so long as they have the appropriate permissions.
 

content/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/configuring-tag-protection-rules.md

@@ -6,7 +6,7 @@ versions:
   ghes: '<3.16'
 ---
 
->[!NOTE] Tag protection rules will be deprecated on August 30, 2024, and in {% data variables.product.prodname_ghe_server %} version 3.16 and later, in favor of rulesets. Any tag protection rules still in use after the deprecation date will be auto-migrated, but you can also migrate them manually before the deprecation date. You can read more about this deprecation on the [{% data variables.product.prodname_blog %}](https://github.blog/changelog/2024-05-29-sunset-notice-tag-protections).
+>[!NOTE] Tag protection rules are {% data variables.release-phases.closing_down %} in {% data variables.product.prodname_ghe_server %} version 3.16 and later. Use rulesets instead. Any tag protection rules still in use will be auto-migrated. You can read more about this on the [{% data variables.product.prodname_blog %}](https://github.blog/changelog/2024-05-29-sunset-notice-tag-protections).
 
 When you add a tag protection rule, all tags that match the pattern provided will be protected. Only users with admin or maintain permissions, or custom roles with the "edit repository rules" permission in the repository will be able to create protected tags, and only users with admin permissions or custom roles with the "edit repository rules" permission in the repository will be able to delete protected tags. For more information, see "[AUTOTITLE](/organizations/managing-user-access-to-your-organizations-repositories/managing-repository-roles/repository-roles-for-an-organization#permissions-for-each-role)." {% data variables.product.prodname_github_apps %} require the `Repository administration: write` permission to modify a protected tag.
 

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

@@ -13,7 +13,7 @@ shortTitle: Manage the push policy
 
 {% note %}
 
-**Note:** The push policy is currently in beta and subject to change.
+**Note:** The push policy is currently in {% data variables.release-phases.public_preview %} and subject to change.
 
 {% endnote %}
 

content/repositories/releasing-projects-on-github/managing-releases-in-a-repository.md

@@ -58,7 +58,7 @@ You can choose whether {% data variables.large_files.product_name_long %} ({% da
 1. Follow the interactive prompts. Alternatively, you can specify arguments to skip these prompts. For more information about possible arguments, see [the {% data variables.product.prodname_cli %} manual](https://cli.github.com/manual/gh_release_create). For example, this command creates a prerelease with the specified title and notes.
 
    ```shell
-   gh release create v1.3.2 --title "v1.3.2 (beta)" --notes "this is a beta release" --prerelease
+   gh release create v1.3.2 --title "v1.3.2 (beta)" --notes "this is a {% data variables.release-phases.public_preview %} release" --prerelease
    ```
 
 If you @mention any {% data variables.product.product_name %} users in the notes, the published release on {% data variables.product.prodname_dotcom_the_website %} will include a **Contributors** section with an avatar list of all the mentioned users.

content/repositories/viewing-activity-and-data-for-your-repository/viewing-deployment-activity-for-your-repository.md

@@ -15,7 +15,7 @@ shortTitle: View deployment activity
 ---
 {% note %}
 
-**Note:** The deployments dashboard is currently in beta and subject to change.
+**Note:** The deployments dashboard is currently in {% data variables.release-phases.public_preview %} and subject to change.
 
 {% endnote %}
 

content/rest/codespaces/organization-secrets.md

@@ -15,7 +15,7 @@ autogenerated: rest
 
 {% note %}
 
-**Note**: These endpoints are currently in public beta and subject to change.
+**Note**: These endpoints are currently in {% data variables.release-phases.public_preview %} and subject to change.
 
 {% endnote %}
 

content/rest/copilot/copilot-user-management.md

@@ -14,6 +14,6 @@ redirect_from:
   - /rest/copilot/copilot-business
 ---
 
-> [!NOTE] These endpoints are in public beta and subject to change.
+> [!NOTE] These endpoints are in {% data variables.release-phases.public_preview %} and subject to change.
 
 <!-- Content after this section is automatically generated -->

content/rest/dependabot/alerts.md

@@ -14,7 +14,7 @@ autogenerated: rest
 
 {% note %}
 
-**Note**: The ability to use the REST API to manage Dependabot alerts is currently in public beta and subject to change.
+**Note**: The ability to use the REST API to manage Dependabot alerts is currently in {% data variables.release-phases.public_preview %} and subject to change.
 
 {% endnote %}
 

content/rest/enterprise-admin/management-console.md

@@ -12,7 +12,7 @@ topics:
 autogenerated: rest
 ---
 
-## Deprecation of the Management Console endpoints
+## About the Management Console endpoints
 
 The full functionality of the Management Console endpoints was added to the [Manage GHES](/rest/enterprise-admin/manage-ghes) endpoints in {% data variables.product.prodname_ghe_server %} version 3.12. With feature parity achieved, the Management Console API endpoints {% ifversion ghes < 3.15 %}will be{% else %}were{% endif %} removed in version 3.15.
 

content/rest/migrations/source-imports.md

@@ -16,7 +16,7 @@ autogenerated: rest
 
 {% warning %}
 
-**Warning**: Due to very low levels of usage and available alternatives, the Source Imports API has been deprecated and is no longer  available as of April 12, 2024. For more details and alternatives, see the [changelog](https://gh.io/source-imports-api-deprecation).
+**Warning**: Due to very low levels of usage and available alternatives, the Source Imports API has been {% data variables.release-phases.retired %}. For more details and alternatives, see the [changelog](https://gh.io/source-imports-api-deprecation).
 
 {% endwarning %}
 

content/search-github/searching-on-github/searching-discussions.md

@@ -107,7 +107,7 @@ You can use the `involves` qualifier to find discussions that involve a certain
 | Qualifier | Example |
 | :- | :- |
 | <code>involves:<em>USERNAME</em></code> | **[involves:becca involves:octocat](https://github.com/search?q=involves%3Abecca+involves%3Aoctocat&type=Discussions)** matches discussions either @becca or @octocat are involved in.
-| `in:body` <code>involves:<em>USERNAME</em></code> | [**NOT beta in:body involves:becca**](https://github.com/search?q=NOT+beta+in%3Abody+involves%3Abecca&type=Discussions) matches discussions @becca is involved in that do not contain the word "beta" in the body.
+| `in:body` <code>involves:<em>USERNAME</em></code> | [**NOT {% data variables.release-phases.public_preview %} in:body involves:becca**](https://github.com/search?q=NOT+beta+in%3Abody+involves%3Abecca&type=Discussions) matches discussions @becca is involved in that do not contain the word "beta" in the body.
 
 ## Search by number of comments
 

content/webhooks/about-webhooks.md

@@ -61,7 +61,7 @@ For information on best practices to follow when using webhooks, see "[AUTOTITLE
 
 {% note %}
 
-**Note:** GitHub Services (sometimes referred to as Service Hooks) was deprecated in 2019, in favor of integrating with webhooks. For more information about migrating your integration from using GitHub Services to using webhooks, see the [blog post](https://developer.github.com/changes/2018-04-25-github-services-deprecation/).
+**Note:** GitHub Services (sometimes referred to as Service Hooks) is {% data variables.release-phases.retired %}, in favor of integrating with webhooks. For more information about migrating your integration from using GitHub Services to using webhooks, see the [blog post](https://developer.github.com/changes/2018-04-25-github-services-deprecation/).
 
 {% endnote %}