Skip to content

[text-auditor] Fix clear typos in security detection rule description (recieve/use) #19314

@github-actions

Description

@github-actions

Text Improvements

The following user-facing text issues were found in the repository. Each is a low-effort fix.

1. Typo family: recievereceive in Security rule descriptions

File: packages/security_detection_engine/kibana/security_rule/3df49ff6-985d-11ef-88a1-f661ea17fbcd_8.json (line 6)
Current text: ...subscribe to recieve topic messages...
Suggested fix: ...subscribe to receive topic messages...
Why: Clear spelling error in user-facing rule description.

File: packages/security_detection_engine/kibana/security_rule/3df49ff6-985d-11ef-88a1-f661ea17fbcd_9.json (line 6)
Current text: ...subscribe to recieve topic messages...
Suggested fix: ...subscribe to receive topic messages...
Why: Clear spelling error in user-facing rule description.

File: packages/security_detection_engine/kibana/security_rule/3df49ff6-985d-11ef-88a1-f661ea17fbcd_10.json (line 6)
Current text: ...subscribe to recieve topic messages...
Suggested fix: ...subscribe to receive topic messages...
Why: Clear spelling error in user-facing rule description.

2. Grammar typo in the same rule family

File: packages/security_detection_engine/kibana/security_rule/3df49ff6-985d-11ef-88a1-f661ea17fbcd_8.json (line 6)
Current text: Identifies when a use subscribes to an SNS topic...
Suggested fix: Identifies when a user subscribes to an SNS topic...
Why: Clear grammatical/wording error (use instead of user) in user-facing description text.

Suggested Actions

  • Replace recieve with receive in all three affected rule JSON files.
  • Replace a use subscribes with a user subscribes in _8.json.
  • Regenerate/revalidate any derived package docs if these rule descriptions are rendered elsewhere.

What is this? | From workflow: Text Auditor

Give us feedback! React with 🚀 if perfect, 👍 if helpful, 👎 if not.

  • expires on Jun 8, 2026, 12:16 PM UTC

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions