Update README.md

README.md

@@ -16,24 +16,26 @@ configs:
 
 # Elliquiy roleplaying forum data
 
-A collection of 6,640,593 posts and 112,328 thousands of mostly _erotic_ roleplaying forum threads from Elliquiy, from about mid-2005 through early April 2023. About 9 GB of uncompressed text data (including formatting tags). The data is from the larger [raw Forum RP dataset](https://huggingface.co/datasets/lemonilia/Roleplay-Forums_2023-04) I also uploaded.
+A collection of 6,640,593 posts and 112,328 thousands of mostly high-effort _erotic_ roleplaying forum threads from Elliquiy, from April 2005 through April 2023. About 9 GB of uncompressed text data (including formatting tags). The data is from the larger [raw Forum RP dataset](https://huggingface.co/datasets/lemonilia/Roleplay-Forums_2023-04) I also uploaded.
 
-Basic automated cleaning was performed, but the messages are still (by deliberate choice) mostly in HTML format, with the notable exception of converting linebreaks into `\n`.
+Basic automated cleaning was performed, but the messages are still (by deliberate choice) in HTML format, with the notable exception of converting linebreaks into `\n`.
 
-In addition to the messages, some metadata was provided for convenience, as well as alternative usernames that could be used instead of directly usernames (in the format of `User0`, `User1` ... `UserN`). These are unique per-thread, but not globally.
+In addition to the messages, some metadata was provided for user convenience, as well as alternative usernames that could be used instead of usernames (in the format of `User0`, `User1` ... `UserN`). These are unique per-thread, but not globally.
 
-Consider this a **work in progress**. I might update the dataset in the future as I improve the cleaning procedure.
+Consider this a **work in progress**. I might update the dataset in the future as I improve the cleaning procedure or the data format.
 
 # Limitations and issues
-During the scraping procedure (occurred on April 2023) some information like text color and links was lost in the process. Most of the data is adult-themed, and given that usernames inside the posts still exist, it would be best if usernames weren't directly used when training a model with this data.
+During the scraping procedure (performed on April 2023) some information like text color and links was lost in the process.
 
-Given the text formatting used by many users, complete and thorough conversion to Markdown seems very difficult without losing information in the process or causing other issues.
+Most of the data is adult-themed, and given that usernames inside the posts still exist, it would be best if usernames weren't directly used when training a model with this data.
+
+Given the text formatting used by many users, complete and thorough conversion to Markdown seems very difficult without losing information in the process or causing formatting problems.
 
 Due to the nested structure of the data, I had to split the original parquet file into smaller ones in order to avoid issues when loading them with `pandas` in Python (via PyArrow). This appears to be a [documented problem](https://github.com/apache/arrow/issues/21526#issuecomment-2350741670).
 
 # Basic usage
 
-The files need PyArrow installed from `pip`. FastParquet will not work properly due to the nested data structure.
+The files need PyArrow installed from `pip` to be loaded with `pandas`. FastParquet will not work properly due to the nested data structure.
 
 ```python
 import pandas
@@ -119,6 +121,7 @@ Name: 2350, dtype: object
 
 ## NOT done
 - Replacing HTML escape characters
+- Balancing quote marks and other characters that are supposed to be paired
 - Changing fancy punctuation to ASCII punctuation
 - Removing usernames entirely
   - Removing them from the message bodies themselves might not be easy.