self-review updates

Author: dev-dist

reports/llms-report.json

@@ -1,5 +1,5 @@
 {
-  "startedAt": "2025-12-09T23:41:23.311Z",
+  "startedAt": "2025-12-10T23:13:13.756Z",
   "siteBase": "https://docs.chain.link",
   "sections": [
     {
@@ -38,9 +38,9 @@
       "section": "data-feeds",
       "pagesProcessed": 37,
       "outputPath": "src/content/data-feeds/llms-full.txt",
-      "bytes": 302589,
-      "prevBytes": 302327,
-      "deltaBytes": 262
+      "bytes": 302816,
+      "prevBytes": 302589,
+      "deltaBytes": 227
     },
     {
       "section": "data-streams",
@@ -123,5 +123,5 @@
       "deltaBytes": 0
     }
   ],
-  "finishedAt": "2025-12-09T23:41:27.135Z"
+  "finishedAt": "2025-12-10T23:13:17.715Z"
 }

src/content/data-feeds/llms-full.txt

@@ -3216,6 +3216,14 @@ Data feeds managed by Chainlink Labs will be considered for deprecation if they
 
 Known users of these feeds will be contacted directly about the feeds' deprecation. Notifications will also be posted on the [Feeds Scheduled For Deprecation](/data-feeds/deprecating-feeds) page and on our [Discord channel](https://discord.com/channels/592041321326182401/991444378335838318) with two weeks of notice before they are shut down.
 
+
+<Aside type="note" title="Data Feed Shutdown Behavior">
+  Once a feed is shutdown, calls to the feed will behave as follows:
+
+  - `lastAnswer` will return `0`
+  - `latestRoundData` will revert with no data available
+</Aside>
+
 ## Market hours
 
 In addition to categories, be aware that markets for several assets are actively traded only during certain hours. Listed data feeds include an attribute describing their market hours. Chainlink Labs recommends using these feeds only during their specified hours:

src/content/data-feeds/selecting-data-feeds.mdx

@@ -103,6 +103,13 @@ Data feeds managed by Chainlink Labs will be considered for deprecation if they
 
 Known users of these feeds will be contacted directly about the feeds' deprecation. Notifications will also be posted on the [Feeds Scheduled For Deprecation](/data-feeds/deprecating-feeds) page and on our [Discord channel](https://discord.com/channels/592041321326182401/991444378335838318) with two weeks of notice before they are shut down.
 
+{/* prettier-ignore */}
+<Aside type="note" title="Data Feed Shutdown Behavior">
+  Once a feed is shutdown, calls to the feed will behave as follows: 
+  - `lastAnswer` will return `0` 
+  - `latestRoundData` will revert with no data available
+</Aside>
+
 ## Market hours
 
 In addition to categories, be aware that markets for several assets are actively traded only during certain hours. Listed data feeds include an attribute describing their market hours. Chainlink Labs recommends using these feeds only during their specified hours:

src/content/data-streams/concepts/calculated-streams.mdx

@@ -32,7 +32,7 @@ All Data Streams use a [Decentralized Oracle Network (DON)](/data-streams/archit
 
 Traditional Data Streams aggregate market data from multiple independent providers, ensuring no single data source can compromise the stream's integrity.
 
-Instead of aggregating raw market data, Calculated Streams compute derived values using predefined formulas applied to various inputs—including existing data streams, onchain state, and offchain APIs. This enables protocols to consume complex, computed data points without implementing their own calculation logic.
+Instead of aggregating only raw market data, calculated streams compute derived values using predefined formulas applied to various inputs, including existing data streams, onchain state, and offchain APIs. Some inputs are decentralized aggregates (for example, crypto price streams from multiple independent providers), while others may come from a single protocol or API (for example, a specific vault contract or yield provider). Because a calculated stream depends on all of these inputs, you should evaluate their dependencies and failure modes carefully before using it in a value-securing application.
 
 <Aside type="caution" title="Important Considerations">
   Calculated streams introduce additional dependencies and timing considerations compared to standard streams. Before
@@ -97,17 +97,17 @@ Calculated streams inherit risks from their underlying inputs and introduce addi
 
 ### Multiple dependencies
 
-Each input—RPC providers, external APIs, smart contracts—represents a potential point of failure. If any required input becomes unavailable, the calculated stream cannot produce a value.
+If a required input becomes unavailable or unreliable, the calculated stream might not continue to reflect current conditions. Integrators should not assume any specific fallback behavior and must design their protocols to handle this scenario explicitly.
 
 #### Mitigation
 
 - Design your protocol to handle missing data gracefully (pause operations, use last-known values, or implement fallbacks based on your risk tolerance)
 
 ### Timing and synchronization
 
-Inputs update at different frequencies and are read via separate calls, so they may reflect slightly different block heights or timestamps. The calculated value is an approximation based on the latest available data, not a single-block atomic snapshot.
+Inputs update at different frequencies and are read via separate calls, so they may reflect slightly different block heights or timestamps. The calculated value is an approximation based on the latest available data from each input, not a single-block atomic snapshot.
 
-Users should expect small, transient differences between the calculated stream value and values you see on dashboards or compute independently. This is normal during rapid changes (large deposits, withdrawals, market volatility).
+Users should expect small, transient differences between the calculated stream value and values observed on block explorers, vault dashboards, or DEX charts—especially during rapid changes such as large deposits, withdrawals, or sharp market moves. This does not necessarily indicate an issue with the stream, but is a natural consequence of combining multiple inputs with different update cadences.
 
 #### Mitigation