[text-auditor] Batch fix clear grammar errors in user-facing Buildkite and FortiManager text

## Text Improvements

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

### 1. Grammar error in Buildkite validation message (`hasn't found`)

**File:** `.buildkite/scripts/backport_branch.sh` (line 258)
**Current text:** `The entered commit hasn't found in the **\$\{SOURCE_BRANCH}** branch`
**Suggested fix:** `The entered commit hasn't been found in the **\$\{SOURCE_BRANCH}** branch`
**Why:** Missing auxiliary verb (`been`) makes the message grammatically incorrect.

### 2. Grammar error in Buildkite validation message (`does not creates`)

**File:** `.buildkite/scripts/backport_branch.sh` (line 280)
**Current text:** `This changeset does not creates the version \$\{PACKAGE_VERSION}`
**Suggested fix:** `This changeset does not create the version \$\{PACKAGE_VERSION}`
**Why:** After `does not`, the verb should be in base form (`create`).

### 3. Verb form error in FortiManager setup description (`needs to setup`)

**File:** `packages/fortinet_fortimanager/data_stream/log/fields/fields.yml` (line 528)
**Current text:** `Whether it needs to setup or not.`
**Suggested fix:** `Whether it needs to be set up or not.`
**Why:** `setup` is a noun/adjective here; the verb phrase should be `set up`.

**File:** `packages/fortinet_fortimanager/docs/README.md` (line 491)
**Current text:** `Whether it needs to setup or not.`
**Suggested fix:** `Whether it needs to be set up or not.`
**Why:** Same user-facing text family appears in docs output.

## Suggested Actions

- [x] Fix both grammar errors in `.buildkite/scripts/backport_branch.sh`.
- [ ] Replace `needs to setup` with `needs to be set up` in both FortiManager occurrences above.

> [!NOTE]
>
> 🔒 Integrity filter blocked 5 items
>
> The following items were blocked because they don't meet the GitHub integrity level.
>
> - [#8311](https://github.com/elastic/integrations/issues/8311) `search_issues`: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
> - [#15905](https://github.com/elastic/integrations/issues/15905) `search_issues`: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
> - [#7992](https://github.com/elastic/integrations/issues/7992) `search_issues`: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
> - [#9335](https://github.com/elastic/integrations/issues/9335) `search_issues`: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
> - [#4827](https://github.com/elastic/integrations/issues/4827) `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/24884986267)

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