Skip to content

Commit fcc3c49

Browse files
matkladlnicola
andauthored
Apply suggestions from code review
Co-authored-by: Laurențiu Nicola <[email protected]>
1 parent 8e3082f commit fcc3c49

File tree

1 file changed

+5
-5
lines changed

1 file changed

+5
-5
lines changed

crates/hir/src/semantics.rs

Lines changed: 5 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -706,15 +706,15 @@ fn find_root(node: &SyntaxNode) -> SyntaxNode {
706706
/// so, but, generally, this is not something left after the analysis.
707707
///
708708
/// However, we do very much need explicit scopes for IDE purposes --
709-
/// completion, at its core, lists the contents of the current scope. Notion of
710-
/// scope is also useful to answer question like "what would be the meaning of
711-
/// this piece of code if we insert into this position?".
709+
/// completion, at its core, lists the contents of the current scope. The notion
710+
/// of scope is also useful to answer questions like "what would be the meaning
711+
/// of this piece of code if we inserted it into this position?".
712712
///
713713
/// So `SemanticsScope` is constructed from a specific program point (a syntax
714714
/// node or just a raw offset) and provides access to the set of visible names
715-
/// in on a somewhat best-effort basis.
715+
/// on a somewhat best-effort basis.
716716
///
717-
/// Note that if you are wondering "what this specific existing name means?",
717+
/// Note that if you are wondering "what does this specific existing name mean?",
718718
/// you'd better use the `resolve_` family of methods.
719719
#[derive(Debug)]
720720
pub struct SemanticsScope<'a> {

0 commit comments

Comments
 (0)