[text-auditor] Fix remaining `statup`/`went Event's` config-comment typos and `Malware familiy` field typos

## Text Improvements

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

### 1. Repeated Kubernetes config-comment typo/grammar pair

**Files:**
- `metricbeat/metricbeat.reference.yml` (line 635, line 637)
- `x-pack/metricbeat/metricbeat.reference.yml` (line 1086, line 1088)
- `metricbeat/module/kubernetes/_meta/config.reference.yml` (line 113, line 115)
- `metricbeat/module/kubernetes/_meta/config.yml` (line 75, line 77)
- `metricbeat/modules.d/kubernetes.yml.disabled` (line 78, line 80)

**Current text:**
- `# Skip events older than Metricbeat's statup time is enabled by default.`
- `# This setting is also useful went Event's timestamps are not populated properly.`

**Suggested fix:**
- `# Skipping events older than Metricbeat's startup time is enabled by default.`
- `# This setting is also useful when events' timestamps are not populated properly.`

**Why:** `statup` and `went` are clear typos, and `Event's` is incorrect possessive usage in user-facing configuration guidance.

### 2. Repeated threatintel field-description typo

**Files:**
- `x-pack/filebeat/module/threatintel/abusemalware/_meta/fields.yml` (line 14)
- `x-pack/filebeat/module/threatintel/malwarebazaar/_meta/fields.yml` (line 13)

**Current text:**
- `Malware familiy.`

**Suggested fix:**
- `Malware family.`

**Why:** `familiy` is an unambiguous spelling error in exported field-description source text.

## Suggested Actions

- [ ] Replace the two Kubernetes comment lines in all five listed files (`statup`/`went Event's`) with the corrected wording.
- [ ] Replace `Malware familiy.` with `Malware family.` in both listed threatintel `_meta/fields.yml` files.

## Completeness and duplicate check

- Completeness pass patterns used: `statup`, `went Event's timestamps`, `Malware familiy`.
- All verified in-scope source occurrences for these patterns are included above.
- Checked `/tmp/previous-findings.json` and current open `[text-auditor]` issues; no open issue was found for these specific families.

> [!NOTE]
>
> 🔒 Integrity filter blocked 22 items
>
> The following items were blocked because they don't meet the GitHub integrity level.
>
> - [#20300](https://github.com/elastic/beats/issues/20300) `search_issues`: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
> - [#10876](https://github.com/elastic/beats/issues/10876) `search_issues`: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
> - [#29511](https://github.com/elastic/beats/issues/29511) `search_issues`: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
> - [#47550](https://github.com/elastic/beats/issues/47550) `search_issues`: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
> - [#40386](https://github.com/elastic/beats/issues/40386) `search_issues`: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
> - [#36020](https://github.com/elastic/beats/issues/36020) `search_issues`: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
> - [#32401](https://github.com/elastic/beats/issues/32401) `search_issues`: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
> - [#18542](https://github.com/elastic/beats/issues/18542) `search_issues`: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
> - [#27903](https://github.com/elastic/beats/issues/27903) `search_issues`: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
> - [#23332](https://github.com/elastic/beats/issues/23332) `search_issues`: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
> - [#5390](https://github.com/elastic/beats/issues/5390) `search_issues`: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
> - [#16777](https://github.com/elastic/beats/issues/16777) `search_issues`: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
> - [#11834](https://github.com/elastic/beats/issues/11834) `search_issues`: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
> - [#3952](https://github.com/elastic/beats/issues/3952) `search_issues`: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
> - [#3465](https://github.com/elastic/beats/issues/3465) `search_issues`: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
> - [#7542](https://github.com/elastic/beats/issues/7542) `search_issues`: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
> - ... and 6 more items
>
> To allow these resources, lower `min-integrity` in your GitHub frontmatter:
>
> ```yaml
> tools:
> github:
> min-integrity: approved # merged | approved | unapproved | none
> ```
>
>

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

Give us feedback! React with 🚀 if perfect, 👍 if helpful, 👎 if not.
> - [x] expires on Jun 4, 2026, 2:28 PM UTC

Start by searching the listed Metricbeat Kubernetes configuration files and threatintel fields.yml files for `statup`, `went Event's`, and `Malware familiy`. Apply the exact wording changes in all seven files, then repeat those searches to verify no in-scope occurrences remain.

Written by the indexing model from the issue text.