[text-auditor] Batch fix clear user-facing typo families and one misleading reporter message

## Text Improvements

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

### 1. Typo family: `asyncronous` → `asynchronous`

**File:** `packages/falco/data_stream/alerts/fields/fields.yml` (line 61)
**Current text:** `The type of event, if asyncronous.`
**Suggested fix:** `The type of event, if asynchronous.`
**Why:** Clear misspelling.

**File:** `packages/falco/data_stream/alerts_agent/fields/fields.yml` (line 61)
**Current text:** `The type of event, if asyncronous.`
**Suggested fix:** `The type of event, if asynchronous.`
**Why:** Same misspelling.

### 2. Typo family: `readeable` → `readable`

**File:** `packages/prisma_cloud/data_stream/vulnerability/fields/vulnerability.yml` (line 12)
**Current text:** `The human readeable title of the vulnerability.`
**Suggested fix:** `The human readable title of the vulnerability.`
**Why:** Clear misspelling.

**File:** `packages/prisma_cloud/elasticsearch/transform/vulnerability/fields/vulnerability.yml` (line 12)
**Current text:** `The human readeable title of the vulnerability.`
**Suggested fix:** `The human readable title of the vulnerability.`
**Why:** Same misspelling.

**File:** `packages/google_scc/data_stream/finding/fields/vulnerability.yml` (line 12)
**Current text:** `The human readeable title of the vulnerability.`
**Suggested fix:** `The human readable title of the vulnerability.`
**Why:** Same misspelling.

**File:** `packages/google_scc/elasticsearch/transform/latest_cdr_vulnerabilities/fields/vulnerability.yml` (line 12)
**Current text:** `The human readeable title of the vulnerability.`
**Suggested fix:** `The human readable title of the vulnerability.`
**Why:** Same misspelling.

**File:** `packages/sysdig/data_stream/vulnerability/fields/vulnerability.yml` (line 12)
**Current text:** `The human readeable title of the vulnerability.`
**Suggested fix:** `The human readable title of the vulnerability.`
**Why:** Same misspelling.

**File:** `packages/aws/data_stream/inspector/fields/vulnerability.yml` (line 12)
**Current text:** `The human readeable title of the vulnerability.`
**Suggested fix:** `The human readable title of the vulnerability.`
**Why:** Same misspelling.

**File:** `packages/aws/elasticsearch/transform/latest_cdr_vulnerabilities_awsinspector/fields/vulnerability.yml` (line 12)
**Current text:** `The human readeable title of the vulnerability.`
**Suggested fix:** `The human readable title of the vulnerability.`
**Why:** Same misspelling.

### 3. Typo family: `identifer` → `identifier`

**File:** `packages/m365_defender/data_stream/event/fields/fields.yml` (line 24)
**Current text:** `The Microsoft Entra security identifer for the account.`
**Suggested fix:** `The Microsoft Entra security identifier for the account.`
**Why:** Clear misspelling.

**File:** `packages/tychon/data_stream/systemcerts/fields/fields.yml` (line 219)
**Current text:** `Subject Key identifer`
**Suggested fix:** `Subject Key identifier`
**Why:** Same misspelling.

**File:** `packages/tychon/elasticsearch/transform/systemcerts/fields/fields.yml` (line 219)
**Current text:** `Subject Key identifer`
**Suggested fix:** `Subject Key identifier`
**Why:** Same misspelling.

### 4. Clear docs text issues

**File:** `docs/extend/developer-workflow-import-beat.md` (line 37)
**Current text:** `Elasticseach instance:`
**Suggested fix:** `Elasticsearch instance:`
**Why:** Product name misspelling.

**File:** `docs/ci_pipelines.md` (line 156)
**Current text:** `More details about these environments variables ...`
**Suggested fix:** `More details about these environment variables ...`
**Why:** Clear grammar error.

**File:** `docs/ci_pipelines.md` (lines 187, 189)
**Current text:** `(buildkite.com/redacted)
**Suggested fix:** `(buildkite.com/redacted)
**Why:** In-file naming is `integrations-serverless`; current URL slug is inconsistent and likely incorrect.

### 5. Misleading runtime message in tests reporter

**File:** `dev/testsreporter/testsreporter.go` (line 61)
**Current text:** `Skip creating GitHub issues, hit the maximum number (%d) of tests to report...`
**Suggested fix:** `Skipping per-test GitHub issues because the maximum (%d) was reached. Creating a single build-level issue instead...`
**Why:** The code immediately continues and creates/reports one issue, so the current wording is directly misleading.

## Suggested Actions

- [ ] Replace `asyncronous` with `asynchronous` in both Falco field files.
- [ ] Replace `readeable` with `readable` across all seven vulnerability field files listed above.
- [ ] Replace `identifer` with `identifier` in all three listed field files.
- [ ] Fix the three docs text issues in `docs/extend/developer-workflow-import-beat.md` and `docs/ci_pipelines.md`.
- [ ] Update the tests reporter message in `dev/testsreporter/testsreporter.go` to match actual behavior.

> [!NOTE]
>
> 🔒 Integrity filter blocked 1 item
>
> The following item were blocked because they don't meet the GitHub integrity level.
>
> - [#5118](https://github.com/elastic/integrations/issues/5118) `search_issues`: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
>
> 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/integrations/actions/runs/26507680819)

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