chore: Spelling (#15970)

* spelling: achievable Signed-off-by: Josh Soref <[email protected]> * spelling: achieved Signed-off-by: Josh Soref <[email protected]> * spelling: acknowledged Signed-off-by: Josh Soref <[email protected]> * spelling: acknowledgments Signed-off-by: Josh Soref <[email protected]> * spelling: actually Signed-off-by: Josh Soref <[email protected]> * spelling: adds Signed-off-by: Josh Soref <[email protected]> * spelling: adjustment Signed-off-by: Josh Soref <[email protected]> * spelling: aggregator Signed-off-by: Josh Soref <[email protected]> * spelling: allowed Signed-off-by: Josh Soref <[email protected]> * spelling: also Signed-off-by: Josh Soref <[email protected]> * spelling: ampersand Signed-off-by: Josh Soref <[email protected]> * spelling: amqp Signed-off-by: Josh Soref <[email protected]> * spelling: and Signed-off-by: Josh Soref <[email protected]> * spelling: are Signed-off-by: Josh Soref <[email protected]> * spelling: associated Signed-off-by: Josh Soref <[email protected]> * spelling: attaches Signed-off-by: Josh Soref <[email protected]> * spelling: awful Signed-off-by: Josh Soref <[email protected]> * spelling: backwards Signed-off-by: Josh Soref <[email protected]> * spelling: below Signed-off-by: Josh Soref <[email protected]> * spelling: calculation Signed-off-by: Josh Soref <[email protected]> * spelling: canonical Signed-off-by: Josh Soref <[email protected]> * spelling: capture Signed-off-by: Josh Soref <[email protected]> * spelling: case Signed-off-by: Josh Soref <[email protected]> * spelling: certificate Signed-off-by: Josh Soref <[email protected]> * spelling: checksum Signed-off-by: Josh Soref <[email protected]> * spelling: circuiting Signed-off-by: Josh Soref <[email protected]> * spelling: client Signed-off-by: Josh Soref <[email protected]> * spelling: clonable Signed-off-by: Josh Soref <[email protected]> * spelling: committing Signed-off-by: Josh Soref <[email protected]> * spelling: community Signed-off-by: Josh Soref <[email protected]> * spelling: completely Signed-off-by: Josh Soref <[email protected]> * spelling: component Signed-off-by: Josh Soref <[email protected]> * spelling: composable Signed-off-by: Josh Soref <[email protected]> * spelling: concatenate Signed-off-by: Josh Soref <[email protected]> * spelling: conclusion Signed-off-by: Josh Soref <[email protected]> * spelling: configurable Signed-off-by: Josh Soref <[email protected]> * spelling: configuration Signed-off-by: Josh Soref <[email protected]> * spelling: configured Signed-off-by: Josh Soref <[email protected]> * spelling: constrained Signed-off-by: Josh Soref <[email protected]> * spelling: construct Signed-off-by: Josh Soref <[email protected]> * spelling: consumer Signed-off-by: Josh Soref <[email protected]> * spelling: contrast Signed-off-by: Josh Soref <[email protected]> * spelling: conventional Signed-off-by: Josh Soref <[email protected]> * spelling: conversions Signed-off-by: Josh Soref <[email protected]> * spelling: copypasted Signed-off-by: Josh Soref <[email protected]> * spelling: correctly Signed-off-by: Josh Soref <[email protected]> * spelling: could Signed-off-by: Josh Soref <[email protected]> * spelling: covered Signed-off-by: Josh Soref <[email protected]> * spelling: cumbersome Signed-off-by: Josh Soref <[email protected]> * spelling: custom Signed-off-by: Josh Soref <[email protected]> * spelling: datadog Signed-off-by: Josh Soref <[email protected]> * spelling: definitely Signed-off-by: Josh Soref <[email protected]> * spelling: delays Signed-off-by: Josh Soref <[email protected]> * spelling: delimited Signed-off-by: Josh Soref <[email protected]> * spelling: derivable Signed-off-by: Josh Soref <[email protected]> * spelling: describing Signed-off-by: Josh Soref <[email protected]> * spelling: description Signed-off-by: Josh Soref <[email protected]> * spelling: deserialization Signed-off-by: Josh Soref <[email protected]> * spelling: deserialized Signed-off-by: Josh Soref <[email protected]> * spelling: dictated Signed-off-by: Josh Soref <[email protected]> * spelling: different Signed-off-by: Josh Soref <[email protected]> * spelling: differentiate Signed-off-by: Josh Soref <[email protected]> * spelling: disabling Signed-off-by: Josh Soref <[email protected]> * spelling: disassembler Signed-off-by: Josh Soref <[email protected]> * spelling: distinguishes Signed-off-by: Josh Soref <[email protected]> * spelling: dividing Signed-off-by: Josh Soref <[email protected]> * spelling: downstream Signed-off-by: Josh Soref <[email protected]> * spelling: elasticsearch Signed-off-by: Josh Soref <[email protected]> * spelling: emitted Signed-off-by: Josh Soref <[email protected]> * spelling: emitting Signed-off-by: Josh Soref <[email protected]> * spelling: encoding Signed-off-by: Josh Soref <[email protected]> * spelling: encountered Signed-off-by: Josh Soref <[email protected]> * spelling: enhancements Signed-off-by: Josh Soref <[email protected]> * spelling: entirely Signed-off-by: Josh Soref <[email protected]> * spelling: evaluate Signed-off-by: Josh Soref <[email protected]> * spelling: evaluated Signed-off-by: Josh Soref <[email protected]> * spelling: exhausted Signed-off-by: Josh Soref <[email protected]> * spelling: existing Signed-off-by: Josh Soref <[email protected]> * spelling: explicitly Signed-off-by: Josh Soref <[email protected]> * spelling: expressions Signed-off-by: Josh Soref <[email protected]> * spelling: extend Signed-off-by: Josh Soref <[email protected]> * spelling: fallibility Signed-off-by: Josh Soref <[email protected]> * spelling: fell Signed-off-by: Josh Soref <[email protected]> * spelling: fixed Signed-off-by: Josh Soref <[email protected]> * spelling: floating Signed-off-by: Josh Soref <[email protected]> * spelling: framestream Signed-off-by: Josh Soref <[email protected]> * spelling: functionally Signed-off-by: Josh Soref <[email protected]> * spelling: generate Signed-off-by: Josh Soref <[email protected]> * spelling: generation Signed-off-by: Josh Soref <[email protected]> * spelling: github Signed-off-by: Josh Soref <[email protected]> * spelling: globally Signed-off-by: Josh Soref <[email protected]> * spelling: go Signed-off-by: Josh Soref <[email protected]> * spelling: got Signed-off-by: Josh Soref <[email protected]> * spelling: guaranteed Signed-off-by: Josh Soref <[email protected]> * spelling: guarantees Signed-off-by: Josh Soref <[email protected]> * spelling: guarded Signed-off-by: Josh Soref <[email protected]> * spelling: gzipped Signed-off-by: Josh Soref <[email protected]> * spelling: happened Signed-off-by: Josh Soref <[email protected]> * spelling: healthchecks Signed-off-by: Josh Soref <[email protected]> * spelling: highlighting Signed-off-by: Josh Soref <[email protected]> * spelling: https Signed-off-by: Josh Soref <[email protected]> * spelling: implementation Signed-off-by: Josh Soref <[email protected]> * spelling: implementers Signed-off-by: Josh Soref <[email protected]> * spelling: inadvertently Signed-off-by: Josh Soref <[email protected]> * spelling: incomplete Signed-off-by: Josh Soref <[email protected]> * spelling: incredibly Signed-off-by: Josh Soref <[email protected]> * spelling: independent Signed-off-by: Josh Soref <[email protected]> * spelling: individual Signed-off-by: Josh Soref <[email protected]> * spelling: influxdb Signed-off-by: Josh Soref <[email protected]> * spelling: information Signed-off-by: Josh Soref <[email protected]> * spelling: initialization Signed-off-by: Josh Soref <[email protected]> * spelling: initially Signed-off-by: Josh Soref <[email protected]> * spelling: initiate Signed-off-by: Josh Soref <[email protected]> * spelling: inkwell Signed-off-by: Josh Soref <[email protected]> * spelling: instead Signed-off-by: Josh Soref <[email protected]> * spelling: integer Signed-off-by: Josh Soref <[email protected]> * spelling: integral Signed-off-by: Josh Soref <[email protected]> * spelling: interior Signed-off-by: Josh Soref <[email protected]> * spelling: interpolation Signed-off-by: Josh Soref <[email protected]> * spelling: into Signed-off-by: Josh Soref <[email protected]> * spelling: intrinsic Signed-off-by: Josh Soref <[email protected]> * spelling: invalid Signed-off-by: Josh Soref <[email protected]> * spelling: iterable Signed-off-by: Josh Soref <[email protected]> * spelling: iterator Signed-off-by: Josh Soref <[email protected]> * spelling: javascript Signed-off-by: Josh Soref <[email protected]> * spelling: journalctl Signed-off-by: Josh Soref <[email protected]> * spelling: kube Signed-off-by: Josh Soref <[email protected]> * spelling: kubernetes Signed-off-by: Josh Soref <[email protected]> * spelling: latest Signed-off-by: Josh Soref <[email protected]> * spelling: line Signed-off-by: Josh Soref <[email protected]> * spelling: load Signed-off-by: Josh Soref <[email protected]> * spelling: maintainable Signed-off-by: Josh Soref <[email protected]> * spelling: management Signed-off-by: Josh Soref <[email protected]> * spelling: manually Signed-off-by: Josh Soref <[email protected]> * spelling: match Signed-off-by: Josh Soref <[email protected]> * spelling: matches Signed-off-by: Josh Soref <[email protected]> * spelling: metadata Signed-off-by: Josh Soref <[email protected]> * spelling: methods Signed-off-by: Josh Soref <[email protected]> * spelling: mimicked Signed-off-by: Josh Soref <[email protected]> * spelling: multiple Signed-off-by: Josh Soref <[email protected]> * spelling: mutually Signed-off-by: Josh Soref <[email protected]> * spelling: myriad Signed-off-by: Josh Soref <[email protected]> * spelling: namespace Signed-off-by: Josh Soref <[email protected]> * spelling: necessarily Signed-off-by: Josh Soref <[email protected]> * spelling: necessary Signed-off-by: Josh Soref <[email protected]> * spelling: nokia Signed-off-by: Josh Soref <[email protected]> * spelling: nonexistent Signed-off-by: Josh Soref <[email protected]> * spelling: nonsensical Signed-off-by: Josh Soref <[email protected]> * spelling: notionally Signed-off-by: Josh Soref <[email protected]> * spelling: occasionally Signed-off-by: Josh Soref <[email protected]> * spelling: official Signed-off-by: Josh Soref <[email protected]> * spelling: oldest Signed-off-by: Josh Soref <[email protected]> * spelling: opentelemetry Signed-off-by: Josh Soref <[email protected]> * spelling: opted into Signed-off-by: Josh Soref <[email protected]> * spelling: organization Signed-off-by: Josh Soref <[email protected]> * spelling: original Signed-off-by: Josh Soref <[email protected]> * spelling: overall Signed-off-by: Josh Soref <[email protected]> * spelling: overwritable Signed-off-by: Josh Soref <[email protected]> * spelling: papyre Signed-off-by: Josh Soref <[email protected]> * spelling: particular Signed-off-by: Josh Soref <[email protected]> * spelling: partitioner Signed-off-by: Josh Soref <[email protected]> * spelling: partitions Signed-off-by: Josh Soref <[email protected]> * spelling: payoff Signed-off-by: Josh Soref <[email protected]> * spelling: pending Signed-off-by: Josh Soref <[email protected]> * spelling: permutation Signed-off-by: Josh Soref <[email protected]> * spelling: pipelines Signed-off-by: Josh Soref <[email protected]> * spelling: plumbing Signed-off-by: Josh Soref <[email protected]> * spelling: policy Signed-off-by: Josh Soref <[email protected]> * spelling: possibilities Signed-off-by: Josh Soref <[email protected]> * spelling: postgresql Signed-off-by: Josh Soref <[email protected]> * spelling: preceded Signed-off-by: Josh Soref <[email protected]> * spelling: prometheus Signed-off-by: Josh Soref <[email protected]> * spelling: pseudo Signed-off-by: Josh Soref <[email protected]> * spelling: qualities Signed-off-by: Josh Soref <[email protected]> * spelling: rather Signed-off-by: Josh Soref <[email protected]> * spelling: reading Signed-off-by: Josh Soref <[email protected]> * spelling: receive Signed-off-by: Josh Soref <[email protected]> * spelling: receiver Signed-off-by: Josh Soref <[email protected]> * spelling: receives Signed-off-by: Josh Soref <[email protected]> * spelling: reconcile Signed-off-by: Josh Soref <[email protected]> * spelling: reconciliation Signed-off-by: Josh Soref <[email protected]> * spelling: recreate Signed-off-by: Josh Soref <[email protected]> * spelling: regardless Signed-off-by: Josh Soref <[email protected]> * spelling: regex Signed-off-by: Josh Soref <[email protected]> * spelling: releases Signed-off-by: Josh Soref <[email protected]> * spelling: rendering Signed-off-by: Josh Soref <[email protected]> * spelling: repercussions Signed-off-by: Josh Soref <[email protected]> * spelling: representation Signed-off-by: Josh Soref <[email protected]> * spelling: represented Signed-off-by: Josh Soref <[email protected]> * spelling: required Signed-off-by: Josh Soref <[email protected]> * spelling: respectively Signed-off-by: Josh Soref <[email protected]> * spelling: response Signed-off-by: Josh Soref <[email protected]> * spelling: results Signed-off-by: Josh Soref <[email protected]> * spelling: returns Signed-off-by: Josh Soref <[email protected]> * spelling: rewritten Signed-off-by: Josh Soref <[email protected]> * spelling: scratching Signed-off-by: Josh Soref <[email protected]> * spelling: scripts Signed-off-by: Josh Soref <[email protected]> * spelling: seconds Signed-off-by: Josh Soref <[email protected]> * spelling: segment Signed-off-by: Josh Soref <[email protected]> * spelling: serialized Signed-off-by: Josh Soref <[email protected]> * spelling: significantly Signed-off-by: Josh Soref <[email protected]> * spelling: similar Signed-off-by: Josh Soref <[email protected]> * spelling: simplicity Signed-off-by: Josh Soref <[email protected]> * spelling: simply Signed-off-by: Josh Soref <[email protected]> * spelling: snyk Signed-off-by: Josh Soref <[email protected]> * spelling: some Signed-off-by: Josh Soref <[email protected]> * spelling: something Signed-off-by: Josh Soref <[email protected]> * spelling: somewhere Signed-off-by: Josh Soref <[email protected]> * spelling: specific Signed-off-by: Josh Soref <[email protected]> * spelling: specifically Signed-off-by: Josh Soref <[email protected]> * spelling: specification Signed-off-by: Josh Soref <[email protected]> * spelling: specifies Signed-off-by: Josh Soref <[email protected]> * spelling: spent Signed-off-by: Josh Soref <[email protected]> * spelling: straightforward Signed-off-by: Josh Soref <[email protected]> * spelling: submitted Signed-off-by: Josh Soref <[email protected]> * spelling: succinct Signed-off-by: Josh Soref <[email protected]> * spelling: support Signed-off-by: Josh Soref <[email protected]> * spelling: suppress Signed-off-by: Josh Soref <[email protected]> * spelling: symmetrical Signed-off-by: Josh Soref <[email protected]> * spelling: syntax Signed-off-by: Josh Soref <[email protected]> * spelling: that Signed-off-by: Josh Soref <[email protected]> * spelling: the Signed-off-by: Josh Soref <[email protected]> * spelling: their Signed-off-by: Josh Soref <[email protected]> * spelling: then Signed-off-by: Josh Soref <[email protected]> * spelling: theoretically Signed-off-by: Josh Soref <[email protected]> * spelling: this Signed-off-by: Josh Soref <[email protected]> * spelling: timestamp Signed-off-by: Josh Soref <[email protected]> * spelling: transform Signed-off-by: Josh Soref <[email protected]> * spelling: transport Signed-off-by: Josh Soref <[email protected]> * spelling: ubiquitousness Signed-off-by: Josh Soref <[email protected]> * spelling: unacknowledged Signed-off-by: Josh Soref <[email protected]> * spelling: unavailable Signed-off-by: Josh Soref <[email protected]> * spelling: undermentioned Signed-off-by: Josh Soref <[email protected]> * spelling: unintended Signed-off-by: Josh Soref <[email protected]> * spelling: unknown Signed-off-by: Josh Soref <[email protected]> * spelling: unwieldy Signed-off-by: Josh Soref <[email protected]> * spelling: was Signed-off-by: Josh Soref <[email protected]> * spelling: whatever Signed-off-by: Josh Soref <[email protected]> * spelling: wildcard Signed-off-by: Josh Soref <[email protected]> * spelling: will Signed-off-by: Josh Soref <[email protected]> * spelling: with Signed-off-by: Josh Soref <[email protected]> * spelling: workaround Signed-off-by: Josh Soref <[email protected]> * spelling: wrapper Signed-off-by: Josh Soref <[email protected]> * spelling: you Signed-off-by: Josh Soref <[email protected]> * squash! spelling: unacknowledged spelling: no acknowledge Signed-off-by: Josh Soref <[email protected]> * squash! spelling: kube spelling: kubeconfig Signed-off-by: Josh Soref <[email protected]> * squash! spelling: ampersand Drop counter proposal: `spelling: at_sign` Signed-off-by: Josh Soref <[email protected]> * squash! spelling: unacknowledged spelling: no acknowledge Signed-off-by: Josh Soref <[email protected]> * spelling: at_sign Signed-off-by: Josh Soref <[email protected]> Signed-off-by: Josh Soref <[email protected]>
vectordotdev · Jan 18, 2023 · 6149615 · 6149615
1 parent 9db4c5e
commit 6149615
Show file tree

Hide file tree

Showing 243 changed files with 658 additions and 807 deletions.
diff --git a/.github/workflows/k8s_e2e.yml b/.github/workflows/k8s_e2e.yml
@@ -74,7 +74,7 @@ jobs:
           name: e2e-test-deb-package
           path: target/artifacts/*
 
-  # Github Actions don't support `matrix` at the job-level `if:` condition.
+  # GitHub Actions don't support `matrix` at the job-level `if:` condition.
   # We apply this workaround - compute `matrix` in a preceding job, and assign
   # it's value dynamically at the actual test job.
   # This approach can be advanced further by, for instance, dynamically

diff --git a/.github/workflows/publish.yml b/.github/workflows/publish.yml
@@ -577,8 +577,8 @@ jobs:
         run: make release-s3
 
   publish-github:
-    name: Publish to Github
-    # We only publish to Github for versioned releases, not nightlies.
+    name: Publish to GitHub
+    # We only publish to GitHub for versioned releases, not nightlies.
     if: ${{ inputs.mode == 'Release' }}
     runs-on: ubuntu-20.04
     needs:
@@ -641,7 +641,7 @@ jobs:
         with:
           name: vector-${{ env.VECTOR_VERSION }}-armv7-unknown-linux-musleabihf
           path: target/artifacts
-      - name: Publish release to Github
+      - name: Publish release to GitHub
         env:
           GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
         run: make release-github

diff --git a/Makefile b/Makefile
@@ -43,8 +43,8 @@ export CURRENT_DIR = $(shell pwd)
 export ENVIRONMENT ?= false
 # The upstream container we publish artifacts to on a successful master build.
 export ENVIRONMENT_UPSTREAM ?= docker.io/timberio/vector-dev:sha-3eadc96742a33754a5859203b58249f6a806972a
-# Override to disable building the container, having it pull from the Github packages repo instead
-# TODO: Disable this by default. Blocked by `docker pull` from Github Packages requiring authenticated login
+# Override to disable building the container, having it pull from the GitHub packages repo instead
+# TODO: Disable this by default. Blocked by `docker pull` from GitHub Packages requiring authenticated login
 export ENVIRONMENT_AUTOBUILD ?= true
 # Override this when appropriate to disable a TTY being available in commands with `ENVIRONMENT=true`
 export ENVIRONMENT_TTY ?= true
@@ -478,7 +478,7 @@ check-examples: ## Check that the config/examples files are valid
 	${MAYBE_ENVIRONMENT_EXEC} cargo vdev check examples
 
 .PHONY: check-scripts
-check-scripts: ## Check that scipts do not have common mistakes
+check-scripts: ## Check that scripts do not have common mistakes
 	${MAYBE_ENVIRONMENT_EXEC} cargo vdev check scripts
 
 .PHONY: check-deny
@@ -603,7 +603,7 @@ release-docker: ## Release to Docker Hub
 	@cargo vdev release docker
 
 .PHONY: release-github
-release-github: ## Release to Github
+release-github: ## Release to GitHub
 	@cargo vdev release github
 
 .PHONY: release-homebrew

diff --git a/PRIVACY.md b/PRIVACY.md
@@ -18,8 +18,8 @@ project thinks about privacy now and in the future.
 
 ### Downloads
 
-Vector uses AWS S3, Github assets, [Cloudsmith][cloudsmith], and Docker Hub to host
-release artifacts. Vector does track download counts in aggregate. For Github, Cloudsmith,
+Vector uses AWS S3, GitHub assets, [Cloudsmith][cloudsmith], and Docker Hub to host
+release artifacts. Vector does track download counts in aggregate. For GitHub, Cloudsmith,
 and Docker this data is anonymous, but for AWS S3 IP addresses are logged. There is no
 way to disable IP address tracking within the AWS S3 logs. If you are concerned about
 sharing your IP address we recommend using a proxy, or downloading Vector from a
@@ -41,9 +41,9 @@ derived from backend server logs which are anonymized. Vector uses
 
 ### Vector Repository
 
-The Vector repository is hosted on Github. You can review their privacy policy
+The Vector repository is hosted on GitHub. You can review their privacy policy
 [here][github_pp]. Additionally, Vector will not attempt to mine information
-about users that interact with Vector on Github. Vector team members will
+about users that interact with Vector on GitHub. Vector team members will
 occasionally reach out to active users offer help debugging or learn about
 ways Vector can improve.
 

diff --git a/RELEASES.md b/RELEASES.md
@@ -37,9 +37,9 @@ experimental or breaking changes.
 
 ### Stable channel
 
-* Go to our [Github repository] and click the "watch" button in the top right.
+* Go to our [GitHub repository] and click the "watch" button in the top right.
   Click "Custom" and then "Releases" to only be notified for new releases.
-  See the [Github subscription docs] for more info.
+  See the [GitHub subscription docs] for more info.
 * Subscribe to the [Vector public calendar], release events are added.
 * Follow [@vectordotdev] on Twitter.
 * Head to our [chat], watch the `#announcements` channel, and configure
@@ -92,7 +92,7 @@ Otherwise, the stable release is your best bet.
 [download page]: https://vector.dev/download/
 [nightly artifact list]: https://packages.timber.io/vector/nightly/
 [@vectordotdev]: https://twitter.com/vectordotdev
-[Github repository]: https://github.com/vectordotdev/vector
-[Github subscription docs]: https://docs.github.com/en/github/managing-subscriptions-and-notifications-on-github/managing-subscriptions-for-activity-on-github/viewing-your-subscriptions
+[GitHub repository]: https://github.com/vectordotdev/vector
+[GitHub subscription docs]: https://docs.github.com/en/github/managing-subscriptions-and-notifications-on-github/managing-subscriptions-for-activity-on-github/viewing-your-subscriptions
 [`master` branch]: https://github.com/vectordotdev/vector/tree/master
 [versioning policy]: https://github.com/vectordotdev/vector/blob/master/VERSIONING.md
diff --git a/SECURITY.md b/SECURITY.md
@@ -69,7 +69,7 @@ otherwise undermine security.
 #### Open Source
 
 Vector and its dependencies are open-source. All code and changes are publicly
-available at [our Github repo][urls.vector_repo]. While the transparent nature
+available at [our GitHub repo][urls.vector_repo]. While the transparent nature
 open source helps to improve security, so does the large collaborative
 community behind Vector.
 
@@ -92,7 +92,7 @@ changes are audited and traceable.
 #### Signed Commits
 
 Because of Vector's [merge style](CONTRIBUTING.md#merge-style), commits to
-release branches are signed by Github itself during the squash and merge
+release branches are signed by GitHub itself during the squash and merge
 process. Commits to development branches are encouraged to be signed but not
 required since changes must go through a [review process](#reviews--approvals).
 
@@ -122,7 +122,7 @@ team members.
 ### Two-factor Authentication
 
 All Vector team members are required to enable two-factor authentication
-for their Github accounts.
+for their GitHub accounts.
 
 ### Privilege Model
 
@@ -166,7 +166,7 @@ the [Reviewing guide](REVIEWING.md#dependencies).
 
 ### Change Control
 
-As noted above Vector uses the Git version control system on Github.
+As noted above Vector uses the Git version control system on GitHub.
 
 #### Pull Requests
 
@@ -199,7 +199,7 @@ When possible, we'll create automated checks to enforce security policies.
 - Vector implements [Dependabot][urls.dependabot] which performs automated
   upgrades on dependencies and [alerts][urls.dependabot_alerts] about any
   dependency-related security vulnerabilities.
-- We verify the security of our Docker images using [Synk's][urls.snyk] vulnerability
+- We verify the security of our Docker images using [Snyk's][urls.snyk] vulnerability
   scanning.
 
 #### Vulnerability Remediation

diff --git a/STYLE.md b/STYLE.md
@@ -258,7 +258,7 @@ most portable and well-tested. In cases where the standard library atomics canno
 when using a 64-bit atomic but wanting to support a 32-bit platform, or support a platform without
 atomic instructions at all, we prefer to use
 **[`crossbeam-utils`](https://docs.rs/crossbeam-utils)** and its `AtomicCell` helper. This type will
-automatically handle either using native atomic support or ensuring mutally exclusive access, and
+automatically handle either using native atomic support or ensuring mutually exclusive access, and
 handle it in a transparent way. It uses a fixed acquire/release ordering that generally provides the
 expected behavior when using atomics, but may not be suitable for usages which require stronger
 ordering.
@@ -298,7 +298,7 @@ itself for use cases where pooling is desired.
 
 Synchronization can be a very common sight when writing multi-threaded code in any language, and
 this document does not aim to familiarize you with all of the common synchronization primitives and
-their intended usage. Instesd, however, there are some caveats that you must be aware of when using
+their intended usage. Instead, however, there are some caveats that you must be aware of when using
 synchronization primitives in synchronous versus asynchronous code.
 
 Generally speaking, developers will lean on the synchronization primitives in `std::sync`, such as

diff --git a/VERSIONING.md b/VERSIONING.md
@@ -123,7 +123,7 @@ here. Each minor release bump will include an upgrade guide in the
 [configuration schema]: https://vector.dev/docs/reference/configuration/
 [data directory]: https://vector.dev/docs/reference/configuration/global-options/#data_dir
 [data model]: https://vector.dev/docs/about/under-the-hood/architecture/data-model/
-[Github repository]: https://github.com/vectordotdev/vector
+[GitHub repository]: https://github.com/vectordotdev/vector
 [GraphQL API]: https://vector.dev/docs/reference/api/
 [Installation workflows]: https://vector.dev/docs/setup/installation/
 [`internal_logs_` source]: https://vector.dev/docs/reference/configuration/sources/internal_logs/

diff --git a/benches/languages.rs b/benches/languages.rs
@@ -249,7 +249,7 @@ fn benchmark_configs(
 ) {
     vector::test_util::trace_init();
 
-    // only used for debug assertions so assigned to supress unused warning
+    // only used for debug assertions so assigned to suppress unused warning
     let _ = output;
 
     let num_lines = 10_000;
@@ -319,7 +319,7 @@ fn benchmark_configs(
                             for output_line in &output_lines {
                                 let actual: serde_json::map::Map<String, serde_json::Value> =
                                     serde_json::from_str(output_line).unwrap();
-                                // avoids asserting the actual == expected as the socket trasform
+                                // avoids asserting the actual == expected as the socket transform
                                 // adds dynamic keys like timestamp
                                 for (key, value) in output.iter() {
                                     assert_eq!(Some(value), actual.get(key), "for key {}", key,);

diff --git a/benches/transform/route.rs b/benches/transform/route.rs
@@ -78,7 +78,7 @@ fn route(c: &mut Criterion) {
             output_buffer: output_buffer.clone(),
         },
         // A small filter where a sole field is mapped into a named route, does
-        // not matche.
+        // not match.
         Param {
             slug: "vrl_field_not_match",
             input: event.clone(),

diff --git a/distribution/docker/README.md b/distribution/docker/README.md
@@ -1,6 +1,6 @@
 <p align="center">
   <strong>
-    <a href="https://vector.dev">Website<a/>&nbsp;&nbsp;&bull;&nbsp;&nbsp;<a href="https://vector.dev/docs/">Docs<a/>&nbsp;&nbsp;&bull;&nbsp;&nbsp;<a href="https://vector.dev/community/">Community<a/>&nbsp;&nbsp;&bull;&nbsp;&nbsp;<a href="https://github.com/vectordotdev/vector">Github<a/>
+    <a href="https://vector.dev">Website<a/>&nbsp;&nbsp;&bull;&nbsp;&nbsp;<a href="https://vector.dev/docs/">Docs<a/>&nbsp;&nbsp;&bull;&nbsp;&nbsp;<a href="https://vector.dev/community/">Community<a/>&nbsp;&nbsp;&bull;&nbsp;&nbsp;<a href="https://github.com/vectordotdev/vector">GitHub<a/>
   </strong>
 </p>
 
@@ -115,7 +115,7 @@ Vector maintains special tags that are automatically updated whenever Vector is
 ### Source Files
 
 Vector's Docker source files are located
-[in it's Github repo][urls.vector_docker_source_files].
+[in it's GitHub repo][urls.vector_docker_source_files].
 
 [docs.administration]: https://vector.dev/docs/administration/
 [docs.setup.configuration]: https://vector.dev/docs/setup/configuration/

diff --git a/distribution/docker/README.md.erb b/distribution/docker/README.md.erb
@@ -1,6 +1,6 @@
 <p align="center">
   <strong>
-    <a href="<%= metadata.links.fetch("urls.vector_website") %>">Website<a/>&nbsp;&nbsp;&bull;&nbsp;&nbsp;<a href="<%= metadata.links.fetch("urls.vector_docs") %>">Docs<a/>&nbsp;&nbsp;&bull;&nbsp;&nbsp;<a href="<%= metadata.links.fetch("urls.vector_community") %>">Community<a/>&nbsp;&nbsp;&bull;&nbsp;&nbsp;<a href="<%= metadata.links.fetch("urls.vector_repo") %>">Github<a/>
+    <a href="<%= metadata.links.fetch("urls.vector_website") %>">Website<a/>&nbsp;&nbsp;&bull;&nbsp;&nbsp;<a href="<%= metadata.links.fetch("urls.vector_docs") %>">Docs<a/>&nbsp;&nbsp;&bull;&nbsp;&nbsp;<a href="<%= metadata.links.fetch("urls.vector_community") %>">Community<a/>&nbsp;&nbsp;&bull;&nbsp;&nbsp;<a href="<%= metadata.links.fetch("urls.vector_repo") %>">GitHub<a/>
   </strong>
 </p>
 

diff --git a/docs/CONTRIBUTING.md b/docs/CONTRIBUTING.md
@@ -13,7 +13,7 @@ Vector team member will find this document useful.
   - [Git Branches](#git-branches)
   - [Git Commits](#git-commits)
     - [Style](#style)
-  - [Github Pull Requests](#github-pull-requests)
+  - [GitHub Pull Requests](#github-pull-requests)
     - [Title](#title)
     - [Reviews & Approvals](#reviews--approvals)
     - [Merge Style](#merge-style)
@@ -82,7 +82,7 @@ Please ensure your commits are small and focused; they should tell a story of
 your change. This helps reviewers to follow your changes, especially for more
 complex changes.
 
-### Github Pull Requests
+### GitHub Pull Requests
 
 Once your changes are ready you must submit your branch as a [pull request](https://github.com/vectordotdev/vector/pulls).
 

diff --git a/docs/DEVELOPING.md b/docs/DEVELOPING.md
@@ -253,7 +253,7 @@ the features corresponding to these components in `Cargo.toml`.
 Sinks may implement a health check as a means for validating their configuration
 against the environment and external systems. Ideally, this allows the system to
 inform users of problems such as insufficient credentials, unreachable
-endpoints, non-existent tables, etc. They're not perfect, however, since it's
+endpoints, nonexistent tables, etc. They're not perfect, however, since it's
 impossible to exhaustively check for issues that may happen at runtime.
 
 When implementing health checks, we prefer false positives to false negatives.

diff --git a/docs/DOCUMENTING.md b/docs/DOCUMENTING.md
@@ -48,7 +48,7 @@ suitable for complex data definitions.
 ### Installing CUE
 
 Cue can be [installed](https://cuelang.org/docs/install/) from package managers,
-however it may be necesary to install it from source in order to use the correct
+however it may be necessary to install it from source in order to use the correct
 version that Vector depends on. Currently Vector is using `v0.4.2`. Using a CUE
 version different than this may result in CUE check/build errors. We are aiming
 to improve the developer experience around external tool dependencies ([#15909](https://github.com/vectordotdev/vector/issues/15909)).

diff --git a/lib/codecs/src/decoding/format/gelf.rs b/lib/codecs/src/decoding/format/gelf.rs
@@ -303,7 +303,7 @@ mod tests {
         );
     }
 
-    /// Validates deserializiation succeeds for edge case inputs.
+    /// Validates deserialization succeeds for edge case inputs.
     #[test]
     fn gelf_deserializing_edge_cases() {
         // timestamp is set if omitted from input

diff --git a/lib/codecs/src/decoding/format/syslog.rs b/lib/codecs/src/decoding/format/syslog.rs
@@ -214,7 +214,7 @@ impl Deserializer for SyslogDeserializer {
         let log = match (self.source, log_namespace) {
             (Some(source), LogNamespace::Vector) => {
                 let mut log = LogEvent::from(Value::Bytes(Bytes::from(parsed.msg.to_string())));
-                insert_metatdata_fields_from_syslog(&mut log, source, parsed, log_namespace);
+                insert_metadata_fields_from_syslog(&mut log, source, parsed, log_namespace);
                 log
             }
             _ => {
@@ -244,7 +244,7 @@ fn resolve_year((month, _date, _hour, _min, _sec): IncompleteDate) -> i32 {
     }
 }
 
-fn insert_metatdata_fields_from_syslog(
+fn insert_metadata_fields_from_syslog(
     log: &mut LogEvent,
     source: &'static str,
     parsed: Message<&str>,

diff --git a/lib/codecs/src/gelf.rs b/lib/codecs/src/gelf.rs
@@ -6,7 +6,7 @@ use regex::Regex;
 /// GELF Message fields. Definitions from https://docs.graylog.org/docs/gelf
 pub mod gelf_fields {
 
-    /// <not a field> The latest version of the GELF specificaiton.
+    /// <not a field> The latest version of the GELF specification.
     pub const GELF_VERSION: &str = "1.1";
 
     /// (required) GELF spec version

diff --git a/lib/datadog/filter/src/filter.rs b/lib/datadog/filter/src/filter.rs
@@ -19,7 +19,7 @@ pub trait Filter<V: Debug + Send + Sync + Clone + 'static>: DynClone {
     /// Determine whether a value starts with a prefix.
     fn prefix(&self, field: Field, prefix: &str) -> Box<dyn Matcher<V>>;
 
-    /// Determine whether a value matches a wilcard.
+    /// Determine whether a value matches a wildcard.
     fn wildcard(&self, field: Field, wildcard: &str) -> Box<dyn Matcher<V>>;
 
     /// Compare a field value against `comparison_value`, using one of the `comparator` operators.

diff --git a/lib/datadog/grok/patterns/java.pattern b/lib/datadog/grok/patterns/java.pattern
@@ -15,5 +15,5 @@ CATALINA_DATESTAMP %{MONTH} %{MONTHDAY}, 20%{YEAR} %{HOUR}:?%{MINUTE}(?::?%{SECO
 # yyyy-MM-dd HH:mm:ss,SSS ZZZ eg: 2014-01-09 17:32:25,527 -0800
 TOMCAT_DATESTAMP 20%{YEAR}-%{MONTHNUM}-%{MONTHDAY} %{HOUR}:?%{MINUTE}(?::?%{SECOND}) %{ISO8601_TIMEZONE}
 CATALINALOG %{CATALINA_DATESTAMP:timestamp} %{JAVACLASS:class} %{JAVALOGMESSAGE:logmessage}
-# 2014-01-09 20:03:28,269 -0800 | ERROR | com.example.service.ExampleService - something compeletely unexpected happened...
+# 2014-01-09 20:03:28,269 -0800 | ERROR | com.example.service.ExampleService - something completely unexpected happened...
 TOMCATLOG %{TOMCAT_DATESTAMP:timestamp} \| %{LOGLEVEL:level} \| %{JAVACLASS:class} - %{JAVALOGMESSAGE:logmessage}
diff --git a/lib/datadog/grok/src/parse_grok_rules.rs b/lib/datadog/grok/src/parse_grok_rules.rs
@@ -368,9 +368,9 @@ fn resolves_match_function(
                         let format = String::from_utf8_lossy(b);
                         let result = date::time_format_to_regex(&format, true)
                             .map_err(|_e| Error::InvalidFunctionArguments(match_fn.name.clone()))?;
-                        let mut regext_opt = None;
+                        let mut regex_opt = None;
                         if result.tz_captured {
-                            regext_opt = Some(regex::Regex::new(&result.regex).map_err(|error| {
+                            regex_opt = Some(regex::Regex::new(&result.regex).map_err(|error| {
                                 error!(message = "Error compiling regex", regex = %result.regex, %error);
                                 Error::InvalidFunctionArguments(match_fn.name.clone())
                             })?);
@@ -393,7 +393,7 @@ fn resolves_match_function(
                         let filter = GrokFilter::Date(DateFilter {
                             original_format: format.to_string(),
                             strp_format,
-                            regex_with_tz: regext_opt,
+                            regex_with_tz: regex_opt,
                             target_tz,
                             tz_aware: result.with_tz,
                         });

diff --git a/lib/dnsmsg-parser/src/dns_message.rs b/lib/dnsmsg-parser/src/dns_message.rs
@@ -31,7 +31,7 @@ pub struct DnsQueryMessage {
     pub answer_section: Vec<DnsRecord>,
     pub authority_section: Vec<DnsRecord>,
     pub additional_section: Vec<DnsRecord>,
-    pub opt_pserdo_section: Option<OptPseudoSection>,
+    pub opt_pseudo_section: Option<OptPseudoSection>,
 }
 
 #[derive(Clone, Debug, Default)]

diff --git a/lib/dnsmsg-parser/src/dns_message_parser.rs b/lib/dnsmsg-parser/src/dns_message_parser.rs
@@ -81,7 +81,7 @@ impl DnsMessageParser {
             answer_section: self.parse_dns_message_section(msg.answers())?,
             authority_section: self.parse_dns_message_section(msg.name_servers())?,
             additional_section: self.parse_dns_message_section(msg.additionals())?,
-            opt_pserdo_section: edns_section,
+            opt_pseudo_section: edns_section,
         })
     }