kc3-lang/md4c

diff --git a/CHANGELOG.md b/CHANGELOG.md
index e151808..0114eb8 100644
--- a/CHANGELOG.md
+++ b/CHANGELOG.md
@@ -42,7 +42,7 @@ Fixes:
    was incomplete and one corner case remained unfixed. This is now addressed.
 
  - [#231](https://github.com/mity/md4c/issues/231):
-   `md2html --full-html` now emits `<meta  charset="UTF-8">` in the HTML header.
+   `md2html --full-html` now emits `<meta charset="UTF-8">` in the HTML header.
 
 
 ## Version 0.5.1
diff --git a/README.md b/README.md
index 79ced33..2c8ed26 100644
--- a/README.md
+++ b/README.md
@@ -219,9 +219,9 @@ language) are full DOM-like parsers: They construct abstract syntax tree (AST)
 representation of the whole Markdown document. That takes time and it leads to
 bigger memory footprint.
 
-Build AST is completely fine as long as you really need it. If you don't need
-it, there is a very high chance that using MD4C will be substantially faster
-and less hungry in terms of memory consumption.
+Building AST is completely fine as long as you need it. If you don't, there is
+a very high chance that using MD4C will be substantially faster and less hungry
+in terms of memory consumption.
 
 Last but not least, some Markdown parsers are implemented in a naive way. When
 fed with a [smartly crafted input pattern](test/pathological_tests.py), they
diff --git a/src/md4c.c b/src/md4c.c
index 4a4e401..a56204e 100644
--- a/src/md4c.c
+++ b/src/md4c.c
@@ -986,7 +986,7 @@ struct MD_UNICODE_FOLD_INFO_tag {
  * line breaks with given replacement character.
  *
  * NOTE: Caller is responsible to make sure the buffer is large enough.
- * (Given the output is always shorter then input, (end - beg) is good idea
+ * (Given the output is always shorter than input, (end - beg) is good idea
  * what the caller should allocate.)
  */
 static void