about summary refs log tree commit diff
path: root/src/doc/rustc-dev-guide
diff options
context:
space:
mode:
authorYuki Okushi <huyuumi.dev@gmail.com>2020-08-03 11:53:26 +0900
committerWho? Me?! <mark-i-m@users.noreply.github.com>2020-08-02 23:16:01 -0500
commitb71885e14eaf02a46fc821c40ed42e1fdcc1a484 (patch)
tree7807031928bf3ba84774eb965b78aaae1e5e2b66 /src/doc/rustc-dev-guide
parent2aa21b8d793d8ac71edc14a25080f4c82e88af33 (diff)
downloadrust-b71885e14eaf02a46fc821c40ed42e1fdcc1a484.tar.gz
rust-b71885e14eaf02a46fc821c40ed42e1fdcc1a484.zip
Prefer `::` than `.`
Diffstat (limited to 'src/doc/rustc-dev-guide')
-rw-r--r--src/doc/rustc-dev-guide/src/overview.md8
1 files changed, 4 insertions, 4 deletions
diff --git a/src/doc/rustc-dev-guide/src/overview.md b/src/doc/rustc-dev-guide/src/overview.md
index 9d8dfd908ee..e97fba6b9cc 100644
--- a/src/doc/rustc-dev-guide/src/overview.md
+++ b/src/doc/rustc-dev-guide/src/overview.md
@@ -38,11 +38,11 @@ we'll talk about that later.
   data which are emitted in `librustc_parse::lexer::mod` as real diagnostics.
 - The lexer preserves full fidelity information for both IDEs and proc macros.
 - The parser [translates the token stream from the lexer into an Abstract Syntax
-  Tree (AST)][parser].  It uses a recursive descent (top-down) approach to syntax
-  analysis. The crate entry points for the parser are the `Parser.parse_crate_mod()` and
-  `Parser.parse_mod()` methods found in `librustc_parse::parser::item`. The external
+  Tree (AST)][parser]. It uses a recursive descent (top-down) approach to syntax
+  analysis. The crate entry points for the parser are the `Parser::parse_crate_mod()` and
+  `Parser::parse_mod()` methods found in `librustc_parse::parser::item`. The external
   module parsing entry point is `librustc_expand::module::parse_external_mod`. And
-  the macro parser entry point is [`Parser.parse_nonterminal()`][parse_nonterminal].
+  the macro parser entry point is [`Parser::parse_nonterminal()`][parse_nonterminal].
 - Parsing is performed with a set of `Parser` utility methods including `fn bump`,
   `fn check`, `fn eat`, `fn expect`, `fn look_ahead`.
 - Parsing is organized by the semantic construct that is being parsed. Separate