Skip to content

Commit f5d20b6

Browse files
Fix Typos on guide.md
1 parent 4d33cdc commit f5d20b6

File tree

1 file changed

+4
-4
lines changed

1 file changed

+4
-4
lines changed

docs/dev/guide.md

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -26,7 +26,7 @@ properties hold:
2626

2727
## IDE API
2828

29-
To see the bigger picture of how the IDE features works, let's take a look at the [`AnalysisHost`] and
29+
To see the bigger picture of how the IDE features work, let's take a look at the [`AnalysisHost`] and
3030
[`Analysis`] pair of types. `AnalysisHost` has three methods:
3131

3232
* `default()` for creating an empty analysis instance
@@ -131,7 +131,7 @@ mapping between `SourceRoot` IDs (which are assigned by the client) and actual
131131
analyzer.
132132

133133
Note that `mod`, `#[path]` and `include!()` can only reference files from the
134-
same source root. It is of course is possible to explicitly add extra files to
134+
same source root. It is of course possible to explicitly add extra files to
135135
the source root, even `/dev/random`.
136136

137137
## Language Server Protocol
@@ -192,7 +192,7 @@ task will be canceled as soon as the main loop calls `apply_change` on the
192192
[`schedule`]: https://github.com/rust-analyzer/rust-analyzer/blob/guide-2019-01/crates/ra_lsp_server/src/main_loop.rs#L426-L455
193193
[The task]: https://github.com/rust-analyzer/rust-analyzer/blob/guide-2019-01/crates/ra_lsp_server/src/main_loop/handlers.rs#L205-L223
194194

195-
This concludes the overview of the analyzer's programing *interface*. Next, lets
195+
This concludes the overview of the analyzer's programing *interface*. Next, let's
196196
dig into the implementation!
197197

198198
## Salsa
@@ -480,7 +480,7 @@ throughout the analyzer:
480480
## Source Map pattern
481481

482482
Due to an obscure edge case in completion, IDE needs to know the syntax node of
483-
an use statement which imported the given completion candidate. We can't just
483+
a use statement which imported the given completion candidate. We can't just
484484
store the syntax node as a part of name resolution: this will break
485485
incrementality, due to the fact that syntax changes after every file
486486
modification.

0 commit comments

Comments
 (0)