Fix instructions for .lsp_symlink workaround

Author: slavistan

README.md

@@ -164,21 +164,25 @@ Use of a python `virtualenv` or a conda env is also recommended.
    or permanently by setting `c.Completer.use_jedi = False` in your
    [`ipython_config.py` file](https://ipython.readthedocs.io/en/stable/config/intro.html?highlight=ipython_config.py#systemwide-configuration).
 
-1. (Optional, Linux/OSX-only) to enable opening files outside of the root
-   directory (the place where you start JupyterLab), create `.lsp_symlink` and
-   symlink your `/home`, or any other location which includes the files that you
-   wish to make possible to open in there:
+1. (Optional; *nix-only) As a security measure Jupyter limits file access to the Jupyter root
+   directory (the place where you launch the Jupyter server). Thus, in order to
+   allow `jupyterlab-lsp` to navigate to external files such as packages
+   installed system-wide or to libraries inside a virtual environment (`conda`,
+   `pip`, ...) this access control mechanism needs to be circumvented: Inside your Jupyter
+   root directory create a symlink named *.lsp_symlink* pointing to your system root */*.
 
-   ```bash
-   mkdir .lsp_symlink
-   cd .lsp_symlink
-   ln -s /home home
-   ```
+    ```
+    ln -s / .lsp_symlink
+    ```
+
+    As this symlink is a hidden file the Jupyter server must be instructed to
+    serve hidden files. Either use the appropriate commandline flag:
+
+    ```
+    jupyter lab --ContentsManager.allow_hidden=True
+    ```
 
-   If your user does not have sufficient permissions to traverse the entire path,
-   you will not be able to open the file. A more detailed guide on symlinking
-   (written for a related jupyterlab-go-to-definition extension) is available
-   [here](https://github.com/krassowski/jupyterlab-go-to-definition/blob/master/README.md#which-directories-to-symlink).
+    or, alternatively, set the corresponding setting inside your *jupyter_server_config.py*.
 
 ### Configuring the servers