add ref to RFC 4180 in CHANGELOG

CHANGELOG.md

@@ -62,7 +62,7 @@ and this project adheres to [Semantic Versioning](http://semver.org/).
     * What I mean by this is that previously the key in the JSON object `{"\"": 3}` was *previously* internally represented as `"\\\""`, with the quote character escaped as shown.
 	* This had the advantage of making it slightly faster to display object keys (e.g., when pretty-printing/compressing/dumping), but *made it impossible for certain strings to be valid object keys, in a way that could not be detected except when pretty-printing or compressing.*
 	* Under the new system as of this version, all strings are acceptable as object keys. This has positive implications for RemesPath, as it means that users do not need to remember to escape string JNodes before using them as keys in an object.
-2. When using the JSON-to-CSV form to create CSV files, newline characters will no longer be escaped in strings. Instead, strings containing newlines will be wrapped in quotes, which should be sufficient to allow most CSV parsers to handle them correctly.
+2. When using the [JSON-to-CSV form](/docs/json-to-csv.md#how-json-nodes-are-represented-in-csv) to create CSV files, newline characters will no longer be escaped in strings. This is one of several changes made in order to acheive compliance with [RFC 4180](https://www.ietf.org/rfc/rfc4180.txt).
 3. Made [`offer_to_show_lint` setting](/docs/README.md#parser-settings) (which controls whether a prompt is shown when errors are found) true by default, so that a fresh installation will show the prompt.
 4. Change RemesPath indexers to reduce the number of backslash escapes needed to get keys containing special characters like `"a\\b"` or `"\"foo\"\tbar"`. For instance, previously ``@.`\\n\\\\a\"` `` would be required to match the key `"\n\\a\""`, whereas now `` @.`\n\\a"` `` matches it.
 5. Running a RemesPath query only causes an attempted re-parsing of the document if the treeview's current file is open.