File tree Expand file tree Collapse file tree 1 file changed +5
-5
lines changed Expand file tree Collapse file tree 1 file changed +5
-5
lines changed Original file line number Diff line number Diff line change @@ -706,15 +706,15 @@ fn find_root(node: &SyntaxNode) -> SyntaxNode {
706
706
/// so, but, generally, this is not something left after the analysis.
707
707
///
708
708
/// 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?".
712
712
///
713
713
/// So `SemanticsScope` is constructed from a specific program point (a syntax
714
714
/// 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.
716
716
///
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 ?",
718
718
/// you'd better use the `resolve_` family of methods.
719
719
#[ derive( Debug ) ]
720
720
pub struct SemanticsScope < ' a > {
You can’t perform that action at this time.
0 commit comments