[text-auditor] Batch fix untracked typo families in manifest, pipeline descriptions, and docs

## Text Improvements

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

### 1. `exisiting` → `existing` in package manifest description

**File:** `packages/cisa_kevs/manifest.yml` (line 5)
**Current text:** `...track exisiting vulnerabilities that are known to be exploited in the wild.`
**Suggested fix:** `...track existing vulnerabilities that are known to be exploited in the wild.`
**Why:** Clear spelling error in integration manifest description.

### 2. `begining` → `beginning` in ingest pipeline processor descriptions (2 occurrences)

**File:** `packages/sentinel_one_cloud_funnel/data_stream/event/elasticsearch/ingest_pipeline/default.yml` (line 55)
**Current text:** `Script to remove quotes from begining and end from a field.`
**Suggested fix:** `Script to remove quotes from beginning and end from a field.`
**Why:** Clear spelling error in user-visible processor description.

**File:** `packages/infoblox_threat_defense/data_stream/event/elasticsearch/ingest_pipeline/default.yml` (line 82)
**Current text:** `Script to remove quotes from begining and end from message field.`
**Suggested fix:** `Script to remove quotes from beginning and end from message field.`
**Why:** Same spelling error in another user-visible processor description.

### 3. `seperator` → `separator` in changelog and pipeline description (2 occurrences)

**File:** `packages/apache_tomcat/changelog.yml` (line 9)
**Current text:** `Fix IP seperator regex for access logs`
**Suggested fix:** `Fix IP separator regex for access logs`
**Why:** Clear spelling error in user-facing changelog text.

**File:** `packages/vsphere/data_stream/log/elasticsearch/ingest_pipeline/login.yml` (line 153)
**Current text:** `...contains either , or . as a thousand seperator...`
**Suggested fix:** `...contains either , or . as a thousand separator...`
**Why:** Clear spelling error in processor description.

### 4. `succeded` → `succeeded` in Dataminr Pulse docs (2 occurrences)

**File:** `packages/dataminr_pulse/README.md` (line 239)
**Current text:** `If the iteration failed or succeded`
**Suggested fix:** `If the iteration failed or succeeded`
**Why:** Clear spelling error in user-facing field table.

**File:** `packages/dataminr_pulse/docs/README.md` (line 239)
**Current text:** `If the iteration failed or succeded`
**Suggested fix:** `If the iteration failed or succeeded`
**Why:** Same spelling error in duplicated package docs.

### 5. `succesfully` / `sour` typo pair in processor description

**File:** `packages/hpe_aruba_cx/data_stream/log/elasticsearch/ingest_pipeline/default.yml` (line 1943)
**Current text:** `...downloaded succesfully from a remote sour | image was downloaded succesfully from a local source...`
**Suggested fix:** `...downloaded successfully from a remote source | image was downloaded successfully from a local source...`
**Why:** Two clear spelling errors in one user-facing description.

## Suggested Actions

- [ ] Replace `exisiting` with `existing` in `packages/cisa_kevs/manifest.yml`.
- [ ] Replace `begining` with `beginning` in both listed ingest pipeline descriptions.
- [ ] Replace `seperator` with `separator` in both listed occurrences.
- [ ] Replace `succeded` with `succeeded` in both Dataminr Pulse README files.
- [ ] Replace `succesfully`/`sour` with `successfully`/`source` in the listed HPE Aruba CX processor description.

## Completeness Notes

The following exact-pattern searches were run repository-wide and all in-scope user-facing matches were included above:

- `\bexisiting\b`
- `\bbegining\b`
- `\bseperator\b`
- `\bsucceded\b`
- `\bsuccesfully\b|\bsour\b`

---
[What is this?](https://ela.st/github-ai-tools) | [From workflow: Text Auditor](https://github.com/elastic/integrations/actions/runs/25491107936)

Give us feedback! React with 🚀 if perfect, 👍 if helpful, 👎 if not.
> - [x] expires on May 14, 2026, 10:55 AM UTC