2 files changed, 9 insertions, 4 deletions

diff --git a/docs/dev/README.md b/docs/dev/README.md
index 24197b332..6bce38e56 100644
--- a/docs/dev/README.md
+++ b/docs/dev/README.md
@@ -43,6 +43,10 @@ https://rust-lang.zulipchat.com/#narrow/stream/185405-t-compiler.2Fwg-rls-2.2E0
   while unactionable ones are effectively wont-fix. Each triaged issue should have one of these labels.
 * [fun](https://github.com/rust-analyzer/rust-analyzer/issues?q=is%3Aopen+is%3Aissue+label%3Afun)
   is for cool, but probably hard stuff.
+* [Design](https://github.com/rust-analyzer/rust-analyzer/issues?q=is%3Aopen+is%3Aissue+label%Design)
+  is for moderate/large scale architecture discussion.
+  Also a kind of fun.
+  These issues should generally include a link to a Zulip discussion thread.
 
 # CI
 
@@ -212,7 +216,7 @@ To log all communication between the server and the client, there are two choice
 
 * you can log on the server side, by running something like
   ```
-  env RA_LOG=gen_lsp_server=trace code .
+  env RA_LOG=lsp_server=debug code .
   ```
 
 * you can log on the client side, by enabling `"rust-analyzer.trace.server":
diff --git a/docs/dev/style.md b/docs/dev/style.md
index 428cee3ad..6dc6868c2 100644
--- a/docs/dev/style.md
+++ b/docs/dev/style.md
@@ -294,8 +294,9 @@ Prefer `Default` even it has to be implemented manually.
 
 **Rationale:** less typing in the common case, uniformity.
 
-Use `Vec::new` rather than `vec![]`. **Rationale:** uniformity, strength
-reduction.
+Use `Vec::new` rather than `vec![]`.
+
+**Rationale:** uniformity, strength reduction.
 
 ## Functions Over Objects
 
@@ -479,7 +480,7 @@ pub fn reachable_nodes(node: Node) -> FxHashSet<Node> {
 }
 ```
 
-**Rational:** re-use allocations, accumulator style is more concise for complex cases.
+**Rationale:** re-use allocations, accumulator style is more concise for complex cases.
 
 # Style