diff --git a/‎.github/workflows/k8s_e2e.yml‎
Lines changed: 1 addition & 1 deletion b/‎.github/workflows/k8s_e2e.yml‎
Lines changed: 1 addition & 1 deletion
diff --git a/‎.github/workflows/publish.yml‎
Lines changed: 3 additions & 3 deletions b/‎.github/workflows/publish.yml‎
Lines changed: 3 additions & 3 deletions
diff --git a/‎Makefile‎
Lines changed: 4 additions & 4 deletions b/‎Makefile‎
Lines changed: 4 additions & 4 deletions
diff --git a/‎PRIVACY.md‎
Lines changed: 4 additions & 4 deletions b/‎PRIVACY.md‎
Lines changed: 4 additions & 4 deletions
diff --git a/‎RELEASES.md‎
Lines changed: 4 additions & 4 deletions b/‎RELEASES.md‎
Lines changed: 4 additions & 4 deletions
diff --git a/‎SECURITY.md‎
Lines changed: 5 additions & 5 deletions b/‎SECURITY.md‎
Lines changed: 5 additions & 5 deletions
diff --git a/‎STYLE.md‎
Lines changed: 2 additions & 2 deletions b/‎STYLE.md‎
Lines changed: 2 additions & 2 deletions
diff --git a/‎VERSIONING.md‎
Lines changed: 1 addition & 1 deletion b/‎VERSIONING.md‎
Lines changed: 1 addition & 1 deletion
diff --git a/‎benches/languages.rs‎
Lines changed: 2 additions & 2 deletions b/‎benches/languages.rs‎
Lines changed: 2 additions & 2 deletions
diff --git a/‎benches/transform/route.rs‎
Lines changed: 1 addition & 1 deletion b/‎benches/transform/route.rs‎
Lines changed: 1 addition & 1 deletion
@@ -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
 
@@ -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
 
@@ -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
 
@@ -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.
 
 
@@ -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
@@ -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
 
@@ -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
 
@@ -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/
 
@@ -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,);
 
@@ -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(),