diff --git a/content/pull-requests/collaborating-with-pull-requests/collaborating-on-repositories-with-code-quality-features/about-status-checks.md b/content/pull-requests/collaborating-with-pull-requests/collaborating-on-repositories-with-code-quality-features/about-status-checks.md
index 1ba4ce813259..a44aa5c4cc18 100644
--- a/content/pull-requests/collaborating-with-pull-requests/collaborating-on-repositories-with-code-quality-features/about-status-checks.md
+++ b/content/pull-requests/collaborating-with-pull-requests/collaborating-on-repositories-with-code-quality-features/about-status-checks.md
@@ -31,19 +31,25 @@ You can see the overall state of the last commit to a branch on your repository'
 There are two types of status checks on {% data variables.product.product_name %}:
 
 - Checks
-- Statuses
+- Commit statuses
 
-_Checks_ are different from _statuses_ in that they provide line annotations, more detailed messaging, and are only available for use with {% data variables.product.prodname_github_apps %}.
+_Checks_ are different from _commit statuses_ in that they provide line annotations, more detailed messaging, and are only available for use with {% data variables.product.prodname_github_apps %}.
 
-Organization owners and users with push access to a repository can create checks and statuses with {% data variables.product.product_name %}'s API. For more information, see "[AUTOTITLE](/rest/checks)" and "[AUTOTITLE](/rest/commits#commit-statuses)."
+{% note %}
+
+**Note:** {% data variables.product.prodname_actions %} generates checks, not commit statuses, when workflows are run.
+
+{% endnote %}
+
+Organization owners and users with push access to a repository can create checks and commit statuses with {% data variables.product.product_name %}'s API. For more information, see "[AUTOTITLE](/rest/checks)" and "[AUTOTITLE](/rest/commits/statuses)."
 
 ## Checks
 
-When _checks_ are set up in a repository, pull requests have a **Checks** tab where you can view detailed build output from status checks and rerun failed checks.
+When _checks_ are set up in a repository, pull requests have a **Checks** tab where you can view detailed build output from checks and rerun failed checks.
 
 {% note %}
 
-**Note:** The **Checks** tab only gets populated for pull requests if you set up _checks_, not _statuses_, for the repository.
+**Note:** The **Checks** tab only gets populated for pull requests if you set up _checks_, not _commit statuses_, for the repository.
 
 {% endnote %}
 
@@ -83,7 +89,7 @@ Alternatively, to skip or request _all_ checks for your commit, add one of the f
 
 {% ifversion status-check-retention %}
 
-### Retention of status checks
+### Retention of checks
 
 {% data reusables.pull_requests.retention-checks-data %}
 
diff --git a/src/content-render/stylesheets/alerts.scss b/src/content-render/stylesheets/alerts.scss
index 0260950e46cd..dd0626eff72a 100644
--- a/src/content-render/stylesheets/alerts.scss
+++ b/src/content-render/stylesheets/alerts.scss
@@ -10,7 +10,7 @@ $colors: "default", "muted", "subtle", "accent", "success", "attention",
   padding: var(--base-size-8, 0.5rem) var(--base-size-16, 1rem);
   border-left: 0.25em solid
     var(--borderColor-default, var(--color-border-default));
-  margin-bottom: 1rem;
+  margin: 1rem 0;
 
   p:last-child,
   ul:last-child,