fix: typos in comments

unimarkup · Jul 31, 2022 · d44505c · d44505c
1 parent 2a1723c
commit d44505c
Show file tree

Hide file tree

Showing 4 changed files with 6 additions and 6 deletions.
diff --git a/inline/src/inlines/content.rs b/inline/src/inlines/content.rs
@@ -107,7 +107,7 @@ impl PlainContent {
         self.content.clone()
     }
 
-    /// Returns the lenght of the content.
+    /// Returns the length of the content.
     pub fn content_len(&self) -> usize {
         self.content.len()
     }
@@ -199,7 +199,7 @@ impl InlineContent<PlainContent, NestedContent> {
         self.set_span(Span::from((start, end)));
     }
 
-    /// Apends an [`Inline`] to this content.
+    /// Appends an [`Inline`] to this content.
     ///
     /// [`Inline`]: self::Inline
     pub fn append_inline(&mut self, inline: Inline) {
@@ -282,7 +282,7 @@ impl InlineContent<PlainContent, NestedContent> {
         }
     }
 
-    /// Returns the lenght of content.
+    /// Returns the length of content.
     pub fn content_len(&self) -> usize {
         match self {
             InlineContent::Plain(plain_content) => plain_content.content_len(),

diff --git a/inline/src/lexer/mod.rs b/inline/src/lexer/mod.rs
@@ -65,7 +65,7 @@ pub(crate) enum Symbol<'a> {
     Backslash,
     /// The start (`*`) literal is used for bold and/or italic formatting.
     Star,
-    /// The underline (`_`) literal is used for undeline and/or subscript formatting.
+    /// The underline (`_`) literal is used for underline and/or subscript formatting.
     Underline,
     /// The caret (`^`) literal is used for superscript formatting.
     Caret,

diff --git a/inline/src/lexer/token.rs b/inline/src/lexer/token.rs
@@ -439,7 +439,7 @@ pub enum TokenKind {
     /// Verbatim delimiter token (`` ` ``).
     Verbatim,
 
-    /// Qotation delimiter token (`""`).
+    /// Quotation delimiter token (`""`).
     Quote,
 
     /// Math delimiter token (`$`).

diff --git a/inline/src/parser/mod.rs b/inline/src/parser/mod.rs
@@ -332,7 +332,7 @@ impl Parser<'_> {
     /// There are three cases:
     /// 1. Opening [`Token`] is not ambiguous, but `next_token` is. In this case, the opening
     ///    [`Token`] will be removed from `next_token`, removed token will be returned and the
-    ///    remaining pairt of `next_token` will be stored into the token cache.
+    ///    remaining part of `next_token` will be stored into the token cache.
     /// 2. Both opening and `next_token` are ambiguous. They will be split into their non-ambiguous
     ///    parts and one part will be returned, and other stored into the token cache.
     /// 3. `next_token` is not ambiguous, so the opening [`Token`] is not relevant. The