Update README.md

README.md

@@ -94,11 +94,17 @@ t-ecd/
 └── reviews/{day}.pq
 ```
 
+#### Data availability
+<img src="https://cdn-uploads.huggingface.co/production/uploads/645d4947f5760d1530d55023/c2Clc9bNxL9i7jgGBfBq2.png" style="max-height: 500px; width: auto;" alt="Temporal distribution of events over domains">
+*Temporal distribution of events over domains*
+In line with real-world industrial environments, domain-specific data availability varies in historical depth. 
+This reflects practical constraints including data retention policies and product lifecycle stages - 
+newer e-commerce services naturally have shorter histories compared to established banking domains like payments and transactions.
+
+
 ### ⚙️ Events and Catalogs
 
 - **Events**: Each domain provides logs of user interactions with the following possible columns:
-  
-  In events you can encounter such columns:
 
   - `action_type` — interaction type (e.g., view, click, add-to-cart, order, transaction).  
   - `subdomain` — surface where the interaction occurred (recommendations, catalog, search, checkout, campaign); available in Marketplace and Retail.  
@@ -120,9 +126,7 @@ t-ecd/
 
 - **Brand catalog (`brands.pq`)**: Contains `brand_id`, brand-level metadata, and embeddings.  
 
----
-
-### 🧾 Special Structures
+#### 🧾 Special Structures
 
 - **Receipts (`payments/receipts/{day}.pq`)**:  
   Some transactions include detailed receipts with purchased items, their quantities, and prices.  
@@ -142,11 +146,18 @@ T-ECD was generated through a multi-step process:
 
 This process ensures that the dataset is privacy-preserving while remaining representative of industrial recommender system data.  
 
-<img src="https://cdn-uploads.huggingface.co/production/uploads/645d4947f5760d1530d55023/c2Clc9bNxL9i7jgGBfBq2.png" style="max-height: 500px; width: auto;" alt="Temporal distribution of events over domains">
-*Temporal distribution of events over domains*
+## ⚠️ Important Note on Temporal Data Usage
+
+
+<img src="https://cdn-uploads.huggingface.co/production/uploads/645d4947f5760d1530d55023/zaPAcuD3CItTzP2PBkErs.png" style="max-width: 800px; height: auto;">
+
+
+**To prevent data leakage, events from the final 12 hours should not be used for prediction tasks.** 
+The dataset contains temporal noise that requires maintaining a minimum 12-hour gap between the timestamp of the most recent user event and the prediction timestamp.
+This constraint applies to both training and testing scenarios to avoid temporal data leakage.
 
 
-### Usage
+## Download
 
 #### Basic Download
 
@@ -183,15 +194,6 @@ download_dataset(
 )
 ```
 
-## ⚠️ Important Note on Temporal Data Usage
-
-
-<img src="https://cdn-uploads.huggingface.co/production/uploads/645d4947f5760d1530d55023/zaPAcuD3CItTzP2PBkErs.png" style="max-width: 800px; height: auto;">
-
-
-**To prevent data leakage, events from the final 12 hours should not be used for prediction tasks.** 
-The dataset contains temporal noise that requires maintaining a minimum 12-hour gap between the timestamp of the most recent user event and the prediction timestamp.
-This constraint applies to both training and testing scenarios to avoid temporal data leakage.
 
 ---