d20e8e2bb4
We had been using `task_id:1` or `taskId:1` because it is parses as a valid task identifier but the `:1` part is confusing. This replaces those examples with `task_id` which matches the response from the list tasks API. Closes #28314 |
||
---|---|---|
.. | ||
allocation-explain.asciidoc | ||
health.asciidoc | ||
nodes-hot-threads.asciidoc | ||
nodes-info.asciidoc | ||
nodes-stats.asciidoc | ||
nodes-usage.asciidoc | ||
pending.asciidoc | ||
remote-info.asciidoc | ||
reroute.asciidoc | ||
state.asciidoc | ||
stats.asciidoc | ||
tasks.asciidoc | ||
update-settings.asciidoc |