diff --git a/content/blog/2024-11-07-clustergroup-sequencing.adoc b/content/blog/2024-11-07-clustergroup-sequencing.adoc
index 037e5bb93..6ed24345a 100644
--- a/content/blog/2024-11-07-clustergroup-sequencing.adoc
+++ b/content/blog/2024-11-07-clustergroup-sequencing.adoc
@@ -46,7 +46,7 @@ Within the framework, we support resource hooks in three ways:
 3. Exposing a new top-level clusterGroup object, extraObjects, that allows users full control of creating their own
 resource hooks.
 
-These features are available in version 0.9.8 and later of the Validated Patterns clustergroup chart.
+These features are available in version 0.9.9 and later of the Validated Patterns clustergroup chart.
 
 == Race Conditions: The Problem
 
@@ -81,11 +81,11 @@ apply resources in. The mechanism is described in the ArgoCD upstream docs https
 resources in the numerically next sync-wave are synced. This mechanism gives us a way of having ArgocD help us enforce
 order with objects that it manages.
 
-== Solution 1: Sync-Waves for Subscriptions in clusterGroup
+== Solution 1: Sync-Waves for Subscriptions (and/or Applications) in clusterGroup
 
-The Validated Patterns framework now allows Kubernetes https://kubernetes.io/docs/concepts/overview/working-with-objects/annotations/[annotations] to be added directly to subscription objects in the clusterGroup. ArgoCD uses annotations
-for Resource Hooks. The clustergoup chart now passes any annotations attached to subscriptions through to the
-subscription object(s) that the clustergroup chart creates. For example:
+The Validated Patterns framework now allows Kubernetes https://kubernetes.io/docs/concepts/overview/working-with-objects/annotations/[annotations] to be added directly to subscription objects and application objects in the clusterGroup.
+ArgoCD uses annotations for Resource Hooks. The clustergoup chart now passes any annotations attached to subscriptions
+through to the subscription object(s) that the clustergroup chart creates. For example:
 
 [source,yaml]
 ----
@@ -150,6 +150,9 @@ In the case of this particular issue, it was not enough. But because all sequenc
 sync-wave annotations, adding the annotation to the subscription object will be necessary for using the other
 solutions.
 
+The sequencing of applications would work the same way, with the same format for adding annotations to the application
+stanzas in the clustergroup.
+
 == Solution 2: The `sequenceJob` attribute for Subscriptions in clusterGroup
 
 In this situation, we have a subscription that installs an operator, but it is not enough for just the subscriptions