[text-auditor] Fix clear docs/fields grammar and typo families in ELB, Filebeat FAQ, and exported fields

## Text Improvements

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

### 1. Grammar error in ELB module README

**File:** `x-pack/filebeat/module/aws/elb/README.md` (line 46)
**Current text:** `Terraform configuration is included in the metricset to deploy an scenario that deploys`
**Suggested fix:** `Terraform configuration is included in the metricset to deploy a scenario that deploys`
**Why:** Clear article error (`an scenario` -> `a scenario`) in user-facing module documentation.

### 2. Multiple clear grammar/wording issues in Filebeat FAQ sentence

**File:** `docs/reference/filebeat/faq-deleted-files-are-not-freed.md` (line 11)
**Current text:** `...in the mean time... can lead to increase disk utilisation or even out of disk situations.`
**Suggested fix:** `...in the meantime... can lead to increased disk utilization or even out-of-disk situations.`
**Why:** This sentence contains clear wording/grammar defects that reduce readability in a user-facing troubleshooting page.

### 3. Typo family: `acccess` in Google Workspace field description source

**Source file:** `x-pack/filebeat/module/google_workspace/drive/_meta/fields.yml` (line 65)
**Current text:** `The domain for which the acccess scope was changed.`
**Suggested fix:** `The domain for which the access scope was changed.`
**Why:** Clear spelling error (`acccess` -> `access`) in user-facing exported-field text.

**All verified occurrences of this typo family:**
- `x-pack/filebeat/module/google_workspace/drive/_meta/fields.yml:65` (source)
- `docs/reference/filebeat/exported-fields-google_workspace.md:641` (generated from source)
- `filebeat/docs/fields.asciidoc:35003` (generated from source)

### 4. Grammar family: `same value than` in Elasticsearch shard field description source

**Source file:** `metricbeat/module/elasticsearch/shard/_meta/fields.yml` (line 26)
**Current text:** `It has the exact same value than relocating_node.name for compatibility purposes.`
**Suggested fix:** `It has the exact same value as relocating_node.name for compatibility purposes.`
**Why:** Clear grammar error (`same ... than` -> `same ... as`) in user-facing exported-field text.

**All verified occurrences of this grammar family:**
- `metricbeat/module/elasticsearch/shard/_meta/fields.yml:26` (source)
- `docs/reference/metricbeat/exported-fields-elasticsearch.md:2966` (generated from source)

## Suggested Actions

- [ ] Replace `an scenario` with `a scenario` in `x-pack/filebeat/module/aws/elb/README.md`.
- [ ] Rewrite the affected sentence in `docs/reference/filebeat/faq-deleted-files-are-not-freed.md` to `meantime` / `increased disk utilization` / `out-of-disk situations` wording.
- [ ] Replace `acccess` with `access` in `x-pack/filebeat/module/google_workspace/drive/_meta/fields.yml` and regenerate derived docs.
- [ ] Replace `same value than` with `same value as` in `metricbeat/module/elasticsearch/shard/_meta/fields.yml` and regenerate derived docs.

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

Give us feedback! React with 🚀 if perfect, 👍 if helpful, 👎 if not.
> - [x] expires on Sep 21, 2026, 1:24 PM UTC

Review the four named source files: the ELB README, Filebeat FAQ, Google Workspace drive fields.yml, and Elasticsearch shard fields.yml. Correct the listed grammar and spelling issues, then regenerate the derived Google Workspace and Elasticsearch exported-field documentation so all verified occurrences are updated. Done means the suggested wording appears in the source and generated docs.

Written by the indexing model from the issue text.