[erlang-ls#553] Move DB info to site/internals, update Slack channel …

…name

README.md

@@ -96,39 +96,17 @@ The `code_reload` takes the following options:
 |-----------|----------------------------------------------------------------------|
 | node | The node to be called for code reloading. Example erlang_ls@hostname |
 
-### The `erlang_ls` Database
-
-The `erlang_ls` language server uses
-[Mnesia](https://erlang.org/doc/man/mnesia.html) to persist
-information. A new database is created and maintained for each
-project/OTP pair. Databases are stored in the application cache
-directory, which varies according to the operating system used.
-
-Generally speaking, the directory should be:
-
-| Operating System | Database Dir |
-|------------------|----------------------------------------------|
-| Linux | /home/USER/.cache/erlang\_ls |
-| OS X | /Users/USER/Library/Caches/erlang\_ls |
-| Windows | c:/Users/USER/AppData/Local/erlang\_ls/Cache |
-
-You can also run the following command on an Erlang shell to identify
-the Database Directory on your system:
-
- > filename:basedir(user_cache, "erlang_ls").
-
 ## Getting in Touch
 
 If you have any questions about the project, feel free to open a new
-issue. You can also join the `#language-server` channel in the
+issue. You can also join the `#erlang-ls` channel in the
 _Erlanger_ Slack if you would like to get involved or if you prefer a
 more informal mean of communication.
 
 All contributions are welcome, be them in the form of a bug report, a
 question, feedback, or code.
 
-A [wiki](https://github.com/erlang-ls/erlang_ls/wiki) is also
-available and I occasionally blog about the project on
+I occasionally blog about the project on
 [Medium](https://medium.com/about-erlang).
 
 ## References