Update website/docs/core-concepts/vendor/vendor-manifest.mdx

Co-authored-by: Erik Osterman (CEO @ Cloud Posse) <[email protected]>

website/docs/core-concepts/vendor/vendor-manifest.mdx

@@ -579,9 +579,9 @@ This excludes both:
 Using `{...}` here prevents the need to write two separate exclusion rules.
 
 Key Takeaways
-	1.	Use `**/` for recursive matching to include everything inside a directory.
-	2.	Use `*` for single-segment matches, which won't include deeper subdirectories.
-	3.	Use `{...}` to match multiple extensions or directories within a single pattern.
-	4.	Exclusion rules must match nested paths explicitly when trying to exclude deep directories.
+1. Use `**/` for recursive matching to include everything inside a directory.
+2. Use `*` for single-segment matches, which won't include deeper subdirectories.
+3. Use `{...}` to match multiple extensions or directories within a single pattern.
+4. Exclusion rules must match nested paths explicitly when trying to exclude deep directories.
 
 By carefully combining `included_paths`, `excluded_paths`, and `{...}` expansion, you can precisely control which files are vendored while ensuring unwanted directories like stargazers are omitted.