elastic / elastic/beats

[text-auditor] Fix repeated `Elastisearch` typo in add_fields docs and changelog text

Open Beginner friendly
#50,701 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

needs_team
Dominant language
Go
Stars
12.7k
Forks
5k
Avg merge
2d 1h
Merged PRs (30d)
370

Description

Text Improvements

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

1. Repeated product-name typo: ElastisearchElasticsearch

Current text: When the event is ingested (e.g. by Elastisearch) the document will have \op_type: "index"` set as a metadata field.`

Suggested fix: When the event is ingested (e.g. by Elasticsearch) the document will have \op_type: "index"` set as a metadata field.`

Why: Clear misspelling of the product name in user-facing documentation.

Verified occurrences (all in-repo matches for Elastisearch):

  • libbeat/processors/actions/docs/add_fields.asciidoc (line 55)
  • docs/reference/filebeat/add-fields.md (line 53)
  • docs/reference/packetbeat/add-fields.md (line 53)
  • docs/reference/winlogbeat/add-fields.md (line 53)
  • docs/reference/metricbeat/add-fields.md (line 53)
  • docs/reference/heartbeat/add-fields.md (line 53)
  • docs/reference/auditbeat/add-fields.md (line 53)
  • CHANGELOG.asciidoc (line 10350)

Suggested Actions

  • Replace Elastisearch with Elasticsearch in all eight verified occurrences listed above.
  • If the docs/reference/*/add-fields.md files are generated from shared source text, apply the fix in the source template and regenerate to prevent reintroduction.

[!NOTE]

🔒 Integrity filter blocked 8 items

The following items were blocked because they don't meet the GitHub integrity level.

  • #15956 search_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
  • #10958 search_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
  • #18542 search_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
  • #21319 search_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
  • #1755 search_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
  • #2926 search_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
  • #28771 search_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
  • #26246 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:

tools:
  github:
    min-integrity: approved  # merged | approved | unapproved | none

What is this? | From workflow: Text Auditor

Give us feedback! React with 🚀 if perfect, 👍 if helpful, 👎 if not.

  • expires on May 21, 2026, 1:50 PM UTC

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with libbeat/processors/actions/docs/add_fields.asciidoc and check whether the docs/reference/*/add-fields.md files are generated from it. Update the eight listed occurrences, including CHANGELOG.asciidoc, and verify that searching the repository finds no remaining Elastisearch typo.

Written by the indexing model from the issue text.

Assessment

Tech stack
elasticsearch
Domain
documentation
Issue type
Documentation
Difficulty
2/5
Estimated time
1-3 hours
Activity status
Quiet
Clarity
Clearly specified
Newbie friendliness
76/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.