Grammar and spelling fixes by Grammarly

Author: jbrejner

.markdownlint.json

@@ -1,5 +1,5 @@
 {
-  "MD013" :false ,
+  "MD013": false,
   "MD033": {
       "allowed_elements": ["details", "summary"]
     }

README.md

@@ -7,7 +7,7 @@ Whether you are a beginner looking to understand the basics or an experienced us
 ## About Argo CD
 
 Argo CD is a declarative, GitOps continuous delivery tool for Kubernetes.
-It allows for Kubernetes resources to be managed using git repositories as the source of truth, making it easier to implement continuous deployment strategies in cloud-native environments.
+It enables Kubernetes resources to be managed using Git repositories as the source of truth, making it easier to implement continuous deployment strategies in cloud-native environments.
 For more info on ArgoCD itself, please visit [their website](https://argoproj.github.io/cd/).
 
 ## Exercise list in order
@@ -25,7 +25,7 @@ It is recommended to follow the exercises in the following order.
 ## Using this outside of the workshop
 
 You need to have ArgoCD installed and running.
-All exercises should work on minikube, or kind.
+All exercises should work on minikube or kind.
 You can refer to the [installation link](https://argo-cd.readthedocs.io/en/stable/operator-manual/installation/) for how to install ArgoCD.
 You do not need the HA setup for the exercises.
 

app-of-apps.md

@@ -2,31 +2,31 @@
 
 ## Learning Goals
 
-- Create a bootstrap app manifest
+- Create a Bootstrap app manifest
 - Arrange Argo CD app manifests in a folder structure
 
 ## Introduction
 
-In this exercise, we will work on organizing and managing Argo CD applications more effectively. We will create a bootstrap app manifest to serve as a starting point, structure our repository to accommodate multiple apps, and work with a new app manifest for a Helm chart.
+In this exercise, we will work on organizing and managing Argo CD applications more effectively. We will create a Bootstrap app manifest to serve as a starting point, structure our repository to accommodate multiple apps, and work with a new app manifest for a Helm chart.
 
 ## Exercise
 
 ### Overview
 
 - Create Bootstrap App Manifest
-- Create Folder for All Apps
+- Create a folder for All Apps
 - Move Jenkins App Manifest
 - Create the App Manifest for the Quotes Helm Chart
 
-### Step by step instructions
+### Step-by-step instructions
 
 <details>
 <summary>More Details</summary>
 
-- Create bootsrap app manifest
-- Create folder for all apps in the repo
+- Create Bootstrap app manifest
+- Create a folder for all apps in the repo
 - Move Jenkins app manifest to the folder
-- Create the app manifest for the quotes helm chart located in the same repo. (OR IN THE OTHER REPO TODO)
+- Create the app manifest for the quotes Helm chart located in the same repo. (OR IN THE OTHER REPO TODO)
   - Enable sync policy, prune and self-heal
 - kubectl delete parent app, make sure nothing is there. kubectl apply parent app again.
 
@@ -68,7 +68,7 @@ kubectl apply -f bootstrap-app.yaml
 
 1. Go to the Argo CD UI and verify that the bootstrap app is present. It should have an error saying that it cannot find the `apps` folder. This is expected.
 
-## Step 2: Create Folder for All Apps, and add Jenkins App Manifest to it
+## Step 2: Create a folder for All Apps, and add Jenkins App Manifest to it
 
 Save the current application manifest to your repository in a new folder named `apps`.
 
@@ -117,11 +117,11 @@ spec:
 - Add, commit and push the jenkins-app.yaml to the repository.
 - Go to the Argo CD UI and verify that the bootstrap app is present. It should now be updated to include the `apps` folder, and therefore the Jenkins app manifest.
 
-Now the jenkins app is connected with the bootstrap app.
+Now the Jenkins app is connected with the bootstrap app.
 
-## Delete the jenkins app
+## Delete the Jenkins app
 
-- In the Argo CD UI, delete the jenkins app.
+- In the Argo CD UI, delete the Jenkins app.
 - What happens when you do that?
 
 ## Create the App Manifest for the Quotes Helm Chart
@@ -161,7 +161,7 @@ spec:
 
 1. Verify the applications are synced and running as expected.
 
-1. Delete the bootstrap app from your cluster:
+1. Delete the Bootstrap app from your cluster:
 
 ```bash
 kubectl delete -f bootstrap-app.yaml
@@ -181,7 +181,7 @@ kubectl apply -f bootstrap-app.yaml
 
 1. Verify the applications are synced and running as expected again.
 
-You have now seen how fast it is to reapply your manifests to the cluster. This is a great way to recover from a disaster, or to make sure that your cluster is in the desired state.
+You have now seen how fast it is to reapply your manifests to the cluster. This is a great way to recover from a disaster or to make sure that your cluster is in the desired state.
 
 </details>
 

applicationsets.md

@@ -2,36 +2,36 @@
 
 ## Learning Goals
 
-- Trying out a pull request based application set
+- Trying out a pull-request based application set
 
 ## Introduction
 
-In this exercise we will try out a pull request based application set. We will try to create an application set that will create an application for each pull request in a repository.
+In this exercise, we will try out a pull-request based application set. We will try to create an application set that will create an application for each pull request in a repository.
 
 ## Application set
 
 The sole responsibility of the ApplicationSet controller is to create, update, and delete `Application` resources within the Argo CD namespace. The controller's only job is to ensure that the Application resources remain consistent with the defined declarative ApplicationSet resource, and nothing more.
 
-Thus the ApplicationSet controller does not create/modify/delete Kubernetes resources (other than the Application CR)
+Thus, the ApplicationSet controller does not create/modify/delete Kubernetes resources (other than the Application CR)
 
 ## Exercise
 
 ### Overview
 
-- Create a github token
+- Create a GitHub token
 - Add the token to a secret in the argocd namespace
 - Create an applicationset manifest
 - Test with a pull request
 - Close the pull request
 
-### Step by step instructions
+### Step-by-step instructions
 
 <details>
 <summary>More Details</summary>
 
-#### Create a github token
+#### Create a GitHub token
 
-- Go to your github account settings and [create a new token](https://github.com/settings/tokens?type=beta) with the following permissions:
+- Go to your GitHub account settings and [create a new token](https://github.com/settings/tokens?type=beta) with the following permissions:
 
 ![github token permissions](img/github-token-permissions.png)
 
@@ -80,12 +80,12 @@ spec:
       github:
         # The GitHub organization or user.
         owner: <YOUR GITHUB USERNAME> #e.g. eficode-academy
-        # The Github repository
+        # The GitHub repository
         repo: <YOUR GIT REPO> #Just the repository name e.g. argocd-katas. Not your entire URL
-        tokenRef: # your github token
-          secretName: student-<NUMBER>-github-token # the name of the secret that contains your github token
-          key: token # the key in the secret that contains your github token
-        # Labels is used to filter the PRs that you want to target. (optional)
+        tokenRef: # your GitHub token
+          secretName: student-<NUMBER>-github-token # the name of the secret that contains your GitHub token
+          key: token # the key in the secret that contains your GitHub token
+        # Labels are used to filter the PRs that you want to target. (optional)
         labels:
         - enhancement
       requeueAfterSeconds: 60
@@ -119,7 +119,7 @@ spec:
           selfHeal: true
 ```
 
-- take the contents of the file, and paste it into a file in your workstation. The file could be named ´appset.yaml´.
+- Copy the contents of the file and paste it into a file in your workstation. The file could be named ´appset.yaml´.
 - edit the file and replace
   - `<YOUR GITHUB USERNAME>` with your github username
   - `<YOUR GIT REPO>` with your git repo
@@ -212,7 +212,7 @@ Events:                    <none>
 
 - Create a pull request in your git repo. The change does not matter at this time, since we are not using the source code in the pull request. 💡 The name of your branch needs to have all lowercase characters, otherwise it will not work.
 
-- Remember to set the label `enhancement` on the pull request. The label does not exist, so create it in the Github UI.
+- Remember to set the label `enhancement` on the pull request. The label does not exist, so create it in the GitHub UI.
 
 - Check that an application has been created in ArgoCD
 
@@ -234,13 +234,13 @@ kubectl get ingress -n <YOUR NAMESPACE>
 
 - Access the application in your browser (remember to add https:// in front of the hostname)
 
-You should see something like the follwing:
+You should see something like the following:
 
 ![the todo application](img/todo-app.png)
 
 #### Close the pull request
 
-- now close the pull request, and see that the application is deleted from ArgoCD
+- Now, close the pull request, and see that the application is deleted from ArgoCD
 
 ```bash
 kubectl get applications -n argocd

argocd-and-helm.md

@@ -1,4 +1,4 @@
-# Exercise: Deploying helm charts with Bitnami
+# Exercise: Deploying Helm charts with Bitnami
 
 ## Learning Goals
 
@@ -27,7 +27,7 @@ spec:
   destination:
     # The namespace the application should be deployed to.
     namespace: student-X
-    # Specify the name of the destination cluster, either name or server url.
+    # Specify the name of the destination cluster, either name or server URL.
     name: in-cluster
 
   # Define the synchronization policy for the Application.
@@ -38,7 +38,7 @@ spec:
   sources:
     # Specify the repository URL for the Helm chart.
     - repoURL: 'https://charts.bitnami.com/bitnami'
-      # Specify the target revision of the helm repository.
+      # Specify the target revision of the Helm repository.
       targetRevision: 12.4.0
       # Specify the name of the Helm chart as "Jenkins".
       chart: jenkins
@@ -64,12 +64,12 @@ spec:
 
 In this exercise, you will:
 
-- Deploy Jenkins in the ArgoCD UI using Bitnami Helm chart.
+- Deploy Jenkins in the ArgoCD UI using the Bitnami Helm chart.
 - Change the source of the deployment file.
 - Write a multi-source deployment file.
 - Change the values in the deployment file for automatic changes to the Jenkins app.
 
-### Step by Step Instructions
+### Step-by-Step Instructions
 
 <details>
 <summary>More Details</summary>
@@ -111,7 +111,7 @@ We will change the values of the Jenkins deployment by using a values file. This
 
 - Look at the `values.yaml` file in the `jenkins` directory. You can see that the `service.type` is set to `NodePort`, and two other values.
 - Now find the manifest in the ArgoCD UI by clicking on `app details`.
-- Change your manifest in ArgoCD in to use the `values.yaml` file by changing `source` to `sources` like the following:
+- Change your manifest in ArgoCD to use the `values.yaml` file by changing `source` to `sources` like the following:
 
 ``` yaml
 project: default
@@ -132,7 +132,7 @@ sources:
     ref: values
 ```
 
-💡 Remember to add your own repo to the file as well, as seen on the bottom. Pay attention to formatting.
+💡 Remember to add your repo to the file as well, as seen at the bottom. Pay attention to formatting.
 
 - Click save.
 

intro.md

@@ -31,7 +31,7 @@ In this exercise, you will:
 - **Refresh**: This action updates the live view in ArgoCD with the current state of the cluster and the state of the git repo. It does not change any resources in the cluster.
 - **Sync**: This action deploys the desired state from the Git repository to the cluster. If there are differences between the Git repo and the cluster, Sync will make the necessary changes to align them.
 
-### Step by Step Instructions
+### Step-by-Step Instructions
 
 <details>
 <summary>More Details</summary>
@@ -148,4 +148,4 @@ postgres-7bc8b45445-kshd8   1/1     Running   1          20h
 
 ### Cleanup
 
-Go ahead and delete the app in the ArgoCD UI. We will add it later as a true GitOps application
+Go ahead and delete the app in the ArgoCD UI. We will add it later as a true GitOps application.

projects.md

@@ -2,15 +2,15 @@
 
 ## Learning Goals
 
-- Introduction to the appproject manifest
-- Examine the restrictions you can make with the appprojects
+- Introduction to the app project manifest
+- Examine the restrictions you can make with the app projects
 
 ## Introduction
 
-Argo CD `projects` logically group applications for multiple teams, providing deployment restrictions to things like source repos, destination clusters/namespaces, resource definitions etc.
-The default project that comes baked in to ArgoCD allows unrestricted deployments.
+Argo CD `projects` logically group applications for multiple teams, providing deployment restrictions to things like source repos, destination clusters/namespaces, resource definitions, etc.
+The default project that comes baked into ArgoCD allows unrestricted deployments.
 New projects should be created for team-specific access levels, managing source repos, destinations, and Kubernetes resource kinds.
-Projects can be created with either Argo CD cli or declaratively.
+Projects can be created with either Argo CD CLI or declaratively.
 
 An `AppProject` is a custom resource definition (CRD) that defines a project in Argo CD. An example of an `AppProject` is shown below:
 
@@ -36,12 +36,12 @@ We are going to try out restrictions with the `appproject` kind. We will apply a
 
 ### Overview
 
-- create a project manifest
-- apply the project manifest
-- apply the application manifest that violates the restrictions
-- choose selective sync to partially sync the application
+- Create a project manifest
+- Apply the project manifest
+- Apply the application manifest that violates the restrictions
+- Choose selective sync to partially sync the application
 
-### Step by step instructions
+### Step-by-step instructions
 
 #### Create a project manifest
 
@@ -69,7 +69,7 @@ spec:
 
 It is a simple project manifest that restricts the deployment to a specific namespace and restricts the deployment of `Role` resources.
 
-- change the `name`, `spec.description` and `spec.destinations.namespace` fields to your student number
+- Change the `name`, `spec.description`, and `spec.destinations.namespace` fields to your student number
 
 #### Apply the project manifest
 
@@ -96,7 +96,7 @@ Go to the ArgoCD UI and see the project from there as well.
 
 - Click on `Settings` -> `Projects` and you should see the project there
 - Click on the project and see the details. Here you can see the different options that can be set for the project.
-- Verify that the description reflects your student number as well, e.g `a project for student-0 to play with`
+- Verify that the description reflects your student number as well, e.g, `a project for student-0 to play with`
 
 #### Apply the application manifest that violates the restrictions
 
@@ -140,10 +140,10 @@ The project restricts the deployment of `Role` resources, so the application wil
 ### Optional: Create an application outside your namespace
 
 If time permits, try to create an application that is deployed to a namespace that is not allowed by the project.  
-> **NOTE:** Don't do this by simply manipulating the destination of the application you just applied as that will
-> potentially interfere with the other students exercises.
+> **NOTE:** Don't do this by simply manipulating the destination of the application you just applied, as that will
+> potentially interfere with the other students' exercises.
 
-What are the differences in the error messages, compared to the previous application?
+What are the differences in the error messages compared to the previous application?
 
 ### Clean up
 

sealed-secrets.md

@@ -1,8 +1,8 @@
 # Sealed Secrets
 
 * Make a new application manifest for the k8s raw manifest
-* take the k8s manifest quotes flask
-* look at the postgres secret
-* seal the secret with kubeseal
+* Take the k8s manifest quotes flask
+* Look at the postgres secret
+* Seal the secret with kubeseal
 * Apply the new sealed secret (add to your repo and push it to see that Argo fetches it)
 * See that everything still works