From 7f1e126157a79884151f07a0e562c2920edec41b Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Christian=20L=C3=BCck?= Date: Mon, 29 Oct 2018 17:11:26 +0100 Subject: [PATCH] Improve documentation wording/typos --- README.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/README.md b/README.md index 8c96311..aa243a1 100644 --- a/README.md +++ b/README.md @@ -99,12 +99,12 @@ contain special characters from the Unicode range. The text-encoding is usually application-dependant, so your best bet would be to convert to (or assume) UTF-8 consistently. -Despite its shortcomings CSV is widely used and this is unlikely to change any +Despite its shortcomings, CSV is widely used and this is unlikely to change any time soon. In particular, CSV is a very common export format for a lot of tools to interface with spreadsheet processors (such as Exel, Calc etc.). This means -that CSV is often used for historial reasons and using CSV to store structured +that CSV is often used for historical reasons and using CSV to store structured application data is usually not a good idea nowadays – but exporting to CSV for -known applications is a very reasonable approach. +known applications continues to be a very reasonable approach. As an alternative, if you want to process structured data in a more modern JSON-based format, you may want to use [clue/reactphp-ndjson](https://github.com/clue/reactphp-ndjson)