Merge branch 'main' of https://github.com/validatedpatterns/workshop

Author: day0hero

documentation/modules/ROOT/pages/consumingPatterns.adoc

@@ -27,20 +27,20 @@ image::consuming-vpWorkflow-hub.png[Hub Cluster]
 image::consuming-vpWorkflow-managedCluster.png[Managed Cluster]
 
 1. When a managed cluster is joined to {rhacm} it needs to have a clusterGroup label applied to it for the correct policies and applications to be deployed.
-2. {rhacm} will confirm the cluster is managed then deploy a rhacm agent 
+2. {rhacm} will confirm the cluster is managed then deploy a rhacm agent
 3. A placement policy is then deployed to the managed cluster which installs an instances of {rh-gitops}
 4. The managed cluster's instance of ArgoCD will then deploy the resources declared in `values-clustergroup.yaml`
 
 > IMPORTANT: Deploying the pattern through the OpenShift Console or via `pattern.sh` will deploy the patterns operator.
 
-=== Element Layering 
+=== Element Layering
 [#layering]
 
 The base component of every Validated Pattern is `common` - which is a link:https://github.com/validatedpatterns/common[Github Repo]
 
 image::consuming-common.png[common]
 
-Without further configuration, common is acutally quite boring. So let's add another layer! 
+Without further configuration, common is actually quite boring. So let's add another layer!
 
 Your specific industry or use-case is layered into the framework and utilizes the underlying common. In this example the solution includes a bespoke application, cloud-native cluster storage, {rhacs}, and an enterprise container registry. The framework will deploy and configure these components through Helm charts, kustomize manifests or Ansible if necessary.
 
@@ -59,6 +59,6 @@ image::consuming-common-solution-layering-modular.png[]
 [#multiArgos]
 == Multiple ArgoCDs
 
-You may be asking yourself ... 
+You may be asking yourself ...
 
 image::consuming-multipleArgos.png[]

documentation/modules/ROOT/pages/landscape.adoc

@@ -7,7 +7,7 @@ include::main@vp-workshop:ROOT:partial$topicHeader.adoc[]
 * What Validated Patterns are available
 ** What business problems are being addressed?
 ** Whether VPs are only applicable for the vertical industry the demo was created to show
-** How are they presented to custoemrs
+** How are they presented to customers
 * Working with Partners
 
 == Available Validated Patterns
@@ -23,7 +23,7 @@ As of July 2024 we can see that there has been a significant uptick in activity.
 image::landscape-july24.png[]
 
 == Validated Patterns WebSite
-The easiest and fastest way to find out what Validated Patterns are available and their availability is to check out the Validated Patterns webiste. 
+The easiest and fastest way to find out what Validated Patterns are available and their availability is to check out the Validated Patterns website.
 
 [#website]
 
@@ -37,5 +37,4 @@ The Patterns are also hosted in link:https://github.com/validatedpatterns/reposi
 // Find out our youtube channel link
 
 //[#OpenShiftCommons]
-// Find out commons-sig info
-
+// Find out commons-sig info

documentation/modules/ROOT/pages/partners.adoc

@@ -2,7 +2,7 @@
 
 include::_attributes.adoc[]
 
-Partners have taken notice of what Validated Patterns can bring to their organizations. In turn, they have had focused development cycles to deploy their product/features using the Validated Pattners framework. In the following sections we will discuss how a few of our partners have taken advantage of the Validated Patterns framework.
+Partners have taken notice of what Validated Patterns can bring to their organizations. In turn, they have had focused development cycles to deploy their product/features using the Validated Patterns framework. In the following sections we will discuss how a few of our partners have taken advantage of the Validated Patterns framework.
 
 == Intel
 [#intel]

documentation/modules/ROOT/pages/patterns.adoc

@@ -25,7 +25,7 @@ image::Linux-Penguin-Evolution-1.png[evolution]
 
 == Business Goals
 
-Every organization is facing the need to transform itself into a digital business. It's part of an evolution to help **accelerate innovation** by making application development faster - fueled with data insights, and enabled through technologies like containers, kubernetes and artifical intelligence/machine learning.
+Every organization is facing the need to transform itself into a digital business. It's part of an evolution to help **accelerate innovation** by making application development faster - fueled with data insights, and enabled through technologies like containers, kubernetes and artificial intelligence/machine learning.
 
 In order to be successful, they know they must also look at how to be more **operationally agile** and **efficient** in order to quickly meet business needs. Hybrid-Cloud computing coupled with these new technologies is helping create new opportunities to achieve these goals.
 
@@ -74,6 +74,6 @@ image::introduction-pattern-values.png[]
 
 * Customers - get going faster, reduce risk, time to value
 * Sales - don't spend time architecting, they have a tested use ccase for a base deployment. Though messaged for a specific vertical in some cases, they can be used across other verticals. 
-* Partners - free use of a defined architecutre that you can build a solution on top of. All the value to accelerate sales/deployments.
+* Partners - free use of a defined architecture that you can build a solution on top of. All the value to accelerate sales/deployments.
 ** Can also be used as a way to promote your product (HashiCorp)
-* GSIs or Consulting Services - predefined architectures, ready to deploy with minimal modifications. They can trust in the use-case as it is maintained across production version updates.
+* GSIs or Consulting Services - predefined architectures, ready to deploy with minimal modifications. They can trust in the use-case as it is maintained across production version updates.

documentation/modules/ROOT/pages/selfContained.adoc

@@ -25,7 +25,7 @@ Where or would I add them to the pattern?
 |===
 |**Resource Type**|**Placement**
 | `kubernetes manifests (.yaml)`
-| They can either be coverted to a Helm chart, or the raw manifests can be placed in a directory under `charts/`
+| They can either be converted to a Helm chart, or the raw manifests can be placed in a directory under `charts/`
 |`kustomize manifests`
 | Kustomize manifests can be placed in a directory under `charts/` or another path (e.g. `kustomize`) could be used
 |`Ansible`

documentation/modules/ROOT/pages/tiers.adoc

@@ -6,7 +6,7 @@ include::main@vp-workshop:ROOT:partial$topicHeader.adoc[]
 
 * What are the Validated Pattern Maintenance Tiers?
 ** What's the difference between the tiers?
-* Additional information on mainteance tiers and the pattern support policy
+* Additional information on maintenance tiers and the pattern support policy
 
 == Tiers
 [#about]
@@ -38,7 +38,7 @@ a| * must include a standardized architecture diagram using (or conforming to) t
 
 |`Maintained`
 a| * functional on all currently supported/extended update support (EUS) versions of OpenShift
-  * must fix breakage in a timely mannger
+  * must fix breakage in a timely manner
   * must document their support policy
 | https://validatedpatterns.io/learn/maintained