[docgen] Update README.md

skip-checks: true

1 files changed, 2 insertions, 1 deletions

diff --git a/doc/lspconfig.txt b/doc/lspconfig.txt
index 3294ffc2..a53e40f7 100644
--- a/doc/lspconfig.txt
+++ b/doc/lspconfig.txt
@@ -174,7 +174,8 @@ server attaches to the current buffer.
 8. Debugging                                             *lspconfig-debugging*
 
 
-The two most common reasons a language server does not start or attach are:
+If you have an issue with lspconfig, the first step is to reproduce with a [minimal configuration](https://github.com/neovim/nvim-lspconfig/blob/master/test/minimal_init.lua).
+The most common reasons a language server does not start or attach are:
 1. The language server is not installed. nvim-lspconfig does not install language servers for you. You should be able to run the `cmd` defined in each server's lua module from the command line and see that the language server starts. If the `cmd` is an executable name, ensure it is on your path.
 2. Not triggering root detection. The language server will only start if it is opened in a directory, or child directory, containing a file which signals the *root* of the project. Most of the time, this is a `.git` folder, but each server defines the root config in the lua file. See [CONFIG.md](CONFIG.md) or the source for the list of root directories.
 3. Misconfiguration. You must pass `on_attach` and `capabilities` for **each** `setup {}` if you want these to take effect. You must also **not call `setup {}` twice for the same server**. The second call to `setup {}` will overwrite the first.