(Doc+) Delineate Bootstrapping Data Stream from Alias #107976
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
👋 howdy, team! This is follow-up to [elasticsearch#107327](#107327). I realized my mistake was that we had duplicate sentences in different sections so I edited the wrong area. However, it seemed like a good opportunity to consider clarifying the page better by fixing header links so that the sub-sections reflect as sub-headers instead of all being equal. Thoughts?
stefnestor
added
>enhancement
>docs
|
Documentation preview: |
|
@stefnestor please enable the option "Allow edits and access to secrets by maintainers" on your PR. For more information, see the documentation. |
|
Pinging @elastic/es-docs (Team:Docs) |
elasticsearchmachine
added
v8.15.0
external-contributor
|
Pinging @elastic/es-data-management (Team:Data Management) |
Co-authored-by: shainaraskas <58563081+shainaraskas@users.noreply.github.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
👋 howdy, team!
This is follow-up to elasticsearch#107327. I realized my mistake was that we had duplicate sentences in different sections so I edited the wrong area. (Sorry again.)
However, it seemed like a good opportunity to (A) fill in links & (B) consider clarifying the page better by fixing header links so that the sub-sections reflect as sub-headers instead of all being equal. Applied forward earlier feedback.
Thoughts? cc: @dakrone