[Cases][Quality] Consolidate and refactor case docs

[nastasha-solomon]

Summary

Fixes https://github.com/elastic/docs-content-internal/issues/791

This PR consolidates and restructures the cases documentation to make it more user-centered, maintainable, and discoverable across solutions. Note that some areas have been lightly edited but no new content was added. This is simply a refresh of the existing content.

Reviewers, I just need a check on the pages I linked in the preview section. Please click around, see if the new organization makes sense, and flag anything that's wrong.

Previews

Core case docs

Core documentation for cases across all Elastic solutions. These docs cover case creation, management, settings, and access control for Stack Management, Security, and Observability, in both Elastic Stack and Serverless deployments.

• Cases overview
• Control case access
• Create cases
• Manage cases
• Search and share cases
• Configure settings
• Use cases as data

Security cases

Solution-specific landing page for Elastic Security users. Introduces cases in the context of security workflows, highlights Security-only features, and links to the centralized docs for detailed guidance.

• Security cases overview and features

Observability cases

Solution-specific landing page for Elastic Observability users. Introduces cases in the context of incident management and links to the centralized docs for detailed guidance.

• Observability cases overview

Major changes

Reduced Duplication

• Consolidated shared content: Duplicated content across Security, Stack, and Observability docs now lives in one central location. Security-specific features are kept in the Security docs.

Improved maintainability

• Clearer file structure: The cases/ folder now has a logical, flat structure with dedicated files for each task (create, manage, find/share, configure access, settings).
• Delete snippet files: Removed 17 snippet files and added their content into the appropriate files. This makes it easier to update content in one place and reduces the need to track dependencies.

Refined IA and enhanced content findability

• Task-oriented organization: Content is now organized by user task rather than by feature area:
  • create-cases.md - Creating new cases
  • manage-cases.md - Working with existing cases
  • search-share-cases.md - Searching and sharing cases
  • control-case-access.md - Setting up permissions
  • configure-cases-settings.md - Configuring case settings
• Reduced navigation depth: Users can find what they need faster without navigating through deeply nested pages.
• Separated alerting from cases: Renamed alerts-cases.md to alerting.md to better reflect content scope and reduce confusion.
• Redirects: All old paths redirect to new locations, ensuring external links (from Kibana, Elasticsearch docs, etc.) continue to work.

Generative AI disclosure

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

• Yes
• No

Cursor and Claude

[github-actions]

Vale Linting Results

Summary: 28 warnings, 254 suggestions found

⚠️ Warnings (28)

File	Line	Rule	Message
explore-analyze/alerting/alerts.md	29	Elastic.Latinisms	Latin terms and abbreviations are a common source of confusion. Use 'using' instead of 'via'.
explore-analyze/alerting/alerts/alerting-getting-started.md	46	Elastic.Latinisms	Latin terms and abbreviations are a common source of confusion. Use 'using' instead of 'via'.
explore-analyze/alerting/alerts/alerting-getting-started.md	83	Elastic.Latinisms	Latin terms and abbreviations are a common source of confusion. Use 'using' instead of 'via'.
explore-analyze/alerting/alerts/alerting-troubleshooting.md	55	Elastic.Latinisms	Latin terms and abbreviations are a common source of confusion. Use 'using' instead of 'via'.
explore-analyze/alerting/alerts/alerting-troubleshooting.md	92	Elastic.DontUse	Don't use 'very'.
explore-analyze/alerting/alerts/maintenance-windows.md	55	Elastic.DontUse	Don't use 'Note that'.
explore-analyze/alerting/alerts/testing-connectors.md	38	Elastic.Latinisms	Latin terms and abbreviations are a common source of confusion. Use 'using' instead of 'via'.
explore-analyze/alerting/watcher/actions-email.md	106	Elastic.Latinisms	Latin terms and abbreviations are a common source of confusion. Use 'using' instead of 'via'.
explore-analyze/alerting/watcher/actions-jira.md	69	Elastic.Latinisms	Latin terms and abbreviations are a common source of confusion. Use 'and so on' instead of 'etc'.
explore-analyze/alerting/watcher/actions-pagerduty.md	81	Elastic.Latinisms	Latin terms and abbreviations are a common source of confusion. Use 'that is' instead of 'i.e'.
explore-analyze/alerting/watcher/actions-pagerduty.md	122	Elastic.Latinisms	Latin terms and abbreviations are a common source of confusion. Use 'using' instead of 'via'.
explore-analyze/alerting/watcher/actions-webhook.md	131	Elastic.Latinisms	Latin terms and abbreviations are a common source of confusion. Use 'using' instead of 'via'.
explore-analyze/alerting/watcher/actions.md	31	Elastic.BritishSpellings	Use American English spelling 'acknowledgment' instead of British English 'Acknowledgement'.
explore-analyze/alerting/watcher/condition-script.md	13	Elastic.DontUse	Don't use 'Note that'.
explore-analyze/alerting/watcher/enable-watcher.md	20	Elastic.Latinisms	Latin terms and abbreviations are a common source of confusion. Use 'using' instead of 'via'.
explore-analyze/alerting/watcher/how-watcher-works.md	162	Elastic.BritishSpellings	Use American English spelling 'acknowledgment' instead of British English 'Acknowledgement'.
explore-analyze/alerting/watcher/how-watcher-works.md	214	Elastic.Latinisms	Latin terms and abbreviations are a common source of confusion. Use 'that is' instead of 'i.e'.
explore-analyze/alerting/watcher/how-watcher-works.md	229	Elastic.Latinisms	Latin terms and abbreviations are a common source of confusion. Use 'for example' instead of 'e.g'.
explore-analyze/alerting/watcher/how-watcher-works.md	229	Elastic.Latinisms	Latin terms and abbreviations are a common source of confusion. Use 'using' instead of 'via'.
explore-analyze/alerting/watcher/how-watcher-works.md	229	Elastic.Latinisms	Latin terms and abbreviations are a common source of confusion. Use 'for example' instead of 'e.g'.
explore-analyze/alerting/watcher/how-watcher-works.md	229	Elastic.Latinisms	Latin terms and abbreviations are a common source of confusion. Use 'using' instead of 'via'.
explore-analyze/alerting/watcher/input-http.md	166	Elastic.Latinisms	Latin terms and abbreviations are a common source of confusion. Use 'using' instead of 'via'.
explore-analyze/alerting/watcher/input-http.md	179	Elastic.DontUse	Don't use 'Note that'.
explore-analyze/alerting/watcher/input-http.md	179	Elastic.Latinisms	Latin terms and abbreviations are a common source of confusion. Use 'using' instead of 'via'.
explore-analyze/alerting/watcher/throttling.md	12	Elastic.BritishSpellings	Use American English spelling 'acknowledgment' instead of British English 'Acknowledgement'.
explore-analyze/alerting/watcher/transform-script.md	30	Elastic.Latinisms	Latin terms and abbreviations are a common source of confusion. Use 'using' instead of 'via'.
explore-analyze/alerting/watcher/trigger-schedule.md	18	Elastic.Latinisms	Latin terms and abbreviations are a common source of confusion. Use 'using' instead of 'via'.
solutions/security/detect-and-alert.md	30	Elastic.Latinisms	Latin terms and abbreviations are a common source of confusion. Use 'using' instead of 'via'.

