[text-auditor] Batch fix clear untracked typo families and GitHub terminology in user-facing text

## Text Improvements

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

### 1. `Collet` typo in Wiz data stream title

**File:** `packages/wiz/data_stream/cloud_configuration_finding/manifest.yml` (line 1)
**Current text:** `title: Collet Cloud Configuration Finding logs from Wiz.`
**Suggested fix:** `title: Collect Cloud Configuration Finding logs from Wiz.`
**Why:** Clear spelling error.

### 2. `Deprectad` typo family in Windows ETW user-facing descriptions

**File:** `packages/windows_etw/fields/winlog.yml` (line 10)
**Current text:** `... Deprectad in favor of \`winlog.activity_id\` from 8.14.0 ...`
**Suggested fix:** `... Deprecated in favor of \`winlog.activity_id\` from 8.14.0 ...`
**Why:** Clear spelling error.

**File:** `packages/windows_etw/docs/README.md` (line 80)
**Current text:** `... Deprectad in favor of \`winlog.activity_id\` from 8.14.0 ...`
**Suggested fix:** `... Deprecated in favor of \`winlog.activity_id\` from 8.14.0 ...`
**Why:** Same typo family in user-facing docs.

### 3. `Dahsboard` typo in Proofpoint screenshot title

**File:** `packages/proofpoint_itm/manifest.yml` (line 16)
**Current text:** `title: Proofpoint ITM Report Dahsboard`
**Suggested fix:** `title: Proofpoint ITM Report Dashboard`
**Why:** Clear spelling error.

### 4. `Vulnerabilty` typo in Qualys WAS data stream title

**File:** `packages/qualys_was/data_stream/vulnerability/manifest.yml` (line 1)
**Current text:** `title: Collects Web Application Vulnerabilty Findings from Qualys WAS platform.`
**Suggested fix:** `title: Collects Web Application Vulnerability Findings from Qualys WAS platform.`
**Why:** Clear spelling error.

### 5. `cpacity` typo in Oracle OTel dashboard title

**File:** `packages/oracle_otel/manifest.yml` (line 40)
**Current text:** `title: Oracle Transaction outcomes and storage cpacity details dashboard.`
**Suggested fix:** `title: Oracle Transaction outcomes and storage capacity details dashboard.`
**Why:** Clear spelling error.

### 6. `Github` terminology family in user-facing scripts and docs

Use the product name `GitHub` consistently in user-facing text.

**File:** `.buildkite/scripts/process_benchmarks.sh` (line 85)
**Current text:** `Benchmark report not posted to Github PR`
**Suggested fix:** `Benchmark report not posted to GitHub PR`

**File:** `.buildkite/scripts/trigger_integrations_in_parallel.sh` (line 45)
**Current text:** `--- Stack version set from Github comment`
**Suggested fix:** `--- Stack version set from GitHub comment`

**File:** `.buildkite/scripts/trigger_integrations_in_parallel.sh` (line 48)
**Current text:** `Use Elastic stack version from Github comment: \$\{STACK_VERSION}`
**Suggested fix:** `Use Elastic stack version from GitHub comment: \$\{STACK_VERSION}`

**File:** `docs/extend/manifest-spec.md` (line 410)
**Current text:** `description: Github team name of the package maintainer.`
**Suggested fix:** `description: GitHub team name of the package maintainer.`

**File:** `docs/extend/elastic-package.md` (line 257)
**Current text:** `#### Benchmark report for Github`
**Suggested fix:** `#### Benchmark report for GitHub`

**File:** `docs/extend/elastic-package.md` (line 262)
**Current text:** `It is formatted as a Markdown Github comment ...`
**Suggested fix:** `It is formatted as a Markdown GitHub comment ...`

**File:** `docs/extend/tips-for-building.md` (line 40)
**Current text:** `Set the proper package owner (either Github team or personal account)`
**Suggested fix:** `Set the proper package owner (either GitHub team or personal account)`

**File:** `docs/extend/tips-for-building.md` (line 77)
**Current text:** `? Github owner: (elastic/integrations)`
**Suggested fix:** `? GitHub owner: (elastic/integrations)`

**File:** `docs/extend/quick-start.md` (line 59)
**Current text:** `* Github owner: \`(your github name)\``
**Suggested fix:** `* GitHub owner: \`\``

**File:** `packages/nvidia_gpu/docs/README.md` (line 46)
**Current text:** `See more in the [DCGM Github Repository](...)`
**Suggested fix:** `See more in the [DCGM GitHub Repository](...)`

**File:** `packages/ti_abusech/docs/README.md` (line 43)
**Current text:** `... authentication provider: Google, Github, X, or LinkedIn.`
**Suggested fix:** `... authentication provider: Google, GitHub, X, or LinkedIn.`

**Why:** Unambiguous terminology inconsistency for a product name in user-facing text.

## Suggested Actions

- [ ] Replace `Collet` with `Collect` in Wiz cloud configuration finding title.
- [ ] Replace `Deprectad` with `Deprecated` in both Windows ETW field and docs text.
- [ ] Replace `Dahsboard` with `Dashboard` in Proofpoint ITM manifest screenshot title.
- [ ] Replace `Vulnerabilty` with `Vulnerability` in Qualys WAS vulnerability stream title.
- [ ] Replace `cpacity` with `capacity` in Oracle OTel manifest screenshot title.
- [ ] Standardize `Github` to `GitHub` across the listed user-facing scripts and documentation files.

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

Give us feedback! React with 🚀 if perfect, 👍 if helpful, 👎 if not.
> - [x] expires on Jun 1, 2026, 11:34 AM UTC