From 0e4999c26c3eaa1332a49c0fe8fe5e8ac97c1b6c Mon Sep 17 00:00:00 2001 From: Gary Armstrong Date: Tue, 11 Jan 2022 11:17:18 -0500 Subject: [PATCH] misspelling fix spelling --- docs/src/new-in-miller-6.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/src/new-in-miller-6.md b/docs/src/new-in-miller-6.md index f2bbc59913..d14dffd691 100644 --- a/docs/src/new-in-miller-6.md +++ b/docs/src/new-in-miller-6.md @@ -300,7 +300,7 @@ IFS and IPS can be regular expressions now. Please see the section on [multi-cha ### JSON and JSON Lines formatting -* `--jknquoteint` and `jquoteall` are ignored; they were workarounds for the (now much-improved) tyoe-inference and type-tracking in Miller 6. +* `--jknquoteint` and `jquoteall` are ignored; they were workarounds for the (now much-improved) type-inference and type-tracking in Miller 6. * `--json-fatal-arrays-on-input`, `--json-map-arrays-on-input`, and `--json-skip-arrays-on-input` are ignored; Miller 6 now supports arrays fully. * See also `mlr help legacy-flags` or the [legacy-flags reference](reference-main-flag-list.md#legacy-flags). * Miller 5 accepted input records either with or without enclosing `[...]`; on output, by default it produced single-line records without outermost `[...]`. Miller 5 let you customize output formatting using `--jvstack` (multi-line records) and `--jlistwrap` (write outermost `[...]`). _Thus, Miller 5's JSON output format, with default flags, was in fact [JSON Lines](file-formats.md#json-lines) all along._