From c7e3d8e4b40e1fa59fa1004851efc5b2c8bc2bad Mon Sep 17 00:00:00 2001
From: Bahram Rushenas <bahram@outlook.com>
Date: Mon, 29 Aug 2022 09:30:18 -0700
Subject: [PATCH] Fixed spelling errors

---
 .vscode/cspell.json       | 3 +++
 shared-services/README.md | 2 +-
 2 files changed, 4 insertions(+), 1 deletion(-)

diff --git a/.vscode/cspell.json b/.vscode/cspell.json
index c830771..ecaba65 100644
--- a/.vscode/cspell.json
+++ b/.vscode/cspell.json
@@ -16,6 +16,7 @@
         "argo",
         "aspnetapp",
         "aspnetsample",
+        "azureidentity",
         "AZURERBAC",
         "azurevote",
         "CARML",
@@ -40,6 +41,7 @@
         "keyvaults",
         "kubeconfig",
         "kubectl",
+        "kube",
         "Kubernetes",
         "Kured",
         "kustomization",
@@ -55,6 +57,7 @@
         "podmi",
         "refs",
         "roadmap",
+        "secretproviderclass",
         "subcharts",
         "SUBSCRIPTIONID",
         "TENANTID",
diff --git a/shared-services/README.md b/shared-services/README.md
index a23fa54..1c7cdf8 100644
--- a/shared-services/README.md
+++ b/shared-services/README.md
@@ -28,7 +28,7 @@ The **cluster** directory contains the configuration that applies to entire clus
 
 Typically, your bootstrapping repository wouldn't be a public facing repository like this one, but instead a private GitHub or Azure DevOps repo. The Flux operator deployed with the cluster supports private git repositories as your bootstrapping source. In addition to requiring network line of sight to the repository from your cluster's nodes, you'll also need to ensure that you've provided the necessary credentials. This can come, typically, in the form of certificate based SSH or personal access tokens (PAT), both ideally scoped as read-only to the repo with no additional permissions.
 
-To configure the setting for the GitHub repo that you want flux to pull from, update the parameter file for your cluster rior :
+To configure the settings for the GitHub repo that you want flux to pull from, update the parameter file for your cluster prior to deploying it:
 * If you are using terraform modify the [`flux.yaml`](../../IaC/terraform/configuration/workloads/flux.tfvars) file.
 * If you are using bicep modify the [`cluster.parameters.json`](../../IaC/bicep/rg-spoke/cluster.parameters.json) file.