Fix up data stream lifecycle tutorials

[kilfoyle]

A few updates to the DLM tutorials, corresponding to Edu's feedback in https://github.com/elastic/docs-content-internal/issues/190

[benironside]

Not familiar with the content, but LGTM!

[github-actions]

🔍 Preview links for changed docs

• manage-data/lifecycle/data-stream.md
• manage-data/lifecycle/data-stream/tutorial-create-data-stream-with-lifecycle.md
• manage-data/lifecycle/data-stream/tutorial-data-stream-retention.md
• manage-data/lifecycle/data-stream/tutorial-migrate-ilm-managed-data-stream-to-data-stream-lifecycle.md
• manage-data/lifecycle/data-stream/tutorial-update-existing-data-stream.md

[yetanothertw]

I've left one comment which I'm not sure about. Maybe check with Edu just to be on the safe side?

[yetanothertw]

minor typo

Suggested change

	1. In this case the index template will be applied to a data stream named `my-data-stream-test`. You can optionally use a wildcard (`*`) in the index pattern to match all data streams created (either manually or using a an indexing request) that have a name matching the specified pattern.
	1. In this case the index template will be applied to a data stream named `my-data-stream-test`. You can optionally use a wildcard (`*`) in the index pattern to match all data streams created (either manually or using an indexing request) that have a name matching the specified pattern.

It's interesting that I actually interpreted Edu's feedback on this differently. I think he was okay with the API example (for creating the index template) using the ["my-data-stream*"] index pattern, and suggesting we changed the index name in the Create a data stream section to my-data-stream-test and then explain that this name works because of the wildcard used in the index template.
I thought it's preferable to use the wildcard in the template, because it would make the template more "universal" (broader scope of use).

Wdyt? Does any of this make sense? (I could also be totally wrong about this 🙈)

[kilfoyle]

@yetanothertw Thanks for asking about this. I looked at the recording just now to confirm. It's at the "Create an index template" section (42:00) that Edu says the asterisk creates misunderstanding for users. Here's what he highlighted in the document while talking about that issue:

[kilfoyle]

I fixed the typo. Thanks for catching that!

[yetanothertw]

Cool, it's very likely I misunderstood :)

[yetanothertw]

LGTM 🚀