fix: Several typos (#422)

## 📝 Description

Wanted to have a look around the codebase, wow, there's a lot going on,
gotta say, it's impressive.

Spotted a couple of typoes in my travels so ran a bit of spellchecking
and amended a few of them, tbh they're all readable enough, just turbo
nitpicking, let me know/remove bits if this'll cause issues.

N.b. Did this before in the Semaphore docs,
semaphoreci/semaphore#290 and it's nice to use
docs + tools where you don't just have to moan if something doesn't make
sense/spot a typo, but being able to fix it is a delight.

## ✅ Checklist
- [ ] I have tested this change
- [ ] This change requires documentation update

---------

Co-authored-by: Veljko Maksimovic <[email protected]>

Author: pieterocp

artifacthub/pkg/workers/bucketcleaner/README.md

@@ -22,10 +22,10 @@ The bucket cleaner is a distributed system based on supervisor/worker pattern.
 In this system, we have:
 
 - A supervisor called "Scheduler" that schedules which buckets need to be cleaned up
-- A worker called "Worker" which listens to the suprvisor and executes the cleanup
+- A worker called "Worker" which listens to the supervisor and executes the cleanup
 
 Communication between the supervisor and the worker is done via AMQP.
-The recomended setup for the system is to have one instance (in kubernetes a pod)
+The recommended setup for the system is to have one instance (in kubernetes a pod)
 that runs the scheduler, and multiple instances that listen and do the work.
 
 Diagram of communication:

auth/test/auth/cli_test.exs

@@ -9,7 +9,7 @@ defmodule Auth.CliTest do
       refute Auth.Cli.is_call_from_deprecated_cli?(conn)
     end
 
-    test "SempahoreCLI user agent with a fresh version => returns false" do
+    test "SemaphoreCLI user agent with a fresh version => returns false" do
       conn = conn(:get, "https://org1.semaphoretest.test/exauth/api/v1alpha/jobs")
       conn = conn |> put_req_header("user-agent", "SemaphoreCLI/v0.30.0 (...)")
 

badge/test/badges/api_test.exs

@@ -55,7 +55,7 @@ defmodule Badges.ApiTest do
   end
 
   describe "/badges/testproject.svg" do
-    test "when branch is ommited => look for master" do
+    test "when branch is omitted => look for master" do
       GrpcMock.stub(PipelineMock, :list_keyset, fn _, _ ->
         InternalApi.Plumber.ListKeysetResponse.new(pipelines: [Support.Factories.pipeline()])
       end)
@@ -127,7 +127,7 @@ defmodule Badges.ApiTest do
       assert conn.resp_body =~ "passed"
     end
 
-    test "private project wihout key => returns 404" do
+    test "private project without key => returns 404" do
       GrpcMock.stub(ProjectMock, :describe, fn _, _ ->
         InternalApi.Projecthub.DescribeResponse.new(
           metadata: Support.Factories.response_meta(:OK),

branch_hub/.gitignore

@@ -2,16 +2,16 @@
 /_build/
 /deps/
 /db
-/deps
 /log
 /*.ez
 *.swp
 
+# The directory Mix downloads your dependencies sources to.
+/deps
+
 # If you run "mix test --cover", coverage assets end up here.
 /cover/
 
-# The directory Mix downloads your dependencies sources to.
-/deps/
 
 # Where third-party dependencies like ExDoc output generated docs.
 /doc/

branch_hub/test/branch_hub/model/branches_queries_test.exs

@@ -59,7 +59,7 @@ defmodule BranchHub.Model.BranchesQueries.Test do
     refute branch_1.used_at == branch_2.used_at
   end
 
-  test "insert new branch if diffrent name" do
+  test "insert new branch if different name" do
     params = [
       name: "rw/branch",
       display_name: "rw/branch",

docs/docs-contributing/CONTRIBUTING.md

@@ -67,7 +67,7 @@ To set up a local environment for contributing to Semaphore documentation:
 
 2. Clone or fork the repository
 
-   - **External Contributors** (no write access to upstream): navigate to [sempahoreci/semaphore](https://github.com/semaphoreci/semaphore), click **Fork**, then select **Create a new fork**. Run the following command to clone the repository:
+   - **External Contributors** (no write access to upstream): navigate to [semaphoreci/semaphore](https://github.com/semaphoreci/semaphore), click **Fork**, then select **Create a new fork**. Run the following command to clone the repository:
 
    ```bash
    git clone https://github.com/<your-github-username>/semaphore

docs/docs-contributing/VERSIONING.md

@@ -10,8 +10,8 @@ This page describes how to create a new version or release.
 We handle docs in two ways:
 
 - Cloud: the cloud edition is unversioned. The docs are located on `docs/`
-- Community Edition: the open-source edition is versined. The docs are located on `versioned_docs/version-CE/`
-- Enterprise Edition: the licensed on-premise is also versined. The docs are located on `versioned_docs/version-EE/`
+- Community Edition: the open-source edition is versioned. The docs are located on `versioned_docs/version-CE/`
+- Enterprise Edition: the licensed on-premise is also versioned. The docs are located on `versioned_docs/version-EE/`
 
 ## Naming conventions
 
@@ -147,7 +147,7 @@ npm run build
 npm run serve
 ```
 
-Open a browser and check that the drowpdown works and the new version is working.
+Open a browser and check that the dropdown works and the new version is working.
 
 ## How to remove versions
 
@@ -167,7 +167,7 @@ There are two options to deal with unavailable versions:
 1. Delete the content: delete the content from the version
 2. Mark it as unavailable: keep the title or subheader but clearly mark it as unavailable. Add links to other editions where the feature is available
 
-As a general rule, we shold make it clear when a feature is unavailable, especially for very prominent features such as Promotions, RBAC, or other enterprise-grade features.
+As a general rule, we should make it clear when a feature is unavailable, especially for very prominent features such as Promotions, RBAC, or other enterprise-grade features.
 
 ### How to manage pages missing in editions
 

docs/docs-drafts/gke_install.md

@@ -33,7 +33,7 @@ export CERTS_DIR=$HOME/mycerts
 
 You only need to create the SSL certificate for your domain.
 
-1. Execute the following command to create the certificates. Follow on-sreen instructions. You will be asked to create a DNS TXT record with a specific value. Press enter only after you have created the DNS Record.
+1. Execute the following command to create the certificates. Follow on-screen instructions. You will be asked to create a DNS TXT record with a specific value. Press enter only after you have created the DNS Record.
 
 ```shell
 source .env
@@ -178,7 +178,7 @@ kubectl wait --timeout=90s --for=condition=available deployment emissary-apiext
 
 ```shell
 =============================================================================================
-Congratulations, Semaphore has been installed succesfully!
+Congratulations, Semaphore has been installed successfully!
 
 To start using the app, go to https://id.<your-domain>/login
 

docs/docs/getting-started/changelog.md

@@ -1046,7 +1046,7 @@ To learn more about this image, check our [Ubuntu 22.04 page](../reference/os-ub
 - Rust 1.70.0 -> 1.72.1
 - Sbt 1.8.3 -> 1.9.6
 - Terraform 1.4.6 -> 1.5.7
-- Vrtualenv 20.23.0 -> 20.24.5
+- Virtualenv 20.23.0 -> 20.24.5
 
 To learn more about this image, check our [Ubuntu 22.04 ARM page](../reference/os-ubuntu-images/ubuntu-2204-arm-image)
 
@@ -3649,7 +3649,7 @@ The Ubuntu 18.04 image has been deprecated.
 - Fixed ligatures that are displayed in test output.
 - More generic test result sample files.
 
-To learn how to set up a Test Summary check [our docummentation](../using-semaphore/tests/test-reports).
+To learn how to set up a Test Summary check [our documentation](../using-semaphore/tests/test-reports).
 
 **(Improved) Ubuntu 20.04 image update**
 
@@ -3729,7 +3729,7 @@ Take the advantage of this new feature now to:
 - Sort and filter the output of your tests however you see fit.
 - Search through big test suits to find what you're looking for.
 
-To learn more about how to configure the Test Summary feature, check our [docummentation](../using-semaphore/tests/test-reports).
+To learn more about how to configure the Test Summary feature, check our [documentation](../using-semaphore/tests/test-reports).
 
 **(New) Parameterized promotions (beta)**  
 With parameterized promotions, you can re-use a single promotion pipeline and use environment variables to achieve different results based on the variable values.
@@ -4559,10 +4559,11 @@ To learn more about this image, check our macOS Xcode 11 page.
 
 ## Week of August 24, 2020
 
-**(New) Information on promoter is stored in related enviroment variable**  
+**(New) Information on promoter is stored in related environment variable**  
+
 Inside a Semaphore job you can now see who initiated a promotion by checking the value of the `SEMAPHORE_PIPELINE_PROMOTED_BY` environment variable.
 
-Information on all available enviroment variables can be found in our [documentation](../reference/env-vars).
+Information on all available environment variables can be found in our [documentation](../reference/env-vars).
 
 **(Improved) Ubuntu 18.04 image update**  
 **(Updated)** Language versions:

docs/docs/getting-started/faq.md

@@ -110,7 +110,7 @@ Not directly from the Semaphore website. After a subscription has been purchased
 
 If you wish to change the VAT number associated with your subscription, please get in touch with `[email protected]` with the VAT number you want to add and we will gladly make it happen.
 
-For security reasons, these requests **must originate from an email** linked to a user with the [Owner role](../using-semaphore/rbac#org-owner), or from the current Billing contact associated with the organization’s FastSpring subscription. This ensuress that only authorized individuals can make changes to the billing information.
+For security reasons, these requests **must originate from an email** linked to a user with the [Owner role](../using-semaphore/rbac#org-owner), or from the current Billing contact associated with the organization’s FastSpring subscription. This ensures that only authorized individuals can make changes to the billing information.
 
 ### Will I get an invoice?