fix: typo (#2084)

## Description

...

## Related Issue

Fixes #
<!-- or -->
Relates to #

## Type of change

- [ ] Bug fix (non-breaking change which fixes an issue)
- [ ] New feature (non-breaking change which adds functionality)
- [ ] Other (security config, docs update, etc)

## Checklist before merging

- [ ] Test, docs, adr added or updated as needed
- [ ] [Contributor Guide
Steps](https://github.com/defenseunicorns/zarf/blob/main/CONTRIBUTING.md#developer-workflow)
followed

Co-authored-by: Wayne Starr <[email protected]>

adr/0009-sbom-more-than-images.md

@@ -21,7 +21,7 @@ Potential considerations:
 2. Run Syft against files and dataInjections
     Pros:
         - We know these files are actually inside of the package and won't just be noise
-        - This is the most common two ways for people to include addtional artifacts in packages (we use files in our own init package)
+        - This is the most common two ways for people to include additional artifacts in packages (we use files in our own init package)
     Cons:
         - This is only a subset of what Zarf provides and someone could commit an artifact to a git repo for example
 

docs/3-create-a-zarf-package/9-github-action.md

@@ -7,7 +7,7 @@ The [setup-zarf](https://github.com/defenseunicorns/setup-zarf) Github action is
 ```yaml
 # .github/workflows/zarf-package-create.yml
 jobs:
-  create_pacakge:
+  create_package:
     runs-on: ubuntu-latest
 
     name: Create my cool Zarf Package