Update README.md

README.md

@@ -7,7 +7,7 @@ size_categories:
 - 100B<n<1T
 ---
 
-This dataset contains the fully prepared data, which has been tokenized and pre-shuffled, used to train the Pythia (deduplicated) models. You can find these models under the EleutherAI organization, and they are also listed in my [Memorization Profiles collection](https://huggingface.co/collections/pietrolesci/memorisation-profiles-6619604c4594c878cd9d451f).
+This dataset contains the fully prepared data, which has been tokenized and pre-shuffled, used to train the Pythia (deduplicated) models. You can find these models under the EleutherAI organization, and they are also listed in my [Memorisation Profiles collection](https://huggingface.co/collections/pietrolesci/memorisation-profiles-6619604c4594c878cd9d451f).
 
 This data is the same as the one found in [EleutherAI/pile-deduped-pythia-preshuffled](https://huggingface.co/datasets/EleutherAI/pile-deduped-pythia-preshuffled), but it is presented in a more manageable format. Instead of using the Megatron format used by the GPT-NeoX library, I have stored the data in a parquet format.
 
@@ -16,11 +16,11 @@ This data is the same as the one found in [EleutherAI/pile-deduped-pythia-preshu
 
 The dataset has 3 columns:
 - `uid`: a sequential identified for the sequence (not present in the original dataset)
-- `batch_idx`: the index of the batch to which a sequence belongs to (not present in the original dataset).
+- `batch_idx`: the index of the batch to which a sequence belongs (not present in the original dataset).
 - `token_ids`: the tokenised texts, each of length 2049 tokens.
 
 The dataset is split into 143 chunks (parquet files) and each chunk includes 1024000 sequences (rows) corresponding to 1000 batches, each formed by 1024 sequences.
-This means that each chunk corresponds to the data seen between between one checkpoint and the next.
+This means that each chunk corresponds to the data seen between one checkpoint and the next.
 Specifically, the Pythia model checkpoints are available* at initialisation (step 0) and each 1000 steps (steps 1000, 2000, etc) up to the last checkpoint (step 143000).
 We reflect this structure into the filenames: `train-001000.parquet`, `train-002000.parquet`, ..., `train-143000.parquet`.
 Let's clarify the mapping between chunks and checkpoints with an example.
@@ -44,7 +44,7 @@ Kudos to [LLM360/AmberDatasets](https://huggingface.co/datasets/LLM360/AmberData
 
 ## Interacting with the data
 
-Besides clarity and ease-of-use, another great advantage of this release is that it allows users to easily interact with the data without downloading it.
+Besides clarity and ease of use, another great advantage of this release is that it allows users to easily interact with the data without downloading it.
 The parquet format plays nicely with the Hugging Face Hub. So you can use its integrations with external tools like [DuckDB](https://huggingface.co/docs/hub/en/datasets-duckdb) or [pola-rs](https://huggingface.co/docs/hub/en/datasets-polars) to run queries over the data.
 For example,