use proper Gherkin syntax

elastic · Feb 12, 2024 · d5db430 · d5db430
1 parent c0f9f23
commit d5db430
Showing 1 changed file with 2 additions and 2 deletions.
diff --git a/...esting/test_plans/detection_response/prebuilt_rules/installation_and_upgrade.md b/...esting/test_plans/detection_response/prebuilt_rules/installation_and_upgrade.md
@@ -967,7 +967,7 @@ When a user upgrades the rule
 Then the rule bound data should be preserved
 ```
 
-CASEs: generated alerts, exception lists (rule exception list, shared exception list, endpoint exception list), timeline reference, actions, enabled state, execution results and execution events.
+Examples: generated alerts, exception lists (rule exception list, shared exception list, endpoint exception list), timeline reference, actions, enabled state, execution results and execution events.
 
 #### **Scenario: Rule bound data is preserved after upgrading a rule to a newer version with a different rule type**
 
@@ -981,7 +981,7 @@ When a user upgrades the rule
 Then the rule bound data should be preserved
 ```
 
-CASEs: generated alerts, exception lists (rule exception list, shared exception list, endpoint exception list), timeline reference, actions, enabled state, execution results and execution events.
+Examples: generated alerts, exception lists (rule exception list, shared exception list, endpoint exception list), timeline reference, actions, enabled state, execution results and execution events.
 
 ### Rule upgrade workflow: misc cases