chore: typo sweep (succesful, occured)

[SAY-5]

Two single-character typo fixes in comments/prose:

• libbeat/processors/dissect/processor_test.go:287 — t.Run subtest name succesful -> successful
• docs/reference/metricbeat/exported-fields-oracle.md:131 — oracle metricset parse description occured -> occurred

No functional change.

[github-actions]

🤖 GitHub comments

Just comment with:

• run docs-build : Re-trigger the docs validation. (use unformatted text in the comment!)
• /test : Run the Buildkite pipeline.

[mergify]

This pull request does not have a backport label.
If this is a bug or security fix, could you label this PR @SAY-5? 🙏.
For such, you'll need to label your PR with:

• The upcoming major version of the Elastic Stack
• The upcoming minor version of the Elastic Stack (if you're not pushing a breaking change)

To fixup this pull request, you need to add the backport labels for the needed
branches, such as:

• backport-8./d is the label to automatically backport to the 8./d branch. /d is the digit
• backport-active-all is the label that automatically backports to all active branches.
• backport-active-8 is the label that automatically backports to all active minor branches for the 8 major.
• backport-active-9 is the label that automatically backports to all active minor branches for the 9 major.

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro Plus

Run ID: 42e7ffaf-0402-4a51-aa66-186263f07bfe

📥 Commits

Reviewing files that changed from the base of the PR and between 8b7236f and b71069a.

📒 Files selected for processing (2)

• docs/reference/metricbeat/exported-fields-oracle.md
• libbeat/processors/dissect/processor_test.go

---

📝 Walkthrough

Walkthrough

This pull request contains two spelling corrections across documentation and test files. In the Oracle metricbeat exported fields documentation, the word "occured" is corrected to "occurred" in a field description. In the dissect processor test file, a test sub-case name string is corrected from "succesful" to "successful". Both changes are documentation and test metadata corrections with no functional code modifications.

🚥 Pre-merge checks | ✅ 2

✅ Passed checks (2 passed)

Check name	Status	Explanation
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests

• 🛠️ Update Documentation: Commit on current branch
• 🛠️ Update Documentation: Create PR

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[SAY-5]

The check / fragments jobs are failing on this PR because it's a pure comment / user-facing-string typo sweep (succesful→successful, occured→occurred) with no behaviour change. Could a maintainer apply whichever label corresponds to "skip changelog fragment" for docs-only touches, or advise which fragment template is appropriate here? Happy to commit the right fragment yaml directly if that's preferred.

[elasticmachine]

Pinging @elastic/elastic-agent-data-plane (Team:Elastic-Agent-Data-Plane)

[SAY-5]

Closing — typo-only PR. Multiple maintainers across the OSS ecosystem have flagged my recent typo-sweep PRs as AI-generated spam. Apologies for the noise.