Merge pull request redhat-scholars#1 from btison/btison-patch-1

Fixed typo
bbethell-1 · May 22, 2023 · f5284a5 · f5284a5
2 parents c5c15c9 + 6afd6f2
commit f5284a5
Showing 1 changed file with 2 additions and 2 deletions.
diff --git a/docs/modules/m3-managing-namespaces/pages/kustomize.adoc b/docs/modules/m3-managing-namespaces/pages/kustomize.adoc
@@ -6,7 +6,7 @@
 
 https://kubernetes.io/docs/concepts/overview/working-with-objects/namespaces/[Namespaces] can be used to provide isolation, and divide resources between different teams within a Kubernetes cluster. For example, two teams could each be given a Namespace within a cluster to deploy their applications. Each Namespace can have a set amount of CPU and memory allocated to it depending on the requirements of the software each team is building and deploying. The members of each team might only have access to their own Namespace and no additional namespaces.
 
-In this section, you'll create two Namespaces based on a shared template. Of course you'll want each Namespace to have a unique name, and custom https://kubernetes.io/docs/concepts/policy/resource-quotas/[ResourceQuotas] and https://kubernetes.io/docs/concepts/policy/limit-range/[LimitRanges] depending on the workloads being deployed within them. You'll learn how to extend and patch YAML files using https://kustomize.io/[Kustomise]. Argo CD supports both Kustomize and Helm for scenarios where templating YAML is necessary.
+In this section, you'll create two Namespaces based on a shared template. Of course you'll want each Namespace to have a unique name, and custom https://kubernetes.io/docs/concepts/policy/resource-quotas/[ResourceQuotas] and https://kubernetes.io/docs/concepts/policy/limit-range/[LimitRanges] depending on the workloads being deployed within them. You'll learn how to extend and patch YAML files using https://kustomize.io/[Kustomize]. Argo CD supports both Kustomize and Helm for scenarios where templating YAML is necessary.
 
 image::ex4.argo-kustomize-example.png[]
 
@@ -94,4 +94,4 @@ image::ex4.github-ide-application-cr.png[]
 +
 image::ex4.github-ide-commit.png[]
 
-You now have two Namespaces ready to be synchronised and managed by Argo CD on your OpenShift cluster. You also have the Application CR required by Argo CD.
+You now have two Namespaces ready to be synchronised and managed by Argo CD on your OpenShift cluster. You also have the Application CR required by Argo CD.