[text-auditor] Batch fix clear user-facing typos and grammar in docs and runtime messages

## Text Improvements

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

### 1. Typo in top-level README (`repostiory`)

**File:** `README.md` (line 21)
**Current text:** `More information about the CI pipelines that are available in this repostiory [here](./docs/ci_pipelines.md).`
**Suggested fix:** `More information about the CI pipelines that are available in this repository [here](./docs/ci_pipelines.md).`
**Why:** Clear spelling error in primary user-facing documentation.

### 2. Typo family: `reponse` → `response` in Azure Firewall Logs docs/field descriptions (6 occurrences)

**File:** `packages/azure/data_stream/firewall_logs/fields/fields.yml` (line 109)
**Current text:** `DNS reponse code.`
**Suggested fix:** `DNS response code.`
**Why:** Clear spelling error in user-facing field description.

**File:** `packages/azure/data_stream/firewall_logs/fields/fields.yml` (line 113)
**Current text:** `DNS reponse flags, comma separated.`
**Suggested fix:** `DNS response flags, comma separated.`
**Why:** Clear spelling error in user-facing field description.

**File:** `packages/azure/data_stream/firewall_logs/fields/fields.yml` (line 117)
**Current text:** `DNS reponse size in bytes.`
**Suggested fix:** `DNS response size in bytes.`
**Why:** Clear spelling error in user-facing field description.

**File:** `packages/azure/docs/firewall_logs.md` (line 201)
**Current text:** `DNS reponse code.`
**Suggested fix:** `DNS response code.`
**Why:** Clear spelling error in user-facing package documentation.

**File:** `packages/azure/docs/firewall_logs.md` (line 202)
**Current text:** `DNS reponse flags, comma separated.`
**Suggested fix:** `DNS response flags, comma separated.`
**Why:** Clear spelling error in user-facing package documentation.

**File:** `packages/azure/docs/firewall_logs.md` (line 203)
**Current text:** `DNS reponse size in bytes.`
**Suggested fix:** `DNS response size in bytes.`
**Why:** Clear spelling error in user-facing package documentation.

### 3. Grammar error in user-visible validation error message (`one owners`)

**File:** `dev/codeowners/codeowners.go` (line 239)
**Current text:** `data stream "%s" of package "%s" has more than one owners [%s]`
**Suggested fix:** `data stream "%s" of package "%s" has more than one owner [%s]`
**Why:** Clear grammatical error in runtime validation output.

### 4. Awkward grammar in runtime error message

**File:** `dev/citools/gomod.go` (line 37)
**Current text:** `not found elastic-package dependency`
**Suggested fix:** `elastic-package dependency not found`
**Why:** Clear grammar issue in user-facing runtime error text.

## Suggested Actions

- [x] Fix `repostiory` → `repository` in `README.md`.
- [ ] Fix all six `reponse` → `response` occurrences in Azure firewall field/docs text.
- [x] Update `one owners` → `one owner` in `dev/codeowners/codeowners.go`.
- [x] Update `not found elastic-package dependency` to clearer grammar in `dev/citools/gomod.go`.

> [!NOTE]
>
> 🔒 Integrity filtering filtered 2 items
>
> Integrity filtering activated and filtered the following items during workflow execution.
> This happens when a tool call accesses a resource that does not meet the required integrity or secrecy level of the workflow.
>
> - issue:elastic/integrations#18202 (`issue_read`: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".)
> - issue:elastic/integrations#18214 (`issue_read`: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".)
>
>

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

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