diff --git a/c/todo.txt b/c/todo.txt
index 0c518b38d..aa971c311 100644
--- a/c/todo.txt
+++ b/c/todo.txt
@@ -230,3 +230,8 @@ Given a version number MAJOR.MINOR.PATCH, increment the:
* MAJOR version when you make incompatible API changes,
* MINOR version when you add functionality in a backwards-compatible manner, and
* PATCH version when you make backwards-compatible bug fixes.
+
+Initial release:
+https://news.ycombinator.com/item?id=10066742
+v2.0.0:
+https://news.ycombinator.com/item?id=10132831
diff --git a/doc/content-for-file-formats.html b/doc/content-for-file-formats.html
index 3f12358da..c039c8040 100644
--- a/doc/content-for-file-formats.html
+++ b/doc/content-for-file-formats.html
@@ -1,7 +1,7 @@
POKI_PUT_TOC_HERE
CSV/TSV/etc.
-When mlr is invoked with the --csv option,
+When mlr is invoked with the --csv or --csvlite option,
key names are found on the first record and values are taken from subsequent
records. This includes the case of CSV-formatted files. See
POKI_PUT_LINK_FOR_PAGE(record-heterogeneity.html)HERE for how Miller handles
@@ -12,12 +12,11 @@ just as awk does. For TSV, use --fs tab; to convert TSV to
CSV, use --ifs tab --ofs , etc. (See also
POKI_PUT_LINK_FOR_PAGE(reference.html)HERE.)
- To be precise, as of August 2015 Miller supports a “CSV-lite”
-format, in the sense of “values which are separated by commas”.
-Double quotes, and all that goes along with them (see the RFC), won’t be correctly
-handled until resolution of https://github.com/johnkerl/miller/issues/4.
+The --csvlite option supports programmable single-byte field and record separators,
+e.g. you can do TSV. Meanwhile --csv supports RFC-4180 CSV (
+https://tools.ietf.org/html/rfc4180).
+For more information about the current status of CSV support in Miller, please see
+https://github.com/johnkerl/miller/releases/tag/v2.0.0.
Pretty-printed
Miller’s pretty-print format is like CSV, but column-aligned. For example, compare
diff --git a/doc/file-formats.html b/doc/file-formats.html
index fdf817064..538596ae8 100644
--- a/doc/file-formats.html
+++ b/doc/file-formats.html
@@ -104,7 +104,7 @@ Miller commands were run with pretty-print-tabular output format.
CSV/TSV/etc.
-When mlr is invoked with the --csv option,
+When mlr is invoked with the --csv or --csvlite option,
key names are found on the first record and values are taken from subsequent
records. This includes the case of CSV-formatted files. See
Record-heterogeneity for how Miller handles
@@ -115,12 +115,11 @@ just as awk does. For TSV, use --fs tab; to convert TSV to
CSV, use --ifs tab --ofs , etc. (See also
Reference.)
- To be precise, as of August 2015 Miller supports a “CSV-lite”
-format, in the sense of “values which are separated by commas”.
-Double quotes, and all that goes along with them (see the RFC), won’t be correctly
-handled until resolution of https://github.com/johnkerl/miller/issues/4.
+The --csvlite option supports programmable single-byte field and record separators,
+e.g. you can do TSV. Meanwhile --csv supports RFC-4180 CSV (
+https://tools.ietf.org/html/rfc4180).
+For more information about the current status of CSV support in Miller, please see
+https://github.com/johnkerl/miller/releases/tag/v2.0.0.
Pretty-printed
Miller’s pretty-print format is like CSV, but column-aligned. For example, compare