Update README.md

README.md

@@ -140,11 +140,10 @@ on the [open-assistant.io](https://www.open-assistant.io/) website until April,
 Conversations are exported as conversation trees with messages as nodes.
 The root node of a conversation tree is called the initial prompt. Each message can have 
 multiple replies. Nodes with more than one reply can have a `rank` field indicating the 
-user preference (the most preferred message has rank 0).
+aggregated user preference (the most preferred message has rank 0).
 
-All messages have a role which can either be "assistant" or "prompter". The roles in 
-conversation threads from prompt to leaf node in a conversation tree are stricly alternating 
-between "prompter" and "assistant".
+All messages have a role property which can either be "assistant" or "prompter". The roles in 
+conversation threads from prompt to leaf node are stricly alternating between "prompter" and "assistant".
 
 ### JSON Example: Message
 
@@ -183,7 +182,7 @@ Objects are stored without indentation on a single lines in the actual jsonl fil
 
 ### JSON Example: Conversation Tree
 
-For readability only a subset of properties are shown here.
+For readability only a subset of the message properties is shown here.
 
 ```
 {
@@ -233,18 +232,17 @@ For readability only a subset of properties are shown here.
 }
 ```
 
-
 Please refer to [oasst-data](https://github.com/LAION-AI/Open-Assistant/tree/main/oasst-data) for
-details about the data structure and python code to read and write jsonl files containing oasst objects.
+details about the data structure and Python code to read and write jsonl files containing oasst data objects.
 
 
 ## Main Dataset Files
 
-Data is provided either as nested messages in conversation trees (extension `.trees.jsonl.gz`) 
-or as flat list of messages (extension `.messages.jsonl.gz`).
+Conversation data is provided either as nested messages in trees (extension `.trees.jsonl.gz`) 
+or as flat list (table) of messages (extension `.messages.jsonl.gz`).
 
-Full conversation trees can be reconstructed from flat messages using the `parent_id` 
-and `message_id` properties to identify their parent-child relationship. The `message_tree_id` 
+Full conversation trees can be reconstructed from flat messages by using the `parent_id` 
+and `message_id` properties to identify the parent-child relationship of messages. The `message_tree_id` 
 and `tree_state` properties (only present in flat messages files) can be used to find all
 all messages of a message tree or to select trees by their state.