💡 Suggestions (254)

File	Line	Rule	Message
deploy-manage/deploy/self-managed/bootstrap-checks.md	190	Elastic.WordChoice	Consider using 'refer to (if it's a document), view (if it's a UI element)' instead of 'see', unless the term is in the UI.
deploy-manage/monitor/monitoring-data/elasticsearch-metrics.md	34	Elastic.WordChoice	Consider using 'refer to (if it's a document), view (if it's a UI element)' instead of 'see', unless the term is in the UI.
deploy-manage/production-guidance/kibana-alerting-production-considerations.md	36	Elastic.WordChoice	Consider using 'refer to (if it's a document), view (if it's a UI element)' instead of 'see', unless the term is in the UI.
explore-analyze/alerting/alerts.md	42	Elastic.Semicolons	Use semicolons judiciously.
explore-analyze/alerting/alerts.md	80	Elastic.Wordiness	Consider using 'many' instead of 'a large number of'.
explore-analyze/alerting/alerts/alerting-common-issues.md	28	Elastic.WordChoice	Consider using 'refer to (if it's a document), view (if it's a UI element)' instead of 'see', unless the term is in the UI.
explore-analyze/alerting/alerts/alerting-common-issues.md	54	Elastic.WordChoice	Consider using 'refer to (if it's a document), view (if it's a UI element)' instead of 'see', unless the term is in the UI.
explore-analyze/alerting/alerts/alerting-common-issues.md	84	Elastic.WordChoice	Consider using 'can, might' instead of 'may', unless the term is in the UI.
explore-analyze/alerting/alerts/alerting-common-issues.md	158	Elastic.WordChoice	Consider using 'cannot' instead of 'unable', unless the term is in the UI.
explore-analyze/alerting/alerts/alerting-getting-started.md	26	Elastic.WordChoice	Consider using 'refer to (if it's a document), view (if it's a UI element)' instead of 'see', unless the term is in the UI.
explore-analyze/alerting/alerts/alerting-getting-started.md	30	Elastic.Wordiness	Consider using 'these' instead of 'all of these'.
explore-analyze/alerting/alerts/alerting-getting-started.md	62	Elastic.WordChoice	Consider using 'refer to (if it's a document), view (if it's a UI element)' instead of 'See', unless the term is in the UI.
explore-analyze/alerting/alerts/alerting-getting-started.md	122	Elastic.Wordiness	Consider using 'some' instead of 'some of the'.
explore-analyze/alerting/alerts/alerting-getting-started.md	128	Elastic.WordChoice	Consider using 'turn off, silence' instead of 'mute', unless the term is in the UI.
explore-analyze/alerting/alerts/alerting-setup.md	25	Elastic.WordChoice	Consider using 'cannot' instead of 'unable', unless the term is in the UI.
explore-analyze/alerting/alerts/alerting-setup.md	25	Elastic.WordChoice	Consider using 'deactivated, deselected, hidden, turned off, unavailable' instead of 'disabled', unless the term is in the UI.
explore-analyze/alerting/alerts/alerting-setup.md	27	Elastic.WordChoice	Consider using 'refer to (if it's a document), view (if it's a UI element)' instead of 'See', unless the term is in the UI.
explore-analyze/alerting/alerts/alerting-setup.md	100	Elastic.WordChoice	Consider using 'deactivate, deselect, hide, turn off' instead of 'disable', unless the term is in the UI.
explore-analyze/alerting/alerts/alerting-setup.md	104	Elastic.Repetition	"support" is repeated.
explore-analyze/alerting/alerts/alerting-setup.md	104	Elastic.Semicolons	Use semicolons judiciously.
explore-analyze/alerting/alerts/alerting-setup.md	113	Elastic.WordChoice	Consider using 'can, might' instead of 'may', unless the term is in the UI.
explore-analyze/alerting/alerts/alerting-troubleshooting.md	18	Elastic.Wordiness	Consider using 'sometimes' instead of 'In some cases'.
explore-analyze/alerting/alerts/alerting-troubleshooting.md	24	Elastic.Wordiness	Consider using 'some' instead of 'Some of the'.
explore-analyze/alerting/alerts/alerting-troubleshooting.md	24	Elastic.WordChoice	Consider using 'can, might' instead of 'may', unless the term is in the UI.
explore-analyze/alerting/alerts/alerting-troubleshooting.md	35	Elastic.WordChoice	Consider using 'refer to (if it's a document), view (if it's a UI element)' instead of 'see', unless the term is in the UI.
explore-analyze/alerting/alerts/alerting-troubleshooting.md	35	Elastic.Wordiness	Consider using 'also' instead of 'In addition'.
explore-analyze/alerting/alerts/alerting-troubleshooting.md	44	Elastic.WordChoice	Consider using 'refer to (if it's a document), view (if it's a UI element)' instead of 'see', unless the term is in the UI.
explore-analyze/alerting/alerts/alerting-troubleshooting.md	51	Elastic.WordChoice	Consider using 'refer to (if it's a document), view (if it's a UI element)' instead of 'see', unless the term is in the UI.
explore-analyze/alerting/alerts/alerting-troubleshooting.md	51	Elastic.WordChoice	Consider using 'can, might' instead of 'may', unless the term is in the UI.
explore-analyze/alerting/alerts/alerting-troubleshooting.md	51	Elastic.WordChoice	Consider using 'can, might' instead of 'may', unless the term is in the UI.
explore-analyze/alerting/alerts/alerting-troubleshooting.md	65	Elastic.Wordiness	Consider using 'also' instead of 'In addition'.
explore-analyze/alerting/alerts/alerting-troubleshooting.md	175	Elastic.Wordiness	Consider using 'also' instead of 'In addition'.
explore-analyze/alerting/alerts/create-manage-rules.md	54	Elastic.Semicolons	Use semicolons judiciously.
explore-analyze/alerting/alerts/create-manage-rules.md	99	Elastic.Wordiness	Consider using 'many' instead of 'a large number of'.
explore-analyze/alerting/alerts/create-manage-rules.md	126	Elastic.WordChoice	Consider using 'deactivate, deselect, hide, turn off' instead of 'disable', unless the term is in the UI.
explore-analyze/alerting/alerts/create-manage-rules.md	128	Elastic.WordChoice	Consider using 'deactivate, deselect, hide, turn off' instead of 'disable', unless the term is in the UI.
explore-analyze/alerting/alerts/create-manage-rules.md	130	Elastic.WordChoice	Consider using 'deactivate, deselect, hide, turn off' instead of 'disable', unless the term is in the UI.
explore-analyze/alerting/alerts/create-manage-rules.md	132	Elastic.WordChoice	Consider using 'deactivate, deselect, hide, turn off' instead of 'disable', unless the term is in the UI.
explore-analyze/alerting/alerts/create-manage-rules.md	184	Elastic.WordChoice	Consider using 'deactivated, deselected, hidden, turned off, unavailable' instead of 'disabled', unless the term is in the UI.
explore-analyze/alerting/alerts/event-log-index.md	14	Elastic.WordChoice	Consider using 'can, might' instead of 'may', unless the term is in the UI.
explore-analyze/alerting/alerts/event-log-index.md	136	Elastic.WordChoice	Consider using 'refer to (if it's a document), view (if it's a UI element)' instead of 'see', unless the term is in the UI.
explore-analyze/alerting/alerts/event-log-index.md	161	Elastic.WordChoice	Consider using 'refer to (if it's a document), view (if it's a UI element)' instead of 'see', unless the term is in the UI.
explore-analyze/alerting/alerts/rule-action-variables.md	29	Elastic.Wordiness	Consider using 'because' instead of 'since'.
explore-analyze/alerting/alerts/rule-action-variables.md	67	Elastic.Semicolons	Use semicolons judiciously.
explore-analyze/alerting/alerts/rule-action-variables.md	93	Elastic.Semicolons	Use semicolons judiciously.
explore-analyze/alerting/alerts/rule-action-variables.md	119	Elastic.Semicolons	Use semicolons judiciously.
explore-analyze/alerting/alerts/rule-action-variables.md	145	Elastic.Semicolons	Use semicolons judiciously.
explore-analyze/alerting/alerts/rule-action-variables.md	215	Elastic.WordChoice	Consider using 'can, might' instead of 'may', unless the term is in the UI.
explore-analyze/alerting/alerts/rule-action-variables.md	304	Elastic.Wordiness	Consider using 'because' instead of 'since'.
explore-analyze/alerting/alerts/rule-action-variables.md	304	Elastic.WordChoice	Consider using 'can, might' instead of 'may', unless the term is in the UI.
explore-analyze/alerting/alerts/rule-type-es-query.md	65	Elastic.Semicolons	Use semicolons judiciously.
explore-analyze/alerting/alerts/rule-types.md	16	Elastic.WordChoice	Consider using 'refer to (if it's a document), view (if it's a UI element)' instead of 'see', unless the term is in the UI.
explore-analyze/alerting/alerts/rule-types.md	53	Elastic.Semicolons	Use semicolons judiciously.
explore-analyze/alerting/alerts/view-alerts.md	36	Elastic.WordChoice	Consider using 'can, might' instead of 'may', unless the term is in the UI.
explore-analyze/alerting/alerts/view-alerts.md	82	Elastic.WordChoice	Consider using 'turn off, silence' instead of 'Mute', unless the term is in the UI.
explore-analyze/alerting/alerts/view-alerts.md	84	Elastic.WordChoice	Consider using 'turn off, silence' instead of 'mute', unless the term is in the UI.
explore-analyze/alerting/alerts/view-alerts.md	84	Elastic.WordChoice	Consider using 'turn off, silence' instead of 'mute', unless the term is in the UI.
explore-analyze/alerting/alerts/view-alerts.md	89	Elastic.WordChoice	Consider using 'turn off, silence' instead of 'mute', unless the term is in the UI.
explore-analyze/alerting/alerts/view-alerts.md	105	Elastic.WordChoice	Consider using 'deactivate, deselect, hide, turn off' instead of 'disable', unless the term is in the UI.
explore-analyze/alerting/watcher.md	31	Elastic.Wordiness	Consider using 'these' instead of 'All of these'.
explore-analyze/alerting/watcher.md	41	Elastic.WordChoice	Consider using 'efficient, basic' instead of 'simple', unless the term is in the UI.
explore-analyze/alerting/watcher.md	50	Elastic.Wordiness	Consider using 'whether' instead of 'whether or not'.
explore-analyze/alerting/watcher.md	50	Elastic.WordChoice	Consider using 'run, start' instead of 'execute', unless the term is in the UI.
explore-analyze/alerting/watcher.md	50	Elastic.WordChoice	Consider using 'efficient, basic' instead of 'simple', unless the term is in the UI.
explore-analyze/alerting/watcher/action-conditions.md	13	Elastic.Wordiness	Consider using 'whether' instead of 'whether or not'.
explore-analyze/alerting/watcher/action-conditions.md	13	Elastic.WordChoice	Consider using 'run, start' instead of 'execute', unless the term is in the UI.
explore-analyze/alerting/watcher/action-conditions.md	13	Elastic.WordChoice	Consider using 'run, start' instead of 'execute', unless the term is in the UI.
explore-analyze/alerting/watcher/action-foreach.md	14	Elastic.Wordiness	Consider using 'to' instead of 'In order to'.
explore-analyze/alerting/watcher/action-foreach.md	50	Elastic.Wordiness	Consider using 'before' instead of 'prior to'.
explore-analyze/alerting/watcher/actions-email.md	17	Elastic.WordChoice	Consider using 'refer to (if it's a document), view (if it's a UI element)' instead of 'See', unless the term is in the UI.
explore-analyze/alerting/watcher/actions-email.md	89	Elastic.WordChoice	Consider using 'refer to (if it's a document), view (if it's a UI element)' instead of 'See', unless the term is in the UI.
explore-analyze/alerting/watcher/actions-email.md	101	Elastic.WordChoice	Consider using 'refer to (if it's a document), view (if it's a UI element)' instead of 'see', unless the term is in the UI.
explore-analyze/alerting/watcher/actions-email.md	102	Elastic.WordChoice	Consider using 'refer to (if it's a document), view (if it's a UI element)' instead of 'See', unless the term is in the UI.
explore-analyze/alerting/watcher/actions-email.md	108	Elastic.WordChoice	Consider using 'refer to (if it's a document), view (if it's a UI element)' instead of 'See', unless the term is in the UI.
explore-analyze/alerting/watcher/actions-email.md	123	Elastic.WordChoice	Consider using 'deactivated, deselected, hidden, turned off, unavailable' instead of 'disabled', unless the term is in the UI.
explore-analyze/alerting/watcher/actions-email.md	125	Elastic.WordChoice	Consider using 'refer to (if it's a document), view (if it's a UI element)' instead of 'see', unless the term is in the UI.
explore-analyze/alerting/watcher/actions-email.md	151	Elastic.WordChoice	Consider using 'refer to (if it's a document), view (if it's a UI element)' instead of 'see', unless the term is in the UI.
explore-analyze/alerting/watcher/actions-email.md	156	Elastic.WordChoice	Consider using 'efficient, basic' instead of 'Simple', unless the term is in the UI.
explore-analyze/alerting/watcher/actions-email.md	186	Elastic.WordChoice	Consider using 'refer to (if it's a document), view (if it's a UI element)' instead of 'see', unless the term is in the UI.
explore-analyze/alerting/watcher/actions-email.md	194	Elastic.WordChoice	Consider using 'refer to (if it's a document), view (if it's a UI element)' instead of 'See', unless the term is in the UI.
explore-analyze/alerting/watcher/actions-email.md	212	Elastic.WordChoice	Consider using 'refer to (if it's a document), view (if it's a UI element)' instead of 'see', unless the term is in the UI.
explore-analyze/alerting/watcher/actions-email.md	221	Elastic.WordChoice	Consider using 'refer to (if it's a document), view (if it's a UI element)' instead of 'See', unless the term is in the UI.
explore-analyze/alerting/watcher/actions-email.md	224	Elastic.WordChoice	Consider using 'efficient, basic' instead of 'Simple', unless the term is in the UI.
explore-analyze/alerting/watcher/actions-email.md	226	Elastic.WordChoice	Consider using 'efficient, basic' instead of 'Simple', unless the term is in the UI.
explore-analyze/alerting/watcher/actions-email.md	245	Elastic.WordChoice	Consider using 'refer to (if it's a document), view (if it's a UI element)' instead of 'see', unless the term is in the UI.
explore-analyze/alerting/watcher/actions-email.md	252	Elastic.WordChoice	Consider using 'refer to (if it's a document), view (if it's a UI element)' instead of 'see', unless the term is in the UI.
explore-analyze/alerting/watcher/actions-email.md	276	Elastic.WordChoice	Consider using 'refer to (if it's a document), view (if it's a UI element)' instead of 'see', unless the term is in the UI.
explore-analyze/alerting/watcher/actions-email.md	296	Elastic.WordChoice	Consider using 'deactivate, deselect, hide, turn off' instead of 'disable', unless the term is in the UI.
explore-analyze/alerting/watcher/actions-index.md	13	Elastic.WordChoice	Consider using 'refer to (if it's a document), view (if it's a UI element)' instead of 'See', unless the term is in the UI.
explore-analyze/alerting/watcher/actions-index.md	42	Elastic.FirstPerson	Use caution when using first-person pronouns such as 'my.'
explore-analyze/alerting/watcher/actions-index.md	57	Elastic.Wordiness	Consider using 'all' instead of 'all of '.
explore-analyze/alerting/watcher/actions-index.md	87	Elastic.Wordiness	Consider using 'because' instead of 'Since'.
explore-analyze/alerting/watcher/actions-jira.md	19	Elastic.WordChoice	Consider using 'efficient, basic' instead of 'simple', unless the term is in the UI.
explore-analyze/alerting/watcher/actions-jira.md	83	Elastic.WordChoice	Consider using 'refer to (if it's a document), view (if it's a UI element)' instead of 'see', unless the term is in the UI.
explore-analyze/alerting/watcher/actions-jira.md	95	Elastic.WordChoice	Consider using 'deactivated, deselected, hidden, turned off, unavailable' instead of 'disabled', unless the term is in the UI.
explore-analyze/alerting/watcher/actions-logging.md	13	Elastic.WordChoice	Consider using 'refer to (if it's a document), view (if it's a UI element)' instead of 'See', unless the term is in the UI.
explore-analyze/alerting/watcher/actions-logging.md	21	Elastic.WordChoice	Consider using 'efficient, basic' instead of 'simple', unless the term is in the UI.
explore-analyze/alerting/watcher/actions-pagerduty.md	19	Elastic.WordChoice	Consider using 'efficient, basic' instead of 'simple', unless the term is in the UI.
explore-analyze/alerting/watcher/actions-pagerduty.md	71	Elastic.Wordiness	Consider using 'some' instead of 'some of the'.
explore-analyze/alerting/watcher/actions-pagerduty.md	84	Elastic.Wordiness	Consider using 'to' instead of 'in order to'.
explore-analyze/alerting/watcher/actions-pagerduty.md	88	Elastic.Wordiness	Consider using 'per' instead of 'as per'.
explore-analyze/alerting/watcher/actions-pagerduty.md	91	Elastic.Wordiness	Consider using 'all' instead of 'All of '.
explore-analyze/alerting/watcher/actions-pagerduty.md	113	Elastic.WordChoice	Consider using 'refer to (if it's a document), view (if it's a UI element)' instead of 'see', unless the term is in the UI.
explore-analyze/alerting/watcher/actions-slack.md	19	Elastic.WordChoice	Consider using 'efficient, basic' instead of 'simple', unless the term is in the UI.
explore-analyze/alerting/watcher/actions-slack.md	41	Elastic.Wordiness	Consider using 'also' instead of 'In addition'.
explore-analyze/alerting/watcher/actions-slack.md	41	Elastic.WordChoice	Consider using 'efficient, basic' instead of 'simple', unless the term is in the UI.
explore-analyze/alerting/watcher/actions-slack.md	136	Elastic.WordChoice	Consider using 'refer to (if it's a document), view (if it's a UI element)' instead of 'see', unless the term is in the UI.
explore-analyze/alerting/watcher/actions-slack.md	146	Elastic.WordChoice	Consider using 'refer to (if it's a document), view (if it's a UI element)' instead of 'see', unless the term is in the UI.
explore-analyze/alerting/watcher/actions-webhook.md	13	Elastic.WordChoice	Consider using 'refer to (if it's a document), view (if it's a UI element)' instead of 'See', unless the term is in the UI.
explore-analyze/alerting/watcher/actions-webhook.md	19	Elastic.WordChoice	Consider using 'efficient, basic' instead of 'simple', unless the term is in the UI.
explore-analyze/alerting/watcher/actions-webhook.md	79	Elastic.WordChoice	Consider using 'efficiently' instead of 'simply', unless the term is in the UI.
explore-analyze/alerting/watcher/actions-webhook.md	101	Elastic.WordChoice	Consider using 'efficiently' instead of 'simply', unless the term is in the UI.
explore-analyze/alerting/watcher/actions.md	88	Elastic.WordChoice	Consider using 'refer to (if it's a document), view (if it's a UI element)' instead of 'See', unless the term is in the UI.
explore-analyze/alerting/watcher/actions.md	90	Elastic.Wordiness	Consider using 'all' instead of 'all of '.
explore-analyze/alerting/watcher/actions.md	150	Elastic.FirstPerson	Use caution when using first-person pronouns such as 'me.'
explore-analyze/alerting/watcher/actions.md	353	Elastic.Wordiness	Consider using 'all' instead of 'all of '.
explore-analyze/alerting/watcher/actions.md	353	Elastic.WordChoice	Consider using 'efficiently' instead of 'simply', unless the term is in the UI.
explore-analyze/alerting/watcher/actions.md	403	Elastic.WordChoice	Consider using 'can, might' instead of 'may', unless the term is in the UI.
explore-analyze/alerting/watcher/condition-array-compare.md	13	Elastic.WordChoice	Consider using 'refer to (if it's a document), view (if it's a UI element)' instead of 'See', unless the term is in the UI.
explore-analyze/alerting/watcher/condition-compare.md	13	Elastic.WordChoice	Consider using 'efficient, basic' instead of 'simple', unless the term is in the UI.
explore-analyze/alerting/watcher/condition-script.md	13	Elastic.WordChoice	Consider using 'refer to (if it's a document), view (if it's a UI element)' instead of 'see', unless the term is in the UI.
explore-analyze/alerting/watcher/condition-script.md	25	Elastic.WordChoice	Consider using 'efficient, basic' instead of 'simple', unless the term is in the UI.
explore-analyze/alerting/watcher/condition-script.md	43	Elastic.WordChoice	Consider using 'efficient, basic' instead of 'simple', unless the term is in the UI.
explore-analyze/alerting/watcher/condition.md	13	Elastic.Wordiness	Consider using 'whether' instead of 'whether or not'.
explore-analyze/alerting/watcher/condition.md	13	Elastic.WordChoice	Consider using 'run, start' instead of 'execute', unless the term is in the UI.
explore-analyze/alerting/watcher/condition.md	17	Elastic.WordChoice	Consider using 'efficient, basic' instead of 'simple', unless the term is in the UI.
explore-analyze/alerting/watcher/condition.md	17	Elastic.Wordiness	Consider using 'whether' instead of 'whether or not'.
explore-analyze/alerting/watcher/condition.md	17	Elastic.WordChoice	Consider using 'run, start' instead of 'execute', unless the term is in the UI.
explore-analyze/alerting/watcher/condition.md	18	Elastic.Wordiness	Consider using 'whether' instead of 'whether or not'.
explore-analyze/alerting/watcher/condition.md	18	Elastic.WordChoice	Consider using 'run, start' instead of 'execute', unless the term is in the UI.
explore-analyze/alerting/watcher/condition.md	19	Elastic.Wordiness	Consider using 'whether' instead of 'whether or not'.
explore-analyze/alerting/watcher/condition.md	19	Elastic.WordChoice	Consider using 'run, start' instead of 'execute', unless the term is in the UI.
explore-analyze/alerting/watcher/condition.md	25	Elastic.Wordiness	Consider using 'whether' instead of 'whether or not'.
explore-analyze/alerting/watcher/condition.md	27	Elastic.Wordiness	Consider using 'also' instead of 'In addition'.
explore-analyze/alerting/watcher/enable-watcher.md	22	Elastic.WordChoice	Consider using 'can, might' instead of 'may', unless the term is in the UI.
explore-analyze/alerting/watcher/enable-watcher.md	22	Elastic.Semicolons	Use semicolons judiciously.
explore-analyze/alerting/watcher/enable-watcher.md	165	Elastic.WordChoice	Consider using 'refer to (if it's a document), view (if it's a UI element)' instead of 'see', unless the term is in the UI.
explore-analyze/alerting/watcher/encrypting-data.md	19	Elastic.Wordiness	Consider using 'all' instead of 'all of '.
explore-analyze/alerting/watcher/execute-watch.md	10	Elastic.WordChoice	Consider using 'run, start' instead of 'Execute', unless the term is in the UI.
explore-analyze/alerting/watcher/execute-watch.md	12	Elastic.WordChoice	Consider using 'run, start' instead of 'execute', unless the term is in the UI.
explore-analyze/alerting/watcher/execute-watch.md	14	Elastic.WordChoice	Consider using 'run, start' instead of 'execute', unless the term is in the UI.
explore-analyze/alerting/watcher/execute-watch.md	155	Elastic.WordChoice	Consider using 'run, start' instead of 'execute', unless the term is in the UI.
explore-analyze/alerting/watcher/execute-watch.md	184	Elastic.WordChoice	Consider using 'run, start' instead of 'execute', unless the term is in the UI.
explore-analyze/alerting/watcher/how-watcher-works.md	21	Elastic.Wordiness	Consider using 'also' instead of 'In addition'.
explore-analyze/alerting/watcher/how-watcher-works.md	108	Elastic.WordChoice	Consider using 'refer to (if it's a document), view (if it's a UI element)' instead of 'see', unless the term is in the UI.
explore-analyze/alerting/watcher/how-watcher-works.md	109	Elastic.Wordiness	Consider using 'all' instead of 'all of '.
explore-analyze/alerting/watcher/how-watcher-works.md	109	Elastic.Wordiness	Consider using 'all' instead of 'All of '.
explore-analyze/alerting/watcher/how-watcher-works.md	132	Elastic.WordChoice	Consider using 'run, start' instead of 'execute', unless the term is in the UI.
explore-analyze/alerting/watcher/how-watcher-works.md	136	Elastic.WordChoice	Consider using 'refer to (if it's a document), view (if it's a UI element)' instead of 'see', unless the term is in the UI.
explore-analyze/alerting/watcher/how-watcher-works.md	141	Elastic.Wordiness	Consider using 'whether' instead of 'whether or not'.
explore-analyze/alerting/watcher/how-watcher-works.md	162	Elastic.WordChoice	Consider using 'refer to (if it's a document), view (if it's a UI element)' instead of 'see', unless the term is in the UI.
explore-analyze/alerting/watcher/how-watcher-works.md	174	Elastic.WordChoice	Consider using 'run, start' instead of 'execute', unless the term is in the UI.
explore-analyze/alerting/watcher/how-watcher-works.md	187	Elastic.WordChoice	Consider using 'refer to (if it's a document), view (if it's a UI element)' instead of 'see', unless the term is in the UI.
explore-analyze/alerting/watcher/how-watcher-works.md	255	Elastic.WordChoice	Consider using 'efficiently' instead of 'simply', unless the term is in the UI.
explore-analyze/alerting/watcher/how-watcher-works.md	268	Elastic.WordChoice	Consider using 'efficiently' instead of 'simply', unless the term is in the UI.
explore-analyze/alerting/watcher/input-chain.md	55	Elastic.Wordiness	Consider using 'to' instead of 'In order to'.
explore-analyze/alerting/watcher/input-chain.md	55	Elastic.WordChoice	Consider using 'refer to (if it's a document), view (if it's a UI element)' instead of 'see', unless the term is in the UI.
explore-analyze/alerting/watcher/input-http.md	13	Elastic.WordChoice	Consider using 'refer to (if it's a document), view (if it's a UI element)' instead of 'See', unless the term is in the UI.
explore-analyze/alerting/watcher/input-http.md	13	Elastic.Wordiness	Consider using 'all' instead of 'all of '.
explore-analyze/alerting/watcher/input-http.md	157	Elastic.Wordiness	Consider using 'also' instead of 'In addition'.
explore-analyze/alerting/watcher/input-http.md	170	Elastic.WordChoice	Consider using 'can, might' instead of 'May', unless the term is in the UI.
explore-analyze/alerting/watcher/input-search.md	13	Elastic.WordChoice	Consider using 'refer to (if it's a document), view (if it's a UI element)' instead of 'See', unless the term is in the UI.
explore-analyze/alerting/watcher/input-search.md	13	Elastic.Wordiness	Consider using 'all' instead of 'all of '.
explore-analyze/alerting/watcher/input-search.md	128	Elastic.Wordiness	Consider using 'all' instead of 'all of '.
explore-analyze/alerting/watcher/input-search.md	130	Elastic.WordChoice	Consider using 'select, press, visits' instead of 'hit', unless the term is in the UI.
explore-analyze/alerting/watcher/input-search.md	130	Elastic.WordChoice	Consider using 'select, press, visits' instead of 'hit', unless the term is in the UI.
explore-analyze/alerting/watcher/input-search.md	131	Elastic.WordChoice	Consider using 'select, press, visits' instead of 'hit', unless the term is in the UI.
explore-analyze/alerting/watcher/input-search.md	131	Elastic.WordChoice	Consider using 'select, press, visits' instead of 'hit', unless the term is in the UI.
explore-analyze/alerting/watcher/input-search.md	144	Elastic.WordChoice	Consider using 'refer to (if it's a document), view (if it's a UI element)' instead of 'See', unless the term is in the UI.
explore-analyze/alerting/watcher/input-search.md	146	Elastic.WordChoice	Consider using 'refer to (if it's a document), view (if it's a UI element)' instead of 'See', unless the term is in the UI.
explore-analyze/alerting/watcher/input-search.md	147	Elastic.WordChoice	Consider using 'refer to (if it's a document), view (if it's a UI element)' instead of 'See', unless the term is in the UI.
explore-analyze/alerting/watcher/input-simple.md	2	Elastic.WordChoice	Consider using 'efficient, basic' instead of 'Simple', unless the term is in the UI.
explore-analyze/alerting/watcher/input-simple.md	11	Elastic.WordChoice	Consider using 'efficient, basic' instead of 'Simple', unless the term is in the UI.
explore-analyze/alerting/watcher/schedule-types.md	109	Elastic.Wordiness	Consider using 'also' instead of 'In addition'.
explore-analyze/alerting/watcher/schedule-types.md	425	Elastic.WordChoice	Consider using 'run, start' instead of 'execute', unless the term is in the UI.
explore-analyze/alerting/watcher/schedule-types.md	434	Elastic.WordChoice	Consider using 'efficiently' instead of 'simply', unless the term is in the UI.
explore-analyze/alerting/watcher/throttling.md	12	Elastic.WordChoice	Consider using 'refer to (if it's a document), view (if it's a UI element)' instead of 'see', unless the term is in the UI.
explore-analyze/alerting/watcher/transform-script.md	30	Elastic.WordChoice	Consider using 'can, might' instead of 'may', unless the term is in the UI.
explore-analyze/alerting/watcher/transform-script.md	35	Elastic.WordChoice	Consider using 'can, might' instead of 'may', unless the term is in the UI.
explore-analyze/alerting/watcher/transform-script.md	47	Elastic.Wordiness	Consider using 'also' instead of 'In addition'.
explore-analyze/alerting/watcher/transform-search.md	13	Elastic.WordChoice	Consider using 'efficient, basic' instead of 'simple', unless the term is in the UI.
explore-analyze/alerting/watcher/transform-search.md	27	Elastic.Wordiness	Consider using 'use' instead of 'make use of'.
explore-analyze/alerting/watcher/transform-search.md	56	Elastic.WordChoice	Consider using 'refer to (if it's a document), view (if it's a UI element)' instead of 'see', unless the term is in the UI.
explore-analyze/alerting/watcher/transform-search.md	57	Elastic.WordChoice	Consider using 'refer to (if it's a document), view (if it's a UI element)' instead of 'see', unless the term is in the UI.
explore-analyze/alerting/watcher/transform-search.md	58	Elastic.WordChoice	Consider using 'refer to (if it's a document), view (if it's a UI element)' instead of 'see', unless the term is in the UI.
explore-analyze/alerting/watcher/transform-search.md	59	Elastic.WordChoice	Consider using 'refer to (if it's a document), view (if it's a UI element)' instead of 'See', unless the term is in the UI.
explore-analyze/alerting/watcher/trigger-schedule.md	18	Elastic.WordChoice	Consider using 'can, might' instead of 'may', unless the term is in the UI.
explore-analyze/alerting/watcher/trigger-schedule.md	21	Elastic.WordChoice	Consider using 'can, might' instead of 'may', unless the term is in the UI.
explore-analyze/alerting/watcher/trigger-schedule.md	31	Elastic.WordChoice	Consider using 'run, start' instead of 'execute', unless the term is in the UI.
explore-analyze/alerting/watcher/watch-cluster-status.md	12	Elastic.WordChoice	Consider using 'efficiently' instead of 'easily', unless the term is in the UI.
explore-analyze/alerting/watcher/watch-cluster-status.md	16	Elastic.Wordiness	Consider using 'act' instead of 'Take action'.
explore-analyze/alerting/watcher/watch-cluster-status.md	33	Elastic.WordChoice	Consider using 'efficiently' instead of 'easily', unless the term is in the UI.
explore-analyze/alerting/watcher/watch-cluster-status.md	33	Elastic.WordChoice	Consider using 'refer to (if it's a document), view (if it's a UI element)' instead of 'see', unless the term is in the UI.
explore-analyze/alerting/watcher/watch-cluster-status.md	33	Elastic.Wordiness	Consider using 'because' instead of 'Since'.
explore-analyze/alerting/watcher/watch-cluster-status.md	41	Elastic.WordChoice	Consider using 'efficiently' instead of 'simply', unless the term is in the UI.
explore-analyze/alerting/watcher/watch-cluster-status.md	89	Elastic.WordChoice	Consider using 'can, might' instead of 'may', unless the term is in the UI.
explore-analyze/alerting/watcher/watch-cluster-status.md	89	Elastic.WordChoice	Consider using 'refer to (if it's a document), view (if it's a UI element)' instead of 'see', unless the term is in the UI.
explore-analyze/alerting/watcher/watch-cluster-status.md	91	Elastic.WordChoice	Consider using 'refer to (if it's a document), view (if it's a UI element)' instead of 'see', unless the term is in the UI.
explore-analyze/alerting/watcher/watch-cluster-status.md	106	Elastic.Wordiness	Consider using 'because' instead of 'Since'.
explore-analyze/alerting/watcher/watch-cluster-status.md	108	Elastic.WordChoice	Consider using 'refer to (if it's a document), view (if it's a UI element)' instead of 'see', unless the term is in the UI.
explore-analyze/alerting/watcher/watch-cluster-status.md	133	Elastic.WordChoice	Consider using 'efficiently' instead of 'easily', unless the term is in the UI.
explore-analyze/alerting/watcher/watch-cluster-status.md	133	Elastic.WordChoice	Consider using 'refer to (if it's a document), view (if it's a UI element)' instead of 'see', unless the term is in the UI.
explore-analyze/alerting/watcher/watch-cluster-status.md	135	Elastic.WordChoice	Consider using 'refer to (if it's a document), view (if it's a UI element)' instead of 'see', unless the term is in the UI.
explore-analyze/alerting/watcher/watch-cluster-status.md	137	Elastic.WordChoice	Consider using 'refer to (if it's a document), view (if it's a UI element)' instead of 'see', unless the term is in the UI.
explore-analyze/alerting/watcher/watch-cluster-status.md	148	Elastic.Wordiness	Consider using 'act' instead of 'Take action'.
explore-analyze/alerting/watcher/watch-cluster-status.md	210	Elastic.WordChoice	Consider using 'refer to (if it's a document), view (if it's a UI element)' instead of 'see', unless the term is in the UI.
explore-analyze/alerting/watcher/watch-cluster-status.md	213	Elastic.WordChoice	Consider using 'refer to (if it's a document), view (if it's a UI element)' instead of 'see', unless the term is in the UI.
explore-analyze/alerting/watcher/watch-cluster-status.md	226	Elastic.Wordiness	Consider using 'because' instead of 'Since'.
explore-analyze/alerting/watcher/watcher-getting-started.md	15	Elastic.WordChoice	Consider using 'refer to (if it's a document), view (if it's a UI element)' instead of 'see', unless the term is in the UI.
explore-analyze/alerting/watcher/watcher-getting-started.md	45	Elastic.WordChoice	Consider using 'efficiently' instead of 'easily', unless the term is in the UI.
explore-analyze/alerting/watcher/watcher-getting-started.md	45	Elastic.WordChoice	Consider using 'refer to (if it's a document), view (if it's a UI element)' instead of 'see', unless the term is in the UI.
explore-analyze/alerting/watcher/watcher-getting-started.md	45	Elastic.Wordiness	Consider using 'because' instead of 'Since'.
explore-analyze/alerting/watcher/watcher-getting-started.md	48	Elastic.WordChoice	Consider using 'refer to (if it's a document), view (if it's a UI element)' instead of 'see', unless the term is in the UI.
explore-analyze/alerting/watcher/watcher-getting-started.md	63	Elastic.WordChoice	Consider using 'refer to (if it's a document), view (if it's a UI element)' instead of 'see', unless the term is in the UI.
explore-analyze/alerting/watcher/watcher-getting-started.md	65	Elastic.WordChoice	Consider using 'efficiently' instead of 'simply', unless the term is in the UI.
explore-analyze/alerting/watcher/watcher-getting-started.md	65	Elastic.WordChoice	Consider using 'refer to (if it's a document), view (if it's a UI element)' instead of 'see', unless the term is in the UI.
explore-analyze/alerting/watcher/watcher-getting-started.md	89	Elastic.WordChoice	Consider using 'efficiently' instead of 'easily', unless the term is in the UI.
explore-analyze/alerting/watcher/watcher-getting-started.md	103	Elastic.Wordiness	Consider using 'whether' instead of 'whether or not'.
explore-analyze/alerting/watcher/watcher-getting-started.md	156	Elastic.Wordiness	Consider using 'because' instead of 'Since'.
explore-analyze/alerting/watcher/watcher-getting-started.md	156	Elastic.WordChoice	Consider using 'refer to (if it's a document), view (if it's a UI element)' instead of 'see', unless the term is in the UI.
explore-analyze/alerting/watcher/watcher-getting-started.md	168	Elastic.Semicolons	Use semicolons judiciously.
explore-analyze/alerting/watcher/watcher-getting-started.md	168	Elastic.WordChoice	Consider using 'run, start' instead of 'execute', unless the term is in the UI.
explore-analyze/alerting/watcher/watcher-getting-started.md	172	Elastic.WordChoice	Consider using 'refer to (if it's a document), view (if it's a UI element)' instead of 'See', unless the term is in the UI.
explore-analyze/alerting/watcher/watcher-getting-started.md	173	Elastic.WordChoice	Consider using 'refer to (if it's a document), view (if it's a UI element)' instead of 'See', unless the term is in the UI.
explore-analyze/alerting/watcher/watcher-getting-started.md	174	Elastic.WordChoice	Consider using 'refer to (if it's a document), view (if it's a UI element)' instead of 'See', unless the term is in the UI.
explore-analyze/alerting/watcher/watcher-ui.md	17	Elastic.WordChoice	Consider using 'efficient, basic' instead of 'simple', unless the term is in the UI.
explore-analyze/alerting/watcher/watcher-ui.md	40	Elastic.WordChoice	Consider using 'refer to (if it's a document), view (if it's a UI element)' instead of 'See', unless the term is in the UI.
explore-analyze/alerting/watcher/watcher-ui.md	45	Elastic.Wordiness	Consider using 'between' instead of 'in between'.
explore-analyze/alerting/watcher/watcher-ui.md	63	Elastic.WordChoice	Consider using 'refer to (if it's a document), view (if it's a UI element)' instead of 'see', unless the term is in the UI.
explore-analyze/alerting/watcher/watcher-ui.md	78	Elastic.WordChoice	Consider using 'refer to (if it's a document), view (if it's a UI element)' instead of 'see', unless the term is in the UI.
explore-analyze/alerting/watcher/watcher-ui.md	95	Elastic.WordChoice	Consider using 'refer to (if it's a document), view (if it's a UI element)' instead of 'see', unless the term is in the UI.
explore-analyze/alerting/watcher/watcher-ui.md	95	Elastic.WordChoice	Consider using 'run, start' instead of 'execute', unless the term is in the UI.
explore-analyze/alerting/watcher/watcher-ui.md	103	Elastic.WordChoice	Consider using 'run, start' instead of 'execute', unless the term is in the UI.
explore-analyze/alerting/watcher/watcher-ui.md	132	Elastic.WordChoice	Consider using 'refer to (if it's a document), view (if it's a UI element)' instead of 'see', unless the term is in the UI.
explore-analyze/alerting/watcher/watcher-ui.md	151	Elastic.WordChoice	Consider using 'refer to (if it's a document), view (if it's a UI element)' instead of 'see', unless the term is in the UI.
explore-analyze/alerting/watcher/watcher-ui.md	151	Elastic.WordChoice	Consider using 'refer to (if it's a document), view (if it's a UI element)' instead of 'see', unless the term is in the UI.
explore-analyze/alerting/watcher/watcher-ui.md	151	Elastic.WordChoice	Consider using 'run, start' instead of 'Execute', unless the term is in the UI.
explore-analyze/cases/cases-as-data.md	28	Elastic.WordChoice	Consider using 'can, might' instead of 'may', unless the term is in the UI.
explore-analyze/cases/cases-as-data.md	38	Elastic.WordChoice	Consider using 'can, might' instead of 'may', unless the term is in the UI.
explore-analyze/cases/configure-case-settings.md	119	Elastic.Wordiness	Consider using 'also' instead of 'In addition'.
explore-analyze/cases/manage-cases.md	64	Elastic.WordChoice	Consider using 'can, might' instead of 'may', unless the term is in the UI.
explore-analyze/machine-learning/anomaly-detection/ml-configuring-alerts.md	252	Elastic.WordChoice	Consider using 'deactivate, deselect, hide, turn off' instead of 'disable', unless the term is in the UI.
manage-data/data-store/data-streams/failure-store-recipes.md	310	Elastic.Wordiness	Consider using 'because' instead of 'Since'.
manage-data/data-store/data-streams/failure-store-recipes.md	311	Elastic.WordChoice	Consider using 'efficient, basic' instead of 'simple', unless the term is in the UI.
reference/fleet/monitor-elastic-agent.md	244	Elastic.WordChoice	Consider using 'refer to (if it's a document), view (if it's a UI element)' instead of 'see', unless the term is in the UI.
reference/glossary/index.md	829	Elastic.WordChoice	Consider using 'refer to (if it's a document), view (if it's a UI element)' instead of 'See', unless the term is in the UI.
solutions/observability/apm/create-apm-rules-alerts.md	70	Elastic.WordChoice	Consider using 'refer to (if it's a document), view (if it's a UI element)' instead of 'See', unless the term is in the UI.
solutions/security/ai/attack-discovery.md	150	Elastic.Wordiness	Consider using 'act' instead of 'Take action'.
solutions/security/detect-and-alert/create-detection-rule.md	664	Elastic.WordChoice	Consider using 'refer to (if it's a document), view (if it's a UI element)' instead of 'see', unless the term is in the UI.
solutions/security/detect-and-alert/using-logsdb-index-mode-with-elastic-security.md	65	Elastic.WordChoice	Consider using 'can, might' instead of 'may', unless the term is in the UI.
solutions/security/investigate/security-cases.md	62	Elastic.WordChoice	Consider using 'refer to (if it's a document), view (if it's a UI element)' instead of 'see', unless the term is in the UI.
troubleshoot/elasticsearch/mapping-explosion.md	35	Elastic.WordChoice	Consider using 'can, might' instead of 'may', unless the term is in the UI.
troubleshoot/kibana/alerts.md	38	Elastic.WordChoice	Consider using 'refer to (if it's a document), view (if it's a UI element)' instead of 'see', unless the term is in the UI.
troubleshoot/kibana/alerts.md	38	Elastic.Wordiness	Consider using 'also' instead of 'In addition'.

---

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]

