[pre-commit.ci] auto fixes from pre-commit.com hooks

for more information, see https://pre-commit.ci

Author: pre-commit-ci[bot]

news/2024-09-08-output-validation-changes.md

@@ -5,7 +5,7 @@ adding new packages to existing feedstocks (e.g., when a new output is added), w
 require that maintainers submit a PR to add the new output via our
 [admin-requests repository](https://github.com/conda-forge/admin-requests?tab=readme-ov-file#add-a-package-output-to-a-feedstock).
 New feedstocks created via `staged-recipes` will have their outputs added automatically. If you maintain a feedstock
-that regularly adds new outputs (e.g., `llvmdev` has `libllvm18`, `libllvm19`, etc.), you can use the `admin-requsts` repo 
+that regularly adds new outputs (e.g., `llvmdev` has `libllvm18`, `libllvm19`, etc.), you can use the `admin-requsts` repo
 to add a glob pattern that matches the pattern of your new outputs. We test these patterns aginst new outputs from the feedstock
 using the Python `fnmatch` module. Outputs from the feedstock that match a glob pattern will added automatically. Further
 details on package output validation can be found in our [documentation](https://conda-forge.org/docs/maintainer/infrastructure/#output-validation-and-feedstock-tokens).