Add clarification for term history in indexerHInts docs

website/pages/en/developing/creating-a-subgraph.mdx

@@ -163,8 +163,26 @@ The important entries to update for the manifest are:
     prune: auto
   ```
 
+  > The term "history" in this context of subgraphs is about storing data that reflects the old states of mutable entities. This capability is essential for [time travel queries](/querying/graphql-api/#time-travel-queries), which permit the examination of previous states of these entities at particular points in the blockchain's history.
+
   Using `"auto"` is generally recommended as it maximizes query performance and is sufficient for most users who do not require access to extensive historical data.
 
+  For subgraphs leveraging [time travel queries](/querying/graphql-api/#time-travel-queries), it's advisable to either set a specific number of blocks for historical data retention or use `prune: never` to keep all historical entity states. Below are examples of how to configure both options in your subgraph's settings:
+
+  To retain a specific amount of historical data:
+
+  ```
+   indexerHints:
+    prune: 1000 # Replace 10000 with the desired number of blocks to retain
+  ```
+
+  To preserve the complete history of entity states:
+
+  ```
+  indexerHints:
+    prune: never
+  ```
+
 - `dataSources.source`: the address of the smart contract the subgraph sources, and the ABI of the smart contract to use. The address is optional; omitting it allows to index matching events from all contracts.
 
 - `dataSources.source.startBlock`: the optional number of the block that the data source starts indexing from. In most cases, we suggest using the block in which the contract was created.