🔍 Preview links for changed docs

• explore-analyze/alerting.md
• explore-analyze/cases.md
• explore-analyze/cases/configure-case-settings.md
• explore-analyze/cases/control-case-access.md
• explore-analyze/cases/create-cases.md
• explore-analyze/cases/manage-cases.md
• explore-analyze/cases/search-share-cases.md
• solutions/observability/incident-management/observability-cases.md
• solutions/security/investigate/security-cases.md
• deploy-manage/autoscaling/autoscaling-in-ece-and-ech.md

More links …

• deploy-manage/deploy/cloud-enterprise/edit-stack-settings-elasticsearch.md
• deploy-manage/deploy/cloud-on-k8s/k8s-service-mesh-istio.md
• deploy-manage/deploy/deployment-comparison.md
• deploy-manage/deploy/elastic-cloud/differences-from-other-elasticsearch-offerings.md
• deploy-manage/deploy/elastic-cloud/restrictions-known-problems.md
• deploy-manage/deploy/elastic-cloud/tools-apis.md
• deploy-manage/deploy/self-managed/bootstrap-checks.md
• deploy-manage/manage-connectors.md
• deploy-manage/monitor/kibana-task-manager-health-monitoring.md
• deploy-manage/monitor/monitoring-data/configure-stack-monitoring-alerts.md
• deploy-manage/monitor/monitoring-data/elasticsearch-metrics.md
• deploy-manage/monitor/monitoring-data/integrations-server-page.md
• deploy-manage/production-guidance/kibana-alerting-production-considerations.md
• deploy-manage/production-guidance/kibana-in-production-environments.md
• deploy-manage/production-guidance/kibana-task-manager-scaling-considerations.md
• deploy-manage/tools/snapshot-and-restore/create-snapshots.md
• deploy-manage/users-roles/cluster-or-deployment-auth/quickstart.md
• explore-analyze/ai-features/agent-builder/tools/builtin-tools-reference.md
• explore-analyze/discover/discover-get-started.md
• explore-analyze/find-and-organize/files.md
• explore-analyze/geospatial-analysis.md
• explore-analyze/machine-learning/anomaly-detection/ml-configuring-alerts.md
• explore-analyze/query-filter/languages/esql-kibana.md
• explore-analyze/report-and-share/automating-report-generation.md
• explore-analyze/scripting/modules-scripting-painless.md
• explore-analyze/scripting/painless-lab.md
• explore-analyze/transforms/transform-alerts.md
• explore-analyze/workflows/data.md
• get-started/evaluate-elastic.md
• get-started/the-stack.md
• manage-data/data-store/data-streams/failure-store-recipes.md
• reference/fleet/alerting-rule-templates.md
• reference/fleet/monitor-elastic-agent.md
• reference/glossary/index.md
• solutions/observability/apm/create-apm-rules-alerts.md
• solutions/observability/incident-management.md
• solutions/observability/incident-management/create-a-degraded-docs-rule.md
• solutions/observability/incident-management/create-a-failed-docs-rule.md
• solutions/observability/incident-management/create-an-anomaly-detection-rule.md
• solutions/observability/incident-management/create-an-apm-anomaly-rule.md
• solutions/observability/incident-management/create-an-elasticsearch-query-rule.md
• solutions/observability/incident-management/create-an-error-count-threshold-rule.md
• solutions/observability/incident-management/create-an-inventory-rule.md
• solutions/observability/incident-management/create-an-slo-burn-rate-rule.md
• solutions/observability/incident-management/create-custom-threshold-rule.md
• solutions/observability/incident-management/create-failed-transaction-rate-threshold-rule.md
• solutions/observability/incident-management/create-latency-threshold-rule.md
• solutions/observability/incident-management/create-log-threshold-rule.md
• solutions/observability/incident-management/create-manage-rules.md
• solutions/observability/incident-management/create-metric-threshold-rule.md
• solutions/observability/incident-management/create-monitor-status-rule.md
• solutions/observability/incident-management/create-tls-certificate-rule.md
• solutions/observability/incident-management/triage-slo-burn-rate-breaches.md
• solutions/observability/incident-management/triage-threshold-breaches.md
• solutions/observability/incident-management/view-alerts.md
• solutions/observability/infra-and-hosts/discover-metrics.md
• solutions/observability/synthetics/cli.md
• solutions/observability/synthetics/configure-lightweight-monitors.md
• solutions/observability/synthetics/configure-projects.md
• solutions/security/ai/attack-discovery.md
• solutions/security/ai/ease/ease-intro.md
• solutions/security/ai/identify-investigate-document-threats.md
• solutions/security/dashboards/data-quality-dashboard.md
• solutions/security/detect-and-alert.md
• solutions/security/detect-and-alert/add-detection-alerts-to-cases.md
• solutions/security/detect-and-alert/create-detection-rule.md
• solutions/security/detect-and-alert/cross-cluster-search-detection-rules.md
• solutions/security/detect-and-alert/manage-detection-alerts.md
• solutions/security/detect-and-alert/manage-detection-rules.md
• solutions/security/detect-and-alert/reduce-notifications-alerts.md
• solutions/security/detect-and-alert/using-logsdb-index-mode-with-elastic-security.md
• solutions/security/get-started/elastic-security-requirements.md
• solutions/security/get-started/elastic-security-ui.md
• solutions/security/get-started/get-started-detect-with-siem.md
• solutions/security/investigate.md
• solutions/security/investigate/indicators-of-compromise.md
• solutions/security/investigate/timeline.md
• solutions/security/security-serverless-feature-tiers.md
• troubleshoot/elasticsearch/mapping-explosion.md
• troubleshoot/elasticsearch/task-queue-backlog.md
• troubleshoot/kibana/alerts.md
• explore-analyze/alerting/alerts.md
• explore-analyze/alerting/alerts/alerting-common-issues.md
• explore-analyze/alerting/alerts/alerting-getting-started.md
• explore-analyze/alerting/alerts/alerting-setup.md
• explore-analyze/alerting/alerts/alerting-troubleshooting.md
• explore-analyze/alerting/alerts/create-manage-rules.md
• explore-analyze/alerting/alerts/event-log-index.md
• explore-analyze/alerting/alerts/geo-alerting.md
• explore-analyze/alerting/alerts/maintenance-windows.md

_{In total, 148 files changed.}

[benironside]

Look good to me! Left a couple of comments but general thoughts: it's great to see the cases content go solution-agnostic. Security content also looks good despite my question about how to organize it into different vs. one page.

[benironside]

Maybe this is perfect and these are the two pages we want to emphasize, but reading this I wondered if we might want to link to more content from this section.

[benironside]

e.g. "Manage Cases" etc

[nastasha-solomon]

yeah, let me see if there's a way to expand this section to provide more pathways for users

[nastasha-solomon]

@benironside how's this?