[text-auditor] Batch fix clear untracked typos in CI runtime messages and CEF outcome text

Search for the eight listed \bsucess\b occurrences in the CEF field YAML and README files under packages/cef and packages/cyberark_pta. Update only those documented outcome descriptions from "sucess" to "success", then rerun the search to confirm no in-scope typo remains; the Buildkite script and backport-message items are already checked off.

Text Improvements

The following user-facing text issues were verified in-repo and appear untracked by current open [text-auditor] issues. Each is a low-effort correction.

1. changset typo in CI/runtime script output (4 occurrences)

Why: Clear spelling error in user-visible script messages.

• File: .buildkite/scripts/trigger_integrations_in_parallel.sh (line 30)
  Current text: Missing "from" changset
  Suggested fix: Missing "from" changeset
• File: .buildkite/scripts/trigger_integrations_in_parallel.sh (line 35)
  Current text: Missing "to" changset
  Suggested fix: Missing "to" changeset
• File: .buildkite/scripts/test_integrations_with_serverless.sh (line 67)
  Current text: Missing "from" changset
  Suggested fix: Missing "from" changeset
• File: .buildkite/scripts/test_integrations_with_serverless.sh (line 72)
  Current text: Missing "to" changset
  Suggested fix: Missing "to" changeset

Completeness search used: \bchangset\b (4 verified in-scope occurrences)

2. Grammar error in commit validation message

Why: Clear grammatical error in a user-facing annotated error.

• File: .buildkite/scripts/backport_branch.sh (line 287)
  Current text: The entered commit hasn't found in the **\$\{SOURCE_BRANCH}** branch
  Suggested fix: The entered commit was not found in the **\$\{SOURCE_BRANCH}** branch

Completeness search used: hasn't found (1 verified in-scope occurrence)

3. sucess typo family in CEF outcome descriptions (8 occurrences)

Why: Clear typo in user-facing field descriptions and corresponding package docs.

• 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 419)
  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 427)
  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/docs/README.md (line 177)
  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/docs/README.md (line 185)
  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).

Completeness search used: \bsucess\b (8 verified in-scope occurrences)

Suggested Actions

• Replace changset with changeset in both Buildkite scripts.
• Update the backport error message grammar to was not found.
• Replace sucess with success across all listed CEF field/docs occurrences.

---

What is this? | From workflow: Text Auditor

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

• expires on May 20, 2026, 11:02 AM UTC