Add ES Bootstrap Checks' errors

[stefnestor]

Summary

We link the actual Elasticsearch bootstrap checks errors to the applicable docs already, but for google searchability, adding in the literal error strings.

Generative AI disclosure

1. Did you use a generative AI (GenAI) tool to assist in creating this contribution?

• Yes
• No

[github-actions]

Elastic Docs AI PR menu

Check the box to run an AI review for this pull request.

• Review docs changes (docs-review). Status: queued.

Powered by GitHub Agentic Workflows and docs-actions. For more information, reach out to the docs team.

[github-actions]

🔍 Preview links for changed docs

• deploy-manage/deploy/self-managed/bootstrap-checks.md

[github-actions]

Vale Linting Results

Summary: 5 warnings, 5 suggestions found

⚠️ Warnings (5)

File	Line	Rule	Message
deploy-manage/deploy/self-managed/bootstrap-checks.md	74	Elastic.QuotesPunctuation	Place punctuation inside closing quotation marks.
deploy-manage/deploy/self-managed/bootstrap-checks.md	74	Elastic.Latinisms	Latin terms and abbreviations are a common source of confusion. Use 'for example' instead of 'e.g'.
deploy-manage/deploy/self-managed/bootstrap-checks.md	74	Elastic.Latinisms	Latin terms and abbreviations are a common source of confusion. Use 'for example' instead of 'e.g'.
deploy-manage/deploy/self-managed/bootstrap-checks.md	74	Elastic.Latinisms	Latin terms and abbreviations are a common source of confusion. Use 'and so on' instead of 'etc'.
deploy-manage/deploy/self-managed/bootstrap-checks.md	277	Elastic.Spelling	'http' is a possible misspelling.

💡 Suggestions (5)

File	Line	Rule	Message
deploy-manage/deploy/self-managed/bootstrap-checks.md	58	Elastic.WordChoice	Consider using 'can, might' instead of 'may', unless the term is in the UI.
deploy-manage/deploy/self-managed/bootstrap-checks.md	58	Elastic.WordChoice	Consider using 'can, might' instead of 'may', unless the term is in the UI.
deploy-manage/deploy/self-managed/bootstrap-checks.md	63	Elastic.Semicolons	Use semicolons judiciously.
deploy-manage/deploy/self-managed/bootstrap-checks.md	141	Elastic.WordChoice	Consider using 'can, might' instead of 'may', unless the term is in the UI.
deploy-manage/deploy/self-managed/bootstrap-checks.md	332	Elastic.WordChoice	Consider using 'deactivate, deselect, hide, turn off' instead of 'disable', unless the term is in the UI.

---

The Vale linter checks documentation changes against the Elastic Docs style guide.

To use Vale locally or report issues, refer to Elastic style guide for Vale.

[github-actions]

Docs review summary

Focus areas

• Style and clarity: One non-standard word choice (induce → cause) and a non-standard cross-reference pattern (Refer also to → For more information, see) in the new intro sentence. Vale found no violations.
• Jargon: No unexplained jargon introduced.
• Frontmatter and applies_to: Unchanged and valid.
• Content type fit: Appropriate — error strings add useful search-discoverability context to each check section.
• Parent issue satisfaction: Not applicable (no linked issue).

Key issue

The "Maximum size virtual memory check" section (line 138) has the same error message as the "Max file size check" section immediately above it (max file size [X] for user [Y] is too low). This is almost certainly a copy-paste error. The virtual memory check enforces unlimited address space (as), not file size — the error string should reflect that. Please verify against the Elasticsearch source.

Nits

• Each "This can cause errors like" lead-in would read more naturally with a colon: "This can cause errors like:" (consistent throughout; fix all or none).
• The serial collector error contains a raw %s placeholder rather than the [X]/[Y] format used in other sections. If that is the literal Elasticsearch error string, it's fine to keep as-is.

Generated by Docs review agent for issue #6535 · ● 346.5K

[github-actions]

Likely copy-paste error. This error message (max file size [X] for user [Y] is too low) is identical to the one in the "Max file size check" section above. The maximum size virtual memory check is about address space (as), not file size. The correct error message is likely something like:

max size virtual memory (of user [Y]) is too low, increase to [unlimited]

Please verify against the Elasticsearch source and replace with the actual address-space error string.

[stefnestor]

Cheers, @yetanothertw! Ready again 🙏 .

FWIW for grammar-not-technical edits, you're welcome to directly edit not just suggest 🙂.

[yetanothertw]

👍

[stefnestor]

🙇‍♀️ cheers!