[text-auditor] Fix `sucess` typo family in CEF/CyberArk user-facing descriptions

Start with the four source field definition files listed in packages/cef/data_stream/log/fields/fields.yml and packages/cyberark_pta/data_stream/events/fields/cef.yml, then inspect the matching tables in both packages' docs/README.md files. Confirm all eight listed user-facing occurrences use the correct spelling and that the source and rendered documentation remain consistent.

Text Improvements

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

1. Typo family: sucess → success in ArcSight outcome descriptions

Why: sucess is an unambiguous typo and appears repeatedly in user-facing field descriptions and rendered package docs.

Verified occurrences (completeness pass):

File: packages/cef/data_stream/log/fields/fields.yml (line 99)
Current text: Outcome of the event (e.g. sucess, failure, or attempt) (ArcSight).
Suggested fix: Outcome of the event (e.g. success, failure, or attempt) (ArcSight).

File: packages/cef/data_stream/log/fields/fields.yml (line 121)
Current text: Outcome of the event (e.g. sucess, failure, or attempt) (ArcSight).
Suggested fix: Outcome of the event (e.g. success, failure, or attempt) (ArcSight).

File: packages/cyberark_pta/data_stream/events/fields/cef.yml (line 154)
Current text: Outcome of the event (e.g. sucess, failure, or attempt) (ArcSight).
Suggested fix: Outcome of the event (e.g. success, failure, or attempt) (ArcSight).

File: packages/cyberark_pta/data_stream/events/fields/cef.yml (line 157)
Current text: Outcome of the event (e.g. sucess, failure, or attempt) (ArcSight).
Suggested fix: Outcome of the event (e.g. success, failure, or attempt) (ArcSight).

File: packages/cef/docs/README.md (line 418)
Current text: | cef.extensions.categoryOutcome | Outcome of the event (e.g. sucess, failure, or attempt) (ArcSight). | keyword |
Suggested fix: | cef.extensions.categoryOutcome | Outcome of the event (e.g. success, failure, or attempt) (ArcSight). | keyword |

File: packages/cef/docs/README.md (line 426)
Current text: | cef.extensions.destinationNtDomain | Outcome of the event (e.g. sucess, failure, or attempt) (ArcSight). | keyword |
Suggested fix: | cef.extensions.destinationNtDomain | Outcome of the event (e.g. success, failure, or attempt) (ArcSight). | keyword |

File: packages/cyberark_pta/docs/README.md (line 177)
Current text: | cef.extensions.categoryOutcome | Outcome of the event (e.g. sucess, failure, or attempt) (ArcSight). | keyword |
Suggested fix: | cef.extensions.categoryOutcome | Outcome of the event (e.g. success, failure, or attempt) (ArcSight). | keyword |

File: packages/cyberark_pta/docs/README.md (line 185)
Current text: | cef.extensions.destinationNtDomain | Outcome of the event (e.g. sucess, failure, or attempt) (ArcSight). | keyword |
Suggested fix: | cef.extensions.destinationNtDomain | Outcome of the event (e.g. success, failure, or attempt) (ArcSight). | keyword |

Suggested Actions

• Replace sucess with success in the 4 source field definition files listed above.
• Update the 4 mirrored docs table entries listed above to keep generated/readable docs consistent.

What is this? | From workflow: Text Auditor

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

• expires on Jun 19, 2026, 11:26 AM UTC