diff --git a/content/code-security/supply-chain-security/understanding-your-software-supply-chain/enforcing-dependency-review-across-an-organization.md b/content/code-security/supply-chain-security/understanding-your-software-supply-chain/enforcing-dependency-review-across-an-organization.md
index e5e1a5f823f5..19394622802e 100644
--- a/content/code-security/supply-chain-security/understanding-your-software-supply-chain/enforcing-dependency-review-across-an-organization.md
+++ b/content/code-security/supply-chain-security/understanding-your-software-supply-chain/enforcing-dependency-review-across-an-organization.md
@@ -34,7 +34,7 @@ You need to add the {% data variables.dependency-review.action_name %} to one of
 {% data reusables.profile.org_settings %}
 {% data reusables.organizations.access-ruleset-settings %}
 1. Click the **New ruleset** dropdown menu, and select **New branch ruleset**.
-1. To help identify your ruleset and clarify its purpose, give the ruselet a name in **Ruleset Name**.
+1. To help identify your ruleset and clarify its purpose, give the ruleset a name in **Ruleset Name**.
 1. Set **Enforcement status** to **{% octicon "play" aria-hidden="true" %} Active**.
 1. Optionally, you can target specific repositories in your organization. For more information, see [Choosing which repositories to target in your organization](/organizations/managing-organization-settings/creating-rulesets-for-repositories-in-your-organization#choosing-which-repositories-to-target-in-your-organization).
 1. In the "Rules" section, select the "Require workflows to pass before merging" option.