Update README.md

README.md

@@ -22,9 +22,9 @@ Prepared by the [Harvard Library Innovation Lab](https://lil.law.harvard.edu) in
 ## Summary
 - [Formats](#formats)
 - [File structure](#file-structure)
-- [Data Dictionary](#data-dictionary)
-- [Data Nutrition Label](https://datanutrition.org/labels/v3/?id=c29976b2-858c-4f4e-b7d0-c8ef12ce7dbe) (DRAFT). ([Archive](https://perma.cc/YV5P-B8JL)).
-- [Pipeline Source Code](https://github.com/harvard-lil/cold-cases-export)
+- [Data dictionary](#data-dictionary)
+- [Data nutrition label](https://datanutrition.org/labels/v3/?id=c29976b2-858c-4f4e-b7d0-c8ef12ce7dbe) (DRAFT). ([Archive](https://perma.cc/YV5P-B8JL)).
+- [Pipeline source code](https://github.com/harvard-lil/cold-cases-export)
 
 ---
 
@@ -34,11 +34,9 @@ We've released this data in two different formats:
 
 ### JSON-L or JSON Lines
 
-This format consists of a JSON document for every row in the dataset, one per line. This makes the data really easy to take a selection of the data or split it out into multiple files for parallel processing using ordinary command line tools such as `head`, `split` and `jq`. 
+This format consists of a JSON document for every row in the dataset, one per line. This makes it easy to sample a selection of the data or split it out into multiple files for parallel processing using ordinary command line tools such as `head`, `split` and `jq`. 
 
-Most JSON parsers are unable to easily stream through an enormous JSON array without loading the whole document in RAM or using more difficult APIs, so writing the data as an enormous JSON arrray would make it unwieldy.
-
-Also, just about any language you can think of has a ready way  to parse JSON data, which makes this version of the dataset more compatible. 
+Just about any language you can think of has a ready way  to parse JSON data, which makes this version of the dataset more compatible. 
 
 See: https://jsonlines.org/
 
@@ -74,18 +72,18 @@ Partial glossary of the fields in the data.
 | --- | --- |
 | `judges` |  Names of judges presiding over the case, extracted from the text. |
 | `date_filed` |  Date the case was filed. Formatted in ISO Date format. |
-| `date_filed_is_approximate` |  Boolean representing whether or not the `date_filed` values are definitively correct. |
+| `date_filed_is_approximate` |  Boolean representing whether the `date_filed` value is precise to the day. |
 | `slug` |  Short, human-readable unique string nickname for the case. |
 | `case_name_short` |  Short name for the case. |
 | `case_name` |  Fuller name for the case. |
 | `case_name_full` |  Full, formal name for the case. |
 | `attorneys` |  Names of attorneys arguing the case, extracted from the text. |
-| `nature_of_suit` |  Free text representinng ype of suit, such as Civil, Tort, etc. |
-| `syllabus` |  Summary of the questions addressed by the court in the decision. |
-| `headnotes` |  Textural headnotes of the case |
-| `summary` |  Textural summary of the case |
+| `nature_of_suit` |  Free text representinng type of suit, such as Civil, Tort, etc. |
+| `syllabus` |  Summary of the questions addressed in the decision, if provided by the reporter of decisions. |
+| `headnotes` |  Textual headnotes of the case |
+| `summary` |  Textual summary of the case |
 | `disposition` |  How the court disposed of the case in their final ruling. |
-| `history` |  Textural information about what happened to this case in later decisions. |
+| `history` |  Textual information about what happened to this case in later decisions. |
 | `other_dates` |  Other dates related to the case in free text. |
 | `cross_reference` |  Citations to related cases. |
 | `citation_count` |  Number of cases that cite this one. |
@@ -94,11 +92,10 @@ Partial glossary of the fields in the data.
 | `court_short_name` |  Short name of court presiding over case. |
 | `court_full_name` |  Full name of court presiding over case. |
 | `opinions` |  An array of subrecords. |
-| `opinions.author_str` | Name of the author of an individual opinion. (Field within entry of `opinions`) |
-| `opinions.per_curiam` | Boolean representing whether the opinion was delivered by an entire court or a single judge. (Field within entry of `opinions`)|
-| `opinions.type` | One of `"010combined"`, `"015unamimous"`, `"020lead"`, `"025plurality"`, `"030concurrence"`, `"035concurrenceinpart"`, `"040dissent"`, `"050addendum"`, `"060remittitur"`, `"070rehearing"`, `"080onthemerits"`, `"090onmotiontostrike"`. (Field within entry of `opinions`) |
-| `opinions.opinion_text` | Actual full text of the opinion. (Field within entry of `opinions`)  |
-| `opinions.ocr` | Whether or not the opinion was captured via optical character recognition. (Field within entry of `opinions`)  |
-
+| `opinions.author_str` | Name of the author of an individual opinion. |
+| `opinions.per_curiam` | Boolean representing whether the opinion was delivered by an entire court or a single judge. |
+| `opinions.type` | One of `"010combined"`, `"015unamimous"`, `"020lead"`, `"025plurality"`, `"030concurrence"`, `"035concurrenceinpart"`, `"040dissent"`, `"050addendum"`, `"060remittitur"`, `"070rehearing"`, `"080onthemerits"`, `"090onmotiontostrike"`. |
+| `opinions.opinion_text` | Actual full text of the opinion. |
+| `opinions.ocr` | Whether the opinion was captured via optical character recognition or born-digital text. |
 
-[☝️ Go back to Summary](#summary)
+[☝️ Go back to Summary](#summary)