diff --git a/content/code-security/getting-started/quickstart-for-securing-your-repository.md b/content/code-security/getting-started/quickstart-for-securing-your-repository.md
index bbc88f242bb3..40c3f2c70ba1 100644
--- a/content/code-security/getting-started/quickstart-for-securing-your-repository.md
+++ b/content/code-security/getting-started/quickstart-for-securing-your-repository.md
@@ -150,7 +150,7 @@ As an alternative to default setup, you can use advanced setup, which generates
 If you are a repository maintainer, it's good practice to specify a security policy for your repository by creating a file named `SECURITY.md` in the repository. This file instructs users about how to best contact you and collaborate with you when they want to report security vulnerabilities in your repository. You can view the security policy of a repository from the repository’s **{% data variables.product.prodname_security_and_quality_tab %}** tab.
 
 1. From the main page of your repository, click **{% data variables.product.prodname_security_and_quality_tab %}**.
-1. In the left sidebar, under "Reporting", click **{% octicon "law" aria-hidden="true" aria-label="law" %} Policy**.
+1. In the left sidebar, under "Reporting", click **{% octicon "law" aria-hidden="true" aria-label="law" %} Security policy**.
 1. Click **Start setup**.
 1. Add information about supported versions of your project and how to report vulnerabilities.
 
diff --git a/data/reusables/gated-features/environments.md b/data/reusables/gated-features/environments.md
index d7dea57aed38..6162f2ead3ae 100644
--- a/data/reusables/gated-features/environments.md
+++ b/data/reusables/gated-features/environments.md
@@ -1 +1,2 @@
 Environments, environment secrets, and deployment protection rules are available in public repositories for all current {% data variables.product.prodname_dotcom %} plans. They are not available on legacy plans, such as Bronze, Silver, or Gold. For access to environments, environment secrets, and deployment branches in private or internal repositories, you must use {% data variables.product.prodname_pro %}, {% data variables.product.prodname_team %}, or {% data variables.product.prodname_enterprise %}. {% ifversion fpt %}If you are on a {% data variables.product.prodname_free_user %}, {% data variables.product.prodname_pro %}, or {% data variables.product.prodname_team %} plan, other deployment protection rules, such as a wait timer or required reviewers, are only available for public repositories.{% endif %}
+
diff --git a/src/languages/lib/correct-translation-content.ts b/src/languages/lib/correct-translation-content.ts
index 7730a196b5b4..04ff3d6f1c8e 100644
--- a/src/languages/lib/correct-translation-content.ts
+++ b/src/languages/lib/correct-translation-content.ts
@@ -64,7 +64,7 @@ export function correctTranslatedContentStrings(
   // unexpanded. Rejoin the marker with its content. This corruption
   // affects every translated language (~47k bullets and ~11k cells in
   // total), so it lives in the universal pre-fixes block.
-  content = content.replace(/^\* ?\n[ \t]+/gm, '* ')
+  content = content.replace(/^([ \t]*)\* ?\n[ \t]+/gm, '$1* ')
   content = content.replace(/^\|[ \t]*\n[ \t]+/gm, '| ')
 
   // --- Per-language fixes (es, ja, pt, zh, ru, fr, ko, de) ---