Просмотр исходного кода

fix some typos (#1444)

Signed-off-by: cui fliter <imcusg@gmail.com>
cui fliter 3 лет назад
Родитель
Сommit
e8206bf4bf

+ 1 - 1
explorer/fuzzing/ast_to_proto_test.cpp

@@ -97,7 +97,7 @@ auto GetUnusedFields(const Message& message) -> std::set<std::string> {
 }
 }
 
 
 // A 'smoke' test to check that each field present in `carbon.proto` is set at
 // A 'smoke' test to check that each field present in `carbon.proto` is set at
-// least once after converting all Carbon test sources to proto represention.
+// least once after converting all Carbon test sources to proto representation.
 TEST(AstToProtoTest, SetsAllProtoFields) {
 TEST(AstToProtoTest, SetsAllProtoFields) {
   Carbon::Fuzzing::CompilationUnit merged_proto;
   Carbon::Fuzzing::CompilationUnit merged_proto;
   for (const llvm::StringRef f : *carbon_files) {
   for (const llvm::StringRef f : *carbon_files) {

+ 1 - 1
explorer/testdata/pointer/heap_alloc_lifetime.carbon

@@ -11,7 +11,7 @@
 
 
 package ExplorerTest api;
 package ExplorerTest api;
 
 
-// The lifetime of a heap-allocated object is until it is explicitely
+// The lifetime of a heap-allocated object is until it is explicitly
 // deleted. Its lifetime is unrelated to the procedure call stack.
 // deleted. Its lifetime is unrelated to the procedure call stack.
 
 
 fn AllocateInteger() -> i32* {
 fn AllocateInteger() -> i32* {

+ 1 - 1
proposals/p0044.md

@@ -972,7 +972,7 @@ issues, the process is more light-weight without them.
 
 
 ### Rationale for pushing high-level comments to GitHub
 ### Rationale for pushing high-level comments to GitHub
 
 
-While opinions were not as strong, reasons given for perferring comments in
+While opinions were not as strong, reasons given for preferring comments in
 GitHub:
 GitHub:
 
 
 -   This flow will maximize the alignment with “normal” GitHub development flow.
 -   This flow will maximize the alignment with “normal” GitHub development flow.

+ 1 - 1
proposals/p0140.md

@@ -85,4 +85,4 @@ Disadvantages:
 
 
 Conversion of Markdown to another language at a later point (either manually or
 Conversion of Markdown to another language at a later point (either manually or
 using a tool like Sphinx) is expected to remain a relatively low-cost option,
 using a tool like Sphinx) is expected to remain a relatively low-cost option,
-due to the relative simplicitly of Markdown-formatted documents.
+due to the relative simplicity of Markdown-formatted documents.

+ 1 - 1
proposals/p0555.md

@@ -185,7 +185,7 @@ operator to the other, precedences monotonically increase, so by transitivity of
 the precedence partial ordering, the ancestor operator has lower precedence than
 the precedence partial ordering, the ancestor operator has lower precedence than
 the descendent operator.
 the descendent operator.
 
 
-An operator precedence parser with a partial ordering of predecence levels
+An operator precedence parser with a partial ordering of precedence levels
 [has been implemented](https://github.com/carbon-language/carbon-lang/commit/b8afadb3c6af5e68192d585232fee759180ea1e3)
 [has been implemented](https://github.com/carbon-language/carbon-lang/commit/b8afadb3c6af5e68192d585232fee759180ea1e3)
 as a proof-of-concept in the Carbon toolchain.
 as a proof-of-concept in the Carbon toolchain.
 
 

+ 1 - 1
toolchain/parser/parse_tree.h

@@ -328,7 +328,7 @@ class ParseTree::PostorderIterator
   Node node_;
   Node node_;
 };
 };
 
 
-// A forward iterator across the silbings at a particular level in the parse
+// A forward iterator across the siblings at a particular level in the parse
 // tree. It produces `ParseTree::Node` objects which are opaque handles and must
 // tree. It produces `ParseTree::Node` objects which are opaque handles and must
 // be used in conjunction with the `ParseTree` itself.
 // be used in conjunction with the `ParseTree` itself.
 //
 //