update v10 to clarify the market status of price and tokenizedprice

Author: dev-dist

src/content/data-streams/reference/report-schema-v10.mdx

@@ -38,9 +38,11 @@ Chainlink Tokenized Asset Data Streams adhere to the report schema outlined belo
 
 {/* prettier-ignore */}
 <Aside type="danger" title="Weekend Usage Disclaimer">
-  **Users should not use these streams during weekends** due to limited exchange activity.
+  **The `price` field does not update during weekends** because the underlying real-world equity market is closed.
 
-  If usage is necessary, increase fees to mitigate risks. Developers are solely responsible for monitoring and mitigating market integrity risks, as outlined in the [Developer Responsibilities](/data-streams/developer-responsibilities) documentation.
+  However, the `tokenizedPrice` field continues to update as it reflects trading activity on centralized exchanges (CEXs). Weekend liquidity tends to be thin, so users should implement guardrails against unexpected volatility.
+  
+  Developers are solely responsible for monitoring and mitigating market integrity risks, as outlined in the [Developer Responsibilities](/data-streams/developer-responsibilities) documentation.
 </Aside>
 
 **Notes:**

src/content/data-streams/tokenized-asset-streams/index.mdx

@@ -14,9 +14,11 @@ import Aside from "@components/Aside.astro"
 
 {/* prettier-ignore */}
 <Aside type="danger" title="Weekend Usage Disclaimer">
-  **Users should not use these streams during weekends** due to limited exchange activity.
+  **The `price` field does not update during weekends** because the underlying real-world equity market is closed.
 
-  If usage is necessary, increase fees to mitigate risks. Developers are solely responsible for monitoring and mitigating market integrity risks, as outlined in the [Developer Responsibilities](/data-streams/developer-responsibilities) documentation.
+  However, the `tokenizedPrice` field continues to update as it reflects trading activity on centralized exchanges (CEXs). Weekend liquidity tends to be thin, so users should implement guardrails against unexpected volatility.
+  
+  Developers are solely responsible for monitoring and mitigating market integrity risks, as outlined in the [Developer Responsibilities](/data-streams/developer-responsibilities) documentation.
 </Aside>
 
 <FeedPage