Address PR feedback: fix terminology and move page to top-level nav

- Changed 'pull-based oracle model' to 'pull oracle model' (2 occurrences)
- Changed 'Pull integration pattern' to 'pull integration pattern' (lowercase)
- Moved why-update-prices.mdx from how-pyth-works/ to price-feeds/ level
- Updated navigation to show in main 'Understanding Pyth' section
- Updated all links to reflect new file location

Co-Authored-By: Nidhi Singh <[email protected]>

Author: devin-ai-integration[bot]

pages/price-feeds/_meta.json

@@ -60,5 +60,6 @@
   },
 
   "pull-updates": "What is a Pull Oracle?",
+  "why-update-prices": "Why Update Prices",
   "how-pyth-works": "How Pyth Works"
 }

pages/price-feeds/how-pyth-works/_meta.json

@@ -2,7 +2,6 @@
   "pythnet": "Pythnet",
   "oracle-program": "Oracle Program",
   "cross-chain": "Cross-chain",
-  "why-update-prices": "Why Update Prices",
   "fees": "Fees",
   "hermes": "Hermes",
   "price-aggregation": "Price Aggregation",

pages/price-feeds/use-real-time-data/pull-integration/evm.mdx

@@ -47,12 +47,12 @@ Then add the following line to your `remappings.txt` file:
 ```
 
 <Callout type="warning" emoji="⚠️">
-  **Important**: Pyth uses a pull-based oracle model that requires users to
-  update prices on-chain before reading them. If you don't update the price or
-  if the on-chain price becomes too stale, calls to `getPriceNoOlderThan()` will
+  **Important**: Pyth uses a pull oracle model that requires users to update
+  prices on-chain before reading them. If you don't update the price or if the
+  on-chain price becomes too stale, calls to `getPriceNoOlderThan()` will
   revert with a `StalePrice` error (0x19abf40e). Learn more about [why you need
-  to update prices](../../how-pyth-works/why-update-prices) and see [how to
-  fetch price updates](../../fetch-price-updates) for implementation details.
+  to update prices](../../why-update-prices) and see [how to fetch price
+  updates](../../fetch-price-updates) for implementation details.
 </Callout>
 
 ## Write Contract Code

pages/price-feeds/how-pyth-works/why-update-prices.mdx renamed to pages/price-feeds/why-update-prices.mdx

@@ -1,17 +1,17 @@
 # Why Update Prices
 
-Pyth uses a pull-based oracle model. Unlike traditional push oracles that automatically update prices on-chain at regular intervals, Pyth requires users to explicitly update the on-chain price before reading it.
+Pyth uses a pull oracle model. Unlike traditional push oracles that automatically update prices on-chain at regular intervals, Pyth requires users to explicitly update the on-chain price before reading it.
 
 This design offers several advantages:
 
 - **Lower costs**: You only pay for price updates when you need them
 - **Lower latency**: You can fetch the latest price update directly from Pyth's low-latency oracle network and submit it on-chain immediately
 - **Flexibility**: Different applications can update prices at different frequencies based on their needs
 
-In the Pull integration pattern, your contract must:
+In the pull integration pattern, your contract must:
 
-1. Accept `priceUpdate` data from the caller (fetched from [Hermes](./hermes))
+1. Accept `priceUpdate` data from the caller (fetched from [Hermes](./how-pyth-works/hermes))
 2. Call `updatePriceFeeds()` to submit this data on-chain before reading prices
 3. Pay a small fee for each update (calculated via `getUpdateFee()`)
 
-If you don't update the price or if the on-chain price becomes too stale, calls to `getPriceNoOlderThan()` will revert with a `StalePrice` error. See [how to fetch price updates](../fetch-price-updates) for more details on obtaining price updates.
+If you don't update the price or if the on-chain price becomes too stale, calls to `getPriceNoOlderThan()` will revert with a `StalePrice` error. See [how to fetch price updates](./fetch-price-updates) for more details on obtaining price updates.