Fix typo in vulnerability policy instructions

src/content/policy-management/block-until-scan.mdx

@@ -41,7 +41,7 @@ To verify the functionality of Block Until Scan, follow these steps:
 
 Browse to your Workspace Settings and [create a new vulnerability policy](/policy-management/vulnerability-policy). Define your policy with:
 - A name.
-- A [package Search Query](/artifact-management/search-filter-sort-packages) to scope the filter to `format:python AND requests`. We're targeting only packages named `requets` from Python, following the example in the next step. Adjust the policy to affect only to your desired scope if you use a different package for this example.
+- A [package Search Query](/artifact-management/search-filter-sort-packages) to scope the filter to `format:python AND requests`. We're targeting only packages named `requests` from Python, following the example in the next step. Adjust the policy to affect only to your desired scope if you use a different package for this example.
 - A severity threshold set to `High`.
 - A Quarantine action enabled.
 
@@ -87,4 +87,4 @@ While this scanning happens before you can download packages, the advantages are
 - **Enforce Security Policies across all your organization**: It blocks any package downloads until security checks has been completed. Only approved software components are used in your workloads, guaranteeing compliance with organizational standards and practices.
 - **Reduced Risk**: checking packages before running them reduces your exposure to non-compliant software.
 
-In short, Block Until Scan is a crucial tool for securing and reducing risk in your software supply chain.
+In short, Block Until Scan is a crucial tool for securing and reducing risk in your software supply chain.