[autofix.ci] apply automated fixes

docs/lang/bun.md

@@ -1,9 +1,9 @@
 # Bun
 
-`mise` can be used to install and manage multiple versions of [bun](https://bun.sh/) on the same system. 
+`mise` can be used to install and manage multiple versions of [bun](https://bun.sh/) on the same system.
 
 > The following are instructions for using the bun mise core plugin. This is used when there isn't a
-git plugin installed named "bun".
+> git plugin installed named "bun".
 
 The code for this is inside the mise repository at
 [`./src/plugins/core/bun.rs`](https://github.com/jdx/mise/blob/main/src/plugins/core/bun.rs).

docs/lang/deno.md

@@ -3,8 +3,8 @@
 `mise` can be used to install and manage multiple versions of [deno](https://deno.land/) on the same system.
 
 > The following are instructions for using the deno mise core plugin. This is used when there isn't a
-git plugin installed named "deno". If you want to use [asdf-deno](https://github.com/asdf-community/asdf-deno)
-then run `mise plugins install deno https://github.com/asdf-community/asdf-deno`.
+> git plugin installed named "deno". If you want to use [asdf-deno](https://github.com/asdf-community/asdf-deno)
+> then run `mise plugins install deno https://github.com/asdf-community/asdf-deno`.
 
 The code for this is inside the mise repository at
 [`./src/plugins/core/deno.rs`](https://github.com/jdx/mise/blob/main/src/plugins/core/deno.rs).

docs/lang/erlang.md

@@ -3,7 +3,7 @@
 `mise` can be used to install and manage multiple versions of [erlang](https://www.erlang.org/) on the same system.
 
 > The following are instructions for using the erlang core plugin.
-This is used when there isn't a git plugin installed named "erlang".
+> This is used when there isn't a git plugin installed named "erlang".
 
 The code for this is inside the mise repository at
 [`./src/plugins/core/erlang.rs`](https://github.com/jdx/mise/blob/main/src/plugins/core/erlang.rs).

docs/lang/go.md

@@ -3,8 +3,8 @@
 `mise` can be used to install and manage multiple versions of [go](https://golang.org/) on the same system.
 
 > The following are instructions for using the go mise core plugin. This is used when there isn't a
-git plugin installed named "go". If you want to use [asdf-golang](https://github.com/kennyp/asdf-golang)
-then use `mise plugins install go GIT_URL`.
+> git plugin installed named "go". If you want to use [asdf-golang](https://github.com/kennyp/asdf-golang)
+> then use `mise plugins install go GIT_URL`.
 
 The code for this is inside the mise repository at
 [`./src/plugins/core/go.rs`](https://github.com/jdx/mise/blob/main/src/plugins/core/go.rs).
@@ -49,5 +49,3 @@ github.com/jesseduffield/lazygit
 import Settings from '/components/settings.vue';
 </script>
 <Settings child="go" :level="3" />
-
-

docs/lang/java.md

@@ -3,8 +3,8 @@
 Like `sdkman`, `mise` can manage multiple versions of Java on the same system.
 
 > The following are instructions for using the java mise core plugin. This is used when there isn't a
-git plugin installed named "java".  If you want to use [asdf-java](https://github.com/halcyon/asdf-java)
-then use `mise plugins install java GIT_URL`.
+> git plugin installed named "java". If you want to use [asdf-java](https://github.com/halcyon/asdf-java)
+> then use `mise plugins install java GIT_URL`.
 
 The code for this is inside the mise repository at
 [`./src/plugins/core/java.rs`](https://github.com/jdx/mise/blob/main/src/plugins/core/java.rs).
@@ -31,7 +31,7 @@ See available versions with `mise ls-remote java`. com>.
 
 ::: warning
 Note that shorthand versions (like `21` in the example) use [`OpenJDK`](https://openjdk.org/) as the vendor.
-The OpenJDK versions will only be updated for a 6-month period. Updates and security patches will not be available after this short period. This also applies for LTS versions. 
+The OpenJDK versions will only be updated for a 6-month period. Updates and security patches will not be available after this short period. This also applies for LTS versions.
 
 For more information on which JDK to choose, see <https://whichjdk.com>.
 :::
@@ -56,9 +56,9 @@ The Java core plugin supports the idiomatic version files `.java-version` and `.
 
 For `.sdkmanrc` files, mise will try to map the vendor and version to the appropriate version
 string. For example, the version `20.0.2-tem` will be mapped to `temurin-20.0.2`. Due to Azul's Zulu
-versioning, the version `11.0.12-zulu` will be mapped to the major version `zulu-11`. 
+versioning, the version `11.0.12-zulu` will be mapped to the major version `zulu-11`.
 
-Not all vendors available in [sdkman](https://sdkman.io/jdks) are supported by mise. 
+Not all vendors available in [sdkman](https://sdkman.io/jdks) are supported by mise.
 The following vendors are NOT supported: `bsg` (Bisheng), `graal` (GraalVM), `nik` (Liberica NIK).
 
 ### Using unsupported versions
@@ -112,12 +112,12 @@ are supported:
 
 ## Gradle toolchains detection
 
-Gradle can automatically detect toolchains installed by some tools (see [toolchain | auto-detection](https://docs.gradle.org/current/userguide/toolchains.html#sec:auto_detection)). 
+Gradle can automatically detect toolchains installed by some tools (see [toolchain | auto-detection](https://docs.gradle.org/current/userguide/toolchains.html#sec:auto_detection)).
 
 At the moment, `Gradle` does not support auto-detecting Java installations by `mise` (see [gradle/issues/29508](https://github.com/gradle/gradle/issues/29508) and [gradle/issues/29355](https://github.com/gradle/gradle/issues/29355)). A workaround is to leverage the fact that `mise` install layout is [similar to the one used by `asdf`](/ide-integration.html#sdk-selection-using-asdf-layout).
 
 ```shell
 mkdir -p ~/.asdf/installs/ && ln -s ~/.local/share/mise/installs/java ~/.asdf/installs/
 ```
 
-Otherwise, you can always use the [foojay-resolver-convention](https://plugins.gradle.org/plugin/org.gradle.toolchains.foojay-resolver-convention) plugin to let Gradle automatically install JDKs required by your project.
+Otherwise, you can always use the [foojay-resolver-convention](https://plugins.gradle.org/plugin/org.gradle.toolchains.foojay-resolver-convention) plugin to let Gradle automatically install JDKs required by your project.

docs/lang/node.md

@@ -3,9 +3,9 @@
 Like `nvm`, (or `volta`, `fnm` or `asdf`...), `mise` can manage multiple versions of Node.js on the same system.
 
 > The following are instructions for using the node mise core plugin. This is used when there isn't a
-git plugin installed named "node".
+> git plugin installed named "node".
 > If you want to use [asdf-nodejs](https://github.com/asdf-vm/asdf-nodejs)
-then run `mise plugins install node https://github.com/asdf-vm/asdf-nodejs`
+> then run `mise plugins install node https://github.com/asdf-vm/asdf-nodejs`
 
 The code for this is inside the mise repository at [`./src/plugins/core/node.rs`](https://github.com/jdx/mise/blob/main/src/plugins/core/node.rs).
 
@@ -20,12 +20,11 @@ mise use -g node@20
 
 See the [Node.JS Cookbook](/mise-cookbook/nodejs.html) for common tasks and examples.
 
-
 ## `.nvmrc` and `.node-version` support
 
 By default, mise uses a `mise.toml` file for auto-switching between software versions.
 
-It also supports `.tool-versions`, `.nvmrc` or `.node-version` file to find out what version of Node.js should be used. This will be used if `node` isn't defined in `mise.toml`. 
+It also supports `.tool-versions`, `.nvmrc` or `.node-version` file to find out what version of Node.js should be used. This will be used if `node` isn't defined in `mise.toml`.
 
 This makes it a drop-in replacement for `nvm`. See [idiomatic version files](/configuration.html#idiomatic-version-files) for more information.
 
@@ -47,7 +46,6 @@ You cannot install/use a plugin named "nodejs". If you attempt this, mise will j
 "node". See the [FAQ](/faq.html#what-is-the-difference-between-nodejs-and-node-or-golang-and-go)
 for an explanation.
 
-
 ## Building from source
 
 If compiling from source, see [BUILDING.md](https://github.com/nodejs/node/blob/main/BUILDING.md#building-nodejs-on-supported-platforms) in node's documentation for
@@ -102,4 +100,4 @@ import Settings from '/components/settings.vue';
 
 ::: info
 These environment variables will be migrated to compatible settings in the future.
-:::
+:::

docs/lang/python.md

@@ -3,8 +3,8 @@
 Like `pyenv`, `mise` can manage multiple versions of Python on the same system. Mise can also automatically create virtual environments for your projects and integrates with `uv`.
 
 > The following are instructions for using the python mise core plugin. The core plugin will be used
-so long as no plugin is manually
-installed named "python" using `mise plugins install python [GIT_URL]`.
+> so long as no plugin is manually
+> installed named "python" using `mise plugins install python [GIT_URL]`.
 
 The code for this is inside of the mise repository
 at [`./src/plugins/core/python.rs`](https://github.com/jdx/mise/blob/main/src/plugins/core/python.rs).

docs/lang/ruby.md

@@ -3,8 +3,8 @@
 Like `rvm`, `rbenv`, or `asdf`, `mise` can manage multiple versions of [Ruby](https://www.ruby-lang.org/) on the same system.
 
 > The following are instructions for using the ruby mise core plugin. This is used when there isn't a
-git plugin installed named "ruby".  If you want to use [asdf-ruby](https://github.com/asdf-vm/asdf-ruby)
-then use `mise plugins install ruby GIT_URL`.
+> git plugin installed named "ruby". If you want to use [asdf-ruby](https://github.com/asdf-vm/asdf-ruby)
+> then use `mise plugins install ruby GIT_URL`.
 
 The code for this is inside the mise repository at
 [`./src/plugins/core/ruby.rs`](https://github.com/jdx/mise/blob/main/src/plugins/core/ruby.rs).
@@ -24,7 +24,6 @@ from source. Ensure that you have the necessary
 You can check its [README](https://github.com/rbenv/ruby-build/blob/master/README.md) for additional settings and some
 troubleshooting.
 
-
 ## Default gems
 
 mise can automatically install a default set of gems right after installing a new ruby version.
@@ -61,6 +60,7 @@ update:
 mise cache clean
 mise ls-remote ruby
 ```
+
 ## Settings
 
 `ruby-build` already has a