1 files changed, 2 insertions, 3 deletions
diff --git a/docs/dev/README.md b/docs/dev/README.md
index 0f64d7e5f..2f6215d6b 100644
--- a/docs/dev/README.md
+++ b/docs/dev/README.md
@@ -124,9 +124,8 @@ Logging is done by both rust-analyzer and VS Code, so it might be tricky to
 figure out where logs go.
 Inside rust-analyzer, we use the standard `log` crate for logging, and
-`flexi_logger` for logging frotend. By default, log goes to stderr (the same as
+`env_logger` for logging frontend. By default, log goes to stderr, but the
-with `env_logger`), but the stderr itself is processed by VS Code. To mirror
+stderr itself is processed by VS Code.
-logs to a `./log` directory, set `RA_LOG_DIR=1` environmental variable.
 To see stderr in the running VS Code instance, go to the "Output" tab of the
 panel and select `rust-analyzer`. This shows `eprintln!` as well. Note that

diff --git a/docs/dev/README.md b/docs/dev/README.md index 0f64d7e5f..2f6215d6b 100644 --- a/docs/dev/README.md +++ b/docs/dev/README.md
@@ -124,9 +124,8 @@ Logging is done by both rust-analyzer and VS Code, so it might be tricky to
124	figure out where logs go.	124	figure out where logs go.
125		125
126	Inside rust-analyzer, we use the standard `log` crate for logging, and	126	Inside rust-analyzer, we use the standard `log` crate for logging, and
127	`flexi_logger` for logging frotend. By default, log goes to stderr (the same as	127	`env_logger` for logging frontend. By default, log goes to stderr, but the
128	with `env_logger`), but the stderr itself is processed by VS Code. To mirror	128	stderr itself is processed by VS Code.
129	logs to a `./log` directory, set `RA_LOG_DIR=1` environmental variable.
130		129
131	To see stderr in the running VS Code instance, go to the "Output" tab of the	130	To see stderr in the running VS Code instance, go to the "Output" tab of the
132	panel and select `rust-analyzer`. This shows `eprintln!` as well. Note that	131	panel and select `rust-analyzer`. This shows `eprintln!` as well. Note that