[DOCS] Move machine learning results definitions into APIs #50257
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.
This PR adds tagged sections that contain descriptions of the machine learning results resource properties. It removes the results resource definitions page (https://www.elastic.co/guide/en/elasticsearch/reference/master/ml-results-resource.html) and uses the shared tagged sections to put that information directly into the appropriate APIs.
NOTE: As a result of these changes, users no longer need to flip between the results resource page and the API pages to find all the necessary details. However, from a maintenance stand-point, it means that when parameters or properties are added or removed, each of the affected APIs' pages must be updated appropriately.
Preview: