1 files changed, 2 insertions, 2 deletions
diff --git a/docs/dev/README.md b/docs/dev/README.md
index 51cf716b3..33829c593 100644
--- a/docs/dev/README.md
+++ b/docs/dev/README.md
@@ -92,11 +92,11 @@ This is primarily useful for performance optimizations, or for bug minimization.
 ## Parser Tests
-Tests for the parser (`ra_parser`) live in the `ra_syntax` crate (see `test_data` directory).
+Tests for the parser (`parser`) live in the `ra_syntax` crate (see `test_data` directory).
 There are two kinds of tests:
 * Manually written test cases in `parser/ok` and `parser/err`
-* "Inline" tests in `parser/inline` (these are generated) from comments in `ra_parser` crate.
+* "Inline" tests in `parser/inline` (these are generated) from comments in `parser` crate.
 The purpose of inline tests is not to achieve full coverage by test cases, but to explain to the reader of the code what each particular `if` and `match` is responsible for.
 If you are tempted to add a large inline test, it might be a good idea to leave only the simplest example in place, and move the test to a manual `parser/ok` test.

diff --git a/docs/dev/README.md b/docs/dev/README.md index 51cf716b3..33829c593 100644 --- a/docs/dev/README.md +++ b/docs/dev/README.md
@@ -92,11 +92,11 @@ This is primarily useful for performance optimizations, or for bug minimization.
92		92
93	## Parser Tests	93	## Parser Tests
94		94
95	Tests for the parser (`ra_parser`) live in the `ra_syntax` crate (see `test_data` directory).	95	Tests for the parser (`parser`) live in the `ra_syntax` crate (see `test_data` directory).
96	There are two kinds of tests:	96	There are two kinds of tests:
97		97
98	* Manually written test cases in `parser/ok` and `parser/err`	98	* Manually written test cases in `parser/ok` and `parser/err`
99	* "Inline" tests in `parser/inline` (these are generated) from comments in `ra_parser` crate.	99	* "Inline" tests in `parser/inline` (these are generated) from comments in `parser` crate.
100		100
101	The purpose of inline tests is not to achieve full coverage by test cases, but to explain to the reader of the code what each particular `if` and `match` is responsible for.	101	The purpose of inline tests is not to achieve full coverage by test cases, but to explain to the reader of the code what each particular `if` and `match` is responsible for.
102	If you are tempted to add a large inline test, it might be a good idea to leave only the simplest example in place, and move the test to a manual `parser/ok` test.	102	If you are tempted to add a large inline test, it might be a good idea to leave only the simplest example in place, and move the test to a manual `parser/ok` test.