🌱 Clarify which ClusterExtension is being asserted in collision test

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>

Author: Per G. da Silva

test/e2e/features/update.feature

@@ -363,7 +363,7 @@ Feature: Update ClusterExtension
       """
     And ClusterExtension is rolled out
     And ClusterExtension is available
-    And ClusterExtension "${NAME}" owns1 ClusterObjectSet
+    And ClusterExtension "${NAME}" owns 1 ClusterObjectSet
     And the current ClusterExtension is tracked for cleanup
     # Apply a second ClusterExtension pointing to the same package and version
     When ClusterExtension is applied
@@ -385,6 +385,7 @@ Feature: Update ClusterExtension
               matchLabels:
                 "olm.operatorframework.io/metadata.name": ${CATALOG:test}
       """
+    # The conflicting ClusterExtension (${NAME}-dup, now tracked as ${NAME}) should be retrying
     Then ClusterExtension reports Progressing as True with Reason Retrying and Message includes:
       """
       revision object collisions
@@ -424,7 +425,7 @@ Feature: Update ClusterExtension
               matchLabels:
                 "olm.operatorframework.io/metadata.name": ${CATALOG:test}
       """
-    Then ClusterExtension "${NAME}" owns2 ClusterObjectSets
+    Then ClusterExtension "${NAME}" owns 2 ClusterObjectSets
     # The higher-revision COS (revision 2) should also collide, not take over resources
     And ClusterExtension reports Progressing as True with Reason Retrying and Message includes:
       """