diff --git a/content/account-and-profile/managing-subscriptions-and-notifications-on-github/setting-up-notifications/configuring-notifications.md b/content/account-and-profile/managing-subscriptions-and-notifications-on-github/setting-up-notifications/configuring-notifications.md
index eaf224523c9c..d922620508ba 100644
--- a/content/account-and-profile/managing-subscriptions-and-notifications-on-github/setting-up-notifications/configuring-notifications.md
+++ b/content/account-and-profile/managing-subscriptions-and-notifications-on-github/setting-up-notifications/configuring-notifications.md
@@ -129,7 +129,7 @@ Email notifications from {% data variables.location.product_location %} contain
| --- | --- |
| `From` address | This address will always be {% ifversion fpt or ghec %}'`notifications@github.com`'{% else %}'the no-reply email address configured by your site administrator'{% endif %}. |
| `To` field | This field connects directly to the thread. If you reply to the email, you'll add a new comment to the conversation. |
-| `Cc` address | {% data variables.product.product_name %} will `Cc` you if you're subscribed to a conversation. The second `Cc` email address matches the notification reason. The suffix for these notification reasons is {% data variables.notifications.cc_address %}. The possible notification reasons are:
- `assign`: You were assigned to an issue or pull request.
- `author`: You created an issue or pull request.
- `ci_activity`: A {% data variables.product.prodname_actions %} workflow run that you triggered was completed.
- `comment`: You commented on an issue or pull request.
- `manual`: There was an update to an issue or pull request you manually subscribed to.
- `mention`: You were mentioned on an issue or pull request.
- `push`: Someone committed to a pull request you're subscribed to.
- `review_requested`: You or a team you're a member of was requested to review a pull request.
- `security_alert`: {% data variables.product.prodname_dotcom %} detected a vulnerability in a repository you receive alerts for.
- `state_change`: An issue or pull request you're subscribed to was either closed or opened.
- `subscribed`: There was an update in a repository you're watching.
- `team_mention`: A team you belong to was mentioned on an issue or pull request.
- `your_activity`: You opened, commented on, or closed an issue or pull request.
|
+| `Cc` address | {% data variables.product.product_name %} will `Cc` you if you're subscribed to a conversation. The second `Cc` email address matches the notification reason. The suffix for these notification reasons is {% ifversion fpt or ghec %}`@noreply.github.com`{% else %}based on the no-reply email address configured by your site administrator{% endif %}. The possible notification reasons are: - `assign`: You were assigned to an issue or pull request.
- `author`: You created an issue or pull request.
- `ci_activity`: A {% data variables.product.prodname_actions %} workflow run that you triggered was completed.
- `comment`: You commented on an issue or pull request.
- `manual`: There was an update to an issue or pull request you manually subscribed to.
- `mention`: You were mentioned on an issue or pull request.
- `push`: Someone committed to a pull request you're subscribed to.
- `review_requested`: You or a team you're a member of was requested to review a pull request.
- `security_alert`: {% data variables.product.prodname_dotcom %} detected a vulnerability in a repository you receive alerts for.
- `state_change`: An issue or pull request you're subscribed to was either closed or opened.
- `subscribed`: There was an update in a repository you're watching.
- `team_mention`: A team you belong to was mentioned on an issue or pull request.
- `your_activity`: You opened, commented on, or closed an issue or pull request.
|
| `List-Id` field | This field identifies the name of the repository and its owner. The format of this address is always `OWNER/REPOSITORY `, e.g. `List-Id: grain-lang/grain `. |
| `X-GitHub-Severity` field | {% data reusables.repositories.security-alerts-x-github-severity %} The possible severity levels are:- `low`
- `moderate`
- `high`
- `critical`
For more information, see "[AUTOTITLE](/code-security/dependabot/dependabot-alerts/about-dependabot-alerts)." |
diff --git a/data/variables/notifications.yml b/data/variables/notifications.yml
deleted file mode 100644
index bc4b4d7f646a..000000000000
--- a/data/variables/notifications.yml
+++ /dev/null
@@ -1,5 +0,0 @@
-no_reply_address: >-
- {% ifversion fpt or ghec %}`noreply@github.com`{% else %}the no-reply email address configured by your site administrator{% endif %}
-
-cc_address: >-
- {% ifversion fpt or ghec %}`@noreply.github.com`{% else %}based on the no-reply email address configured by your site administrator{% endif %}