Check for typos (#93)

Author: simcod

.github/workflows/build.yaml

@@ -15,6 +15,9 @@ jobs:
       - name: checkout
         uses: actions/checkout@v5
 
+      - name: Check spelling
+        uses: crate-ci/typos@master
+
       - name: setup-bun
         uses: oven-sh/setup-bun@v2
         with:

README.md

@@ -89,7 +89,7 @@ This file is used to generate the sidebar.
 
 ## Embedding drawio images
 
-> ⚠️ referenced `.drawio.svg` images throw **warnings** because of unsupported file-types. We save `.drawio` files separatly and export them as `svg`. Issue is also known in [docusaurus](https://github.com/facebook/docusaurus/issues/9715)
+> ⚠️ referenced `.drawio.svg` images throw **warnings** because of unsupported file-types. We save `.drawio` files separately and export them as `svg`. Issue is also known in [docusaurus](https://github.com/facebook/docusaurus/issues/9715)
 
 Some svgs still can have problems e.g:
 

_typos.toml

@@ -0,0 +1,8 @@
+[default.extend-words]
+# Don't correct the surname "Teh"
+CLOS = "CLOS"
+leafs = "leafs"
+nd = "nd"
+
+[files]
+extend-exclude = ["*.svg", "*.drawio", "allocate.yml"]

blog/2023/08-metal-stack-v0.15.0/index.md

@@ -27,7 +27,7 @@ Check out the direct link to the release [here](https://github.com/metal-stack/r
 
 Before metal-stack v0.15.0, when creating a machine through the metal-api, the machine was placed randomly inside a partition. The algorithm did not consider spreading machines across different racks and different chassis.
 
-This may lead to the situation that a group of machines (that for example form a cluster) can end up being placed in the same rack and the same chassis. In certain meltdown scenarios like a rack loosing power or chassis meltdown, it is desirable have machines within a project spread across data ceneter racks as best as possible.
+This may lead to the situation that a group of machines (that for example form a cluster) can end up being placed in the same rack and the same chassis. In certain meltdown scenarios like a rack losing power or chassis meltdown, it is desirable have machines within a project spread across data ceneter racks as best as possible.
 
 So, instead of just randomly deciding the placement of a machine candidate, there is now a placement strategy that distributes machines within the same partition on the available racks evenly. For placement, it is also possible to allocate machines with so called "placement tags", allowing own distribution groups defined by the user. With this release, our Gardener integration already takes this opportunity to spread cluster workers across racks utilizing the cluster ID tag.
 

docs/contributing/01-Proposals/MEP12/README.md

@@ -8,7 +8,7 @@ sidebar_position: 12
 
 Currently, when creating a machine through the metal-api, the machine is placed randomly inside a partition. This algorithm does not consider spreading machines across different racks and different chassis. This may lead to the situation that a group of machines (that for example form a cluster) can end up being placed in the same rack and the same chassis.
 
-Spreading a group of machines across racks can enhance availability for scenarios like a rack loosing power or a chassis meltdown.
+Spreading a group of machines across racks can enhance availability for scenarios like a rack losing power or a chassis meltdown.
 
 So, instead of just randomly deciding the placement of a machine candidate, we want to propose a placement strategy that attempts to spread machine candidates across the racks inside a partition.
 

docs/docs/07-Release Notes/v0.21/v0.21.3.md

@@ -1,10 +1,10 @@
----
-slug: /release-notes/v0.21.3
-title: v0.21.3
-sidebar_position: 6
----
-# metal-stack v0.21.3
-See original release note at [https://github.com/metal-stack/releases/releases/tag/v0.21.3](https://github.com/metal-stack/releases/releases/tag/v0.21.3)
+---
+slug: /release-notes/v0.21.3
+title: v0.21.3
+sidebar_position: 6
+---
+# metal-stack v0.21.3
+See original release note at [https://github.com/metal-stack/releases/releases/tag/v0.21.3](https://github.com/metal-stack/releases/releases/tag/v0.21.3)
 ## General
 * [Gardener v1.112](https://github.com/gardener/gardener/releases/tag/v1.112.0)
 
@@ -17,7 +17,7 @@ See original release note at [https://github.com/metal-stack/releases/releases/t
 
 ## Component Releases
 ### node-init v0.1.7
-* Wrap erros for better understanding (metal-stack/node-init#16) @majst01
+* Wrap errors for better understanding (metal-stack/node-init#16) @majst01
 ### helm-charts v0.4.23
 * increase default memory limit for wal-g-exporter (metal-stack/helm-charts#119) @TLINDEN
 ### metal-roles v0.15.15

versioned_docs/version-v0.21.8/contributing/01-Proposals/MEP12/README.md

@@ -8,7 +8,7 @@ sidebar_position: 12
 
 Currently, when creating a machine through the metal-api, the machine is placed randomly inside a partition. This algorithm does not consider spreading machines across different racks and different chassis. This may lead to the situation that a group of machines (that for example form a cluster) can end up being placed in the same rack and the same chassis.
 
-Spreading a group of machines across racks can enhance availability for scenarios like a rack loosing power or a chassis meltdown.
+Spreading a group of machines across racks can enhance availability for scenarios like a rack losing power or a chassis meltdown.
 
 So, instead of just randomly deciding the placement of a machine candidate, we want to propose a placement strategy that attempts to spread machine candidates across the racks inside a partition.
 

versioned_docs/version-v0.21.8/docs/07-Release Notes/v0.21/v0.21.3.md

@@ -1,10 +1,10 @@
----
-slug: /release-notes/v0.21.3
-title: v0.21.3
-sidebar_position: 6
----
-# metal-stack v0.21.3
-See original release note at [https://github.com/metal-stack/releases/releases/tag/v0.21.3](https://github.com/metal-stack/releases/releases/tag/v0.21.3)
+---
+slug: /release-notes/v0.21.3
+title: v0.21.3
+sidebar_position: 6
+---
+# metal-stack v0.21.3
+See original release note at [https://github.com/metal-stack/releases/releases/tag/v0.21.3](https://github.com/metal-stack/releases/releases/tag/v0.21.3)
 ## General
 * [Gardener v1.112](https://github.com/gardener/gardener/releases/tag/v1.112.0)
 
@@ -17,7 +17,7 @@ See original release note at [https://github.com/metal-stack/releases/releases/t
 
 ## Component Releases
 ### node-init v0.1.7
-* Wrap erros for better understanding (metal-stack/node-init#16) @majst01
+* Wrap errors for better understanding (metal-stack/node-init#16) @majst01
 ### helm-charts v0.4.23
 * increase default memory limit for wal-g-exporter (metal-stack/helm-charts#119) @TLINDEN
 ### metal-roles v0.15.15