From 19efa1787938e29b56a6f30de27187861a486aa2 Mon Sep 17 00:00:00 2001
From: Mikhail Vasin <12434833+mvasin@users.noreply.github.com>
Date: Thu, 12 Aug 2021 12:13:35 +0200
Subject: [PATCH 1/2] Fix typo

---
 README.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/README.md b/README.md
index 0127a583b8..76d09c160d 100644
--- a/README.md
+++ b/README.md
@@ -395,7 +395,7 @@ as a remote image destination:
 ### Caching
 
 #### Caching Layers
-kaniko can cache layers created by `RUN` and `Copy` (configured by flag `--cache-copy-layers`) commands in a remote repository.
+kaniko can cache layers created by `RUN` and `COPY` (configured by flag `--cache-copy-layers`) commands in a remote repository.
 Before executing a command, kaniko checks the cache for the layer.
 If it exists, kaniko will pull and extract the cached layer instead of executing the command.
 If not, kaniko will execute the command and then push the newly created layer to the cache.

From 5bdf7b5d878be20fb7f445232b2bc6d125f3eeba Mon Sep 17 00:00:00 2001
From: Mikhail Vasin <12434833+mvasin@users.noreply.github.com>
Date: Thu, 12 Aug 2021 12:57:48 +0200
Subject: [PATCH 2/2] Another typo

---
 README.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/README.md b/README.md
index 76d09c160d..fe2c6fa826 100644
--- a/README.md
+++ b/README.md
@@ -471,7 +471,7 @@ If you have enabled Workload Indentity on your GKE cluster then you can use the
 
 Learn more on how to [enable](https://cloud.google.com/kubernetes-engine/docs/how-to/workload-identity#enable_on_cluster) and [migrate existing apps](https://cloud.google.com/kubernetes-engine/docs/how-to/workload-identity#migrate_applications_to) to workload identity.
 
-To authenticate using workload identity you need to run the kaniko pod using the Kubernetes Service Account (KSA) bound to Google Service Account (GSA) which as `Storage.Admin` permissions to push images to Google Container registry.
+To authenticate using workload identity you need to run the kaniko pod using the Kubernetes Service Account (KSA) bound to Google Service Account (GSA) which has `Storage.Admin` permissions to push images to Google Container registry.
 
 Please follow the detailed steps [here](https://cloud.google.com/kubernetes-engine/docs/how-to/workload-identity#authenticating_to) to create a Kubernetes Service Account, Google Service Account and create an IAM policy binding between the two to allow the Kubernetes Service account to act as the Google service account.