Update a few phrases for mise install

[erickguan]

A minor effort in updating the doc. I can see more venues for improvements on:

• mentioning more UX features.
• clarifying what the default tool's version

I will leave it to future work for now. Perhaps soon!

The text should be more intuitive for my understanding on #1711

[jdx]

Suggested change

	`install` will install a tool version to `~/.local/share/mise/installs/<PLUGIN>/<VERSION>`
	Installs a tool version to `~/.local/share/mise/installs/<PLUGIN>/<VERSION>`

[jdx]

Suggested change

	Another way is to use a tool explicitly with `mise exec <TOOL>@<VERSION> -- <COMMAND>`.
	Alternatively, run `mise exec <TOOL>@<VERSION> -- <COMMAND>` to execute a tool without creating config files.

[jdx]

Suggested change

	Tools are inactive without being enabled, however.
	Installing alone will not activate the tools so they won't be in PATH.

I'm a little uncomfortable with this language since it still will create shims, so shim users will have it in PATH but the shims won't work. I think that this language does make sense for the majority of users though and that subtle behavior difference won't make any practical difference since the way shims behave is if they're not active it falls back to the system bin (if any). So it behaves basically as if it "wasn't in PATH".

[erickguan]

Good point!

[jdx]

Suggested change

	To enable a tool, set up a `.mise.toml`/`.tool-version` file or `mise use`.
	To install and/or activate in one command, use `mise use` which will create a `.mise.toml` file in the current directory to activate this tool when inside the directory.

[jdx]

Suggested change

	Show installation output. This argument will print plugins' logs.
	When plugin downloads assets, mise will show download logs.
	When plugin configures and compiles tools, mise will show configuration and compilation logs.
	Show installation output.
	This argument will print plugin output such as download, configuration, and compilation output.

[jdx]

so I really appreciate your attention on this. I agree that this language can be improved (like a lot of stuff in mise). Apologies if some of my feedback seems nitpicky. I'm trying to be careful about being consistent and using "activated" instead of "enabled" everywhere I describe this behavior.

Unfortunately this isn't the right place to make this change. This file is autogenerated, you'll need to make these changes in this file's comments instead. Then on the next release this markdown file will be updated.

[erickguan]

Thanks for your review. I would guess the doc comes from a script but I didn't browser through code yet. Writing a PR is probably better than forgetting about it after getting your help (from an issue).

mise is a nice tool. I am using it instead of asdf. I understand the consistency you want to achieve. I respect the effort you had put into mise already. The next patch will be better!

[erickguan]

Good point!