Fixed typos

.github/workflows/build_rakudo-star.yml

@@ -1,5 +1,5 @@
-# This workflow enforces always the "Rakodo latest" release as the basis for the to-build Star release
-# As we always work with TAGs, the two build tools could get the TAG as a parameter and then build this relaase instead of always building "Rakudo latest"
+# This workflow enforces always the "Rakudo latest" release as the basis for the to-build Star release
+# As we always work with TAGs, the two build tools could get the TAG as a parameter and then build this release instead of always building "Rakudo latest"
 #  Will enhance the workflow later to getr a TAG as an input
 
 name: Build Rakudo Star Releases (Windows MSI and Linux RSTAR source)
@@ -64,7 +64,7 @@ jobs:
           gpg_private_key: ${{ secrets.GPG_PRIVATE_KEY }}
           passphrase: ${{ secrets.PASSPHRASE }}
           fingerprint: ${{ env.GPG_FINGERPRINT }}
-      - name: Create RSTAR Distrubution
+      - name: Create RSTAR Distribution
         run: ./bin/rstar dist
       - name: List my stuff
         run: ls -lAR -I ".git" -I "src"

.github/workflows/publish_rakudo-star_on_rakudo.org.yml

@@ -2,13 +2,13 @@
 name: Upload Rakudo-Star to Rakudo.org
 
 on:
-  schedule: # Allways later then the publishing of the Rakudo-Star releases at GH, see https://github.com/rakudo/star/blob/1149d43fd272661a1dbbcb9328200df24d1c2e81/.github/workflows/sync_latest_rakudo_release.yml#L11
+  schedule: # Always later then the publishing of the Rakudo-Star releases at GH, see https://github.com/rakudo/star/blob/1149d43fd272661a1dbbcb9328200df24d1c2e81/.github/workflows/sync_latest_rakudo_release.yml#L11
     - cron:  '55 1 * * 1,4'
   workflow_dispatch:
 
 env:
   RKD_REVISION: "01" # Default build revision if RKD_STR_GH below has only a VERSION and not a revision (say, something like 202203-01 is expected)
-  DEBUG: 0           # Set this to 1 or anythin other then 0 (ZERO) for more debut output
+  DEBUG: 0           # Set this to 1 or anything other then 0 (ZERO) for more debut output
 
 jobs:
   upload_star_release:

.github/workflows/sync_latest_rakudo_release.yml

@@ -1,6 +1,6 @@
 # See https://stackoverflow.com/questions/58465057/trigger-a-github-action-when-another-repository-creates-a-new-release
 # 
-# This Action works only because of the avilable "build_rakudo-star.yml" Action.
+# This Action works only because of the available "build_rakudo-star.yml" Action.
 ## Actually this here triggers the other build Action by adding a new TAG (Rakudo releases are having TAGs)
 ## TODO: switch to env vars later
 

README.md

@@ -4,7 +4,7 @@ A *user-friendly* distribution of the [Raku programming language](https://raku.o
 
 ## Docker Image
 
-* Please refer to [Rakodo-Star on Docker Hub](https://hub.docker.com/_/rakudo-star) for an image
+* Please refer to [Rakudo-Star on Docker Hub](https://hub.docker.com/_/rakudo-star) for an image
 * Find the related Docker files on the ["Raku Docker" GitHub repository](https://github.com/Raku/docker) 
 
 ## What's in this GIT repo
@@ -55,7 +55,7 @@ depending on the protocol.
 
 * If you have a question about Rakudo Star, you probably want to write to the “[email protected]” mailing list or ask the [irc.libera.chat/#raku-star](https://web.libera.chat/#raku-star) IRC channel.
 
-#### Github Plattform
+#### GitHub Platform
 
 * Knowledge and documentation related to Rakudo Star can be published in the related [wiki](https://github.com/rakudo/star/wiki).
 * There is also [Star discussions](https://github.com/rakudo/star/discussions) for any kind of ongoing discussions, alignements, FAQ's, ...

lib/main.bash

@@ -98,7 +98,7 @@ Actions:
 	              directory will also be removed.
 	dist          Create a distributable tarball of this repository. If no
 	              version identifier is specified, it will assume it should
-	              build ontop of the latest RAKUDO release and therefore
+	              build on top of the latest RAKUDO release and therefore
 	              check "https://github.com/rakudo/rakudo/releases/latest"
 	              for something like i.e. "2020.08" or "2020.08.1".
 	              If the "RAKUDO latest" doesn't match, it will use the

lib/util.bash

@@ -173,7 +173,7 @@ tmpdir() {
 
 	dir="$(mktemp -d)"
 
-	# Ensure the file was created succesfully
+	# Ensure the file was created successfully
 	if [[ ! -d "$dir" ]]
 	then
 		die "Failed to create a temporary directory at $dir"
@@ -192,7 +192,7 @@ tmpfile() {
 
 	file="$(mktemp)"
 
-	# Ensure the file was created succesfully
+	# Ensure the file was created successfully
 	if [[ ! -f "$file" ]]
 	then
 		die "Failed to create a temporary file at $file"

tools/build/binary-release/Windows/build-with-choco.ps1

@@ -2,7 +2,7 @@ param ([string]$RAKUDO_VER, [switch]$sign, [switch]$keep)
 
 # inspired by https://github.com/hankache/rakudo-star-win/blob/master/build.ps1
 # expected $RAKUDO_VER is something like "2021.03"
-# if none is given, we will try to get the "latest" from gihub
+# if none is given, we will try to get the "latest" from GitHub
 
 # $ErrorActionPreference = "stop"
 

tools/build/binary-release/Windows/star.wxs

@@ -83,7 +83,7 @@
 
 		<!--UI Reference-->
 		<UIRef Id="WixUI_Common" />
-		<!--Artisric License-->
+		<!--Artistic License-->
 		<WixVariable Id="WixUILicenseRtf" Value="License.rtf" />
 
         <UI Id="WixUI_InstallDir">

tools/pretty_print_modules.bash

@@ -25,7 +25,7 @@ function clean_modules_dir() {
 
 }
 
-# If module file names are given as parametrs, ensure the directories exist to store those files
+# If module file names are given as parameters, ensure the directories exist to store those files
 function mk_local_modules_dirs() {
 
     local LOCAL_MODULES_DIR