codespell

docs/src/new-in-miller-6.md

@@ -84,7 +84,7 @@ For `mlr put` and `mlr filter`, parse-error messages now include location inform
 
 <pre class="pre-non-highlight-non-pair">
 mlr: cannot parse DSL expression.
-Parse error on token ">" at line 63 columnn 7.
+Parse error on token ">" at line 63 column 7.
 </pre>
 
 ### Scripting

docs/src/new-in-miller-6.md.in

@@ -68,7 +68,7 @@ For `mlr put` and `mlr filter`, parse-error messages now include location inform
 
 GENMD-CARDIFY
 mlr: cannot parse DSL expression.
-Parse error on token ">" at line 63 columnn 7.
+Parse error on token ">" at line 63 column 7.
 GENMD-EOF
 
 ### Scripting

docs/src/reference-dsl-output-statements.md

@@ -342,7 +342,7 @@ JSON vs. tabular formats](flatten-unflatten.md) for more information.
 The reason for this is part historical and part technical. As we'll see below,
 you can do lots of syntactical things with `emit`, `emitp`, and `emitf`,
 including printing them side-by-side, index them, redirect the output to files,
-etc. What this means syntatically is that Miller's parser needs to handle all
+etc. What this means syntactically is that Miller's parser needs to handle all
 sorts of commas, parentheses, and so on:
 
 <pre class="pre-non-highlight-non-pair">

docs/src/reference-dsl-output-statements.md.in

@@ -153,7 +153,7 @@ JSON vs. tabular formats](flatten-unflatten.md) for more information.
 The reason for this is part historical and part technical. As we'll see below,
 you can do lots of syntactical things with `emit`, `emitp`, and `emitf`,
 including printing them side-by-side, index them, redirect the output to files,
-etc. What this means syntatically is that Miller's parser needs to handle all
+etc. What this means syntactically is that Miller's parser needs to handle all
 sorts of commas, parentheses, and so on:
 
 GENMD-CARDIFY