Commit 12f7d3c

HPCesia <me@hpcesia.com>
2025-02-11 09:18:05
docs: fix grammar mistakes
1 parent d9df39d
Changed files (3)
src/content/posts/manual.md
@@ -1,5 +1,5 @@
 ---
-title: Maunal
+title: Manual
 slug: '12345678'
 published: 2025-01-16T22:01:22+08:00
 category: Guide
src/content/posts/Markdown-Extensions.md
@@ -24,7 +24,7 @@ And to create this:sup[:a[1]{#fake-footnote-here data-footnote-ref href="#fake-f
 And to create this:sup[:a[1]{#fake-footnote-here data-footnote-ref href="#fake-footnote-there"}], you can use the following markdown:
 
 ```markdown
-A infinite loop! So there is no need to write the markdown code again and again here.
+An infinite loop! So there is no need to write the markdown code again and again here.
 ```
 
 :a[1: fake footnote here.]{#fake-footnote-there data-footnote-backref href="#fake-footnote-here"}
@@ -50,9 +50,9 @@ Instead of using HTML comments:
 
 ## Components
 
-Using directives, you can write HTML with markdown inside. But to generate complex components, it's a bit tedious, not elegant, and not easy to maintain, it's another hell of HTML tags[^1]. Fortunately, with [rehype-components](https://github.com/marekweb/rehype-components), you can use pre-defined components in markdown files.
+Using directives, you can write HTML with markdown inside. But to generate complex components, it's a bit tedious, not elegant, and not easy to maintain. It's another hell of HTML tags[^1]. Fortunately, with [rehype-components](https://github.com/marekweb/rehype-components), you can use pre-defined components in markdown files.
 
-[^1]: If you want to know how hell it is, check the [source code](https://github.com/HPCesia/astral-halo/tree/master/src/content/posts/Markdown-Extensions.md) of this post.
+[^1]: If you want to know how hellish it is, check the [source code](https://github.com/HPCesia/astral-halo/tree/master/src/content/posts/Markdown-Extensions.md) of this post.
 
 ### Tabs
 
src/content/posts/markdown.md
@@ -11,7 +11,7 @@ tags:
 
 Here is an example of a Markdown blog post.
 
-# Heading Level 1 (I Suggest That DO NOT Use This Level)
+# Heading Level 1 (I suggest not to use this level)
 
 Heading Level 1 is reserved for the post title, so you should start with Heading Level 2.
 
@@ -28,7 +28,7 @@ You can use GitHub Flavored Markdown to format your blog posts. For example, you
 
 ![Example Image](../../assets/img/avatar.jpg)
 
-common Markdown features like:
+Common Markdown features like:
 
 - Lists
   - Nested lists