Update the docs about lua_ls

README.md

@@ -280,11 +280,6 @@ sudo pacman -S --noconfirm --needed gcc make git ripgrep fd tree-sitter-cli unzi
 
 <details><summary>Alpine Install Steps</summary>
 
-> [!CAUTION]
-> Neovim works fine on Alpine, but some tooling appears incompatible with musl
-> (lua-language-server, etc., check `:Mason` or `:MasonLog`).
-> Quickfix Lua-LSP-Support: `:%s/lua_ls/emmylua_ls`
-
 ```shell
 sudo apk add gcc make git fd ripgrep tree-sitter-cli unzip bash gzip curl musl-dev neovim-doc neovim
 ```

init.lua

@@ -639,7 +639,7 @@ do
   -- and language tooling communicate in a standardized fashion.
   --
   -- In general, you have a "server" which is some tool built to understand a particular
-  -- language (such as `gopls`, `lua_ls`, `rust_analyzer`, etc.). These Language Servers
+  -- language (such as `gopls`, `emmylua_ls`, `rust_analyzer`, etc.). These Language Servers
   -- (sometimes called LSP servers, but that's kind of like ATM Machine) are standalone
   -- processes that communicate with some "client" - in this case, Neovim!
   --
@@ -790,7 +790,7 @@ do
   -- Automatically install LSPs and related tools to stdpath for Neovim
   require('mason').setup {}
 
-  -- Translates between nvim-lspconfig server names and mason.nvim package names (e.g. lua_ls <-> lua-language-server)
+  -- Translates between nvim-lspconfig server names and mason.nvim package names (e.g. yaml_ls <-> yaml-language-server)
   require('mason-lspconfig').setup {
     automatic_enable = false, -- Change this to true if you want to automatically enable servers that are installed manually (e.g. via :Mason / :MasonInstall)
   }