From c313d375a4cd9857ae3efab07de76a86deb0afaf Mon Sep 17 00:00:00 2001
From: Sean McGinnis <sean.mcginnis@gmail.com>
Date: Fri, 23 Feb 2024 08:44:40 -0600
Subject: [PATCH] Minor typo fixes

I noticed a few places in the repo where there were some misspellings.
This is a minor update to correct those instances.

Signed-off-by: Sean McGinnis <sean.mcginnis@gmail.com>
---
 .github/ISSUE_TEMPLATE/bug_report.yml      | 6 +++---
 .github/ISSUE_TEMPLATE/feature_request.yml | 2 +-
 .github/PULL_REQUEST_TEMPLATE.md           | 2 +-
 README.md                                  | 4 ++--
 4 files changed, 7 insertions(+), 7 deletions(-)

diff --git a/.github/ISSUE_TEMPLATE/bug_report.yml b/.github/ISSUE_TEMPLATE/bug_report.yml
index 4443b0e..32ca48a 100644
--- a/.github/ISSUE_TEMPLATE/bug_report.yml
+++ b/.github/ISSUE_TEMPLATE/bug_report.yml
@@ -37,7 +37,7 @@ body:
           <em>Why?</em>
         </summary>
 
-        We would do it by ourselves but unfortunatelly, the curent
+        We would do it by ourselves but unfortunately, the current
         edition of GitHub Issue Forms Alpha does not support this yet 🤷
 
 
@@ -55,7 +55,7 @@ body:
     label: Ansible Version
     description: >-
       Paste verbatim output from `ansible --version` below, under
-      the prompt line. Please don't wrap it with tripple backticks — your
+      the prompt line. Please don't wrap it with triple backticks — your
       whole input will be turned into a code snippet automatically.
     render: console
     placeholder: |
@@ -102,7 +102,7 @@ body:
     description: |
       Describe what actually happened.
 
-      Paste command output and don't wrap it with tripple backticks — your
+      Paste command output and don't wrap it with triple backticks — your
       whole input will be turned into a code snippet automatically.
     render: console
     placeholder: Ansible command output...
diff --git a/.github/ISSUE_TEMPLATE/feature_request.yml b/.github/ISSUE_TEMPLATE/feature_request.yml
index 1db645e..c5e3fee 100644
--- a/.github/ISSUE_TEMPLATE/feature_request.yml
+++ b/.github/ISSUE_TEMPLATE/feature_request.yml
@@ -37,7 +37,7 @@ body:
           <em>Why?</em>
         </summary>
 
-        We would do it by ourselves but unfortunatelly, the curent
+        We would do it by ourselves but unfortunately, the current
         edition of GitHub Issue Forms Alpha does not support this yet 🤷
 
 
diff --git a/.github/PULL_REQUEST_TEMPLATE.md b/.github/PULL_REQUEST_TEMPLATE.md
index e712177..f75d607 100644
--- a/.github/PULL_REQUEST_TEMPLATE.md
+++ b/.github/PULL_REQUEST_TEMPLATE.md
@@ -10,7 +10,7 @@ Please include a summary of the change and which issue is fixed.
 - [ ] New feature (non-breaking change which adds functionality)
 - [ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
 - [ ] This change requires a documentation update
-- [ ] Small minor change not affecting the Ansible Role code (Github Actions Workflow, Documentation etc.)
+- [ ] Small minor change not affecting the Ansible Role code (GitHub Actions Workflow, Documentation etc.)
 
 ## How Has This Been Tested?
 <!---
diff --git a/README.md b/README.md
index 7c26d5e..8f060f3 100644
--- a/README.md
+++ b/README.md
@@ -18,9 +18,9 @@ The Role can install the RKE2 in 3 modes:
 - RKE2 Cluster with Server(Master) in High Availability mode and zero or more Agent(Worker) nodes. In HA mode you should have an odd number (three recommended) of server(master) nodes that will run etcd, the Kubernetes API (Keepalived VIP or Kube-VIP address), and other control plane services.
 
 ---
-- Additionaly it is possible to install the RKE2 Cluster (all 3 modes) in Air-Gapped functionality with the use of local artifacts.
+- Additionally it is possible to install the RKE2 Cluster (all 3 modes) in Air-Gapped functionality with the use of local artifacts.
 
-> It is possible to upgrade RKE2 by changing `rke2_version` variable and re-running the playbook with this role. During the upgrade process the RKE2 service on the nodes wil be restarted one by one. The Ansible Role will check if the node on which the service was restarted is in Ready state and only then procede with restarting service on another Kubernetes node.
+> It is possible to upgrade RKE2 by changing `rke2_version` variable and re-running the playbook with this role. During the upgrade process the RKE2 service on the nodes will be restarted one by one. The Ansible Role will check if the node on which the service was restarted is in Ready state and only then proceed with restarting service on another Kubernetes node.
 
 ## Requirements