Update with a better UX plugin

Author: RossSmyth

src/building/suggested.md

@@ -56,20 +56,14 @@ you can write: <!-- date-check: nov 2022 --><!-- the date comment is for the edi
 in your `.vscode/settings.json` file. This will ask `rust-analyzer` to use
 `./x.py check` to check the sources, and the stage 0 rustfmt to format them.
 
+There are several ways for configuring neovim for rustc. The easiest way is to use the plugin 
+[neoconf.nvim](https://github.com/folke/neoconf.nvim/), which is compatible with VSCode (and 
+other) config formats. To manage configuration files use the `:Neoconf local` command.
 
-For Neovim users there are several options for configuring for rustc. The easiest way is by using 
-[nlsp-settings](https://github.com/tamago324/nlsp-settings.nvim), which allows for project-local
-configuration files with the native LSP. The steps for how to use it are below.
-
-1. First install the plugin
-2. Run `:LspSettings local rust_analyzer` while the rust repo is open.
-
-This will create and open a JSON file to put the above JSON in.
-
-3. Open a Rust buffer that causes Rust Analyzer to attach.
-4. Run `:LspSettings update rust_analyzer` 
-
-The final step must be repeated every time you open Neovim after you open a Rust buffer.
+If you're running `coc.nvim`, you can use `:CocLocalConfig` to create a
+`.vim/coc-settings.json` and enter the same settings as above, but replacing
+`editor.formatOnSave: true,` with
+`"coc.preferences.formatOnSaveFiletypes": ["rust"],`.
 
 Another way is without a plugin, and creating your own logic in your configuration. The required 
 Lua for doing so is below.
@@ -107,11 +101,6 @@ Lua for doing so is below.
 }
 ```
 
-If you're running `coc.nvim`, you can use `:CocLocalConfig` to create a
-`.vim/coc-settings.json` and enter the same settings as above, but replacing
-`editor.formatOnSave: true,` with
-`"coc.preferences.formatOnSaveFiletypes": ["rust"],`.
-
 If you have enough free disk space and you would like to be able to run `x.py` commands while
 rust-analyzer runs in the background, you can also add `--build-dir build-rust-analyzer` to the
 `overrideCommand` to avoid x.py locking.