Merge branch 'main' into ois

Author: nidhi-singh02

apps/developer-hub/content/docs/entropy/chainlist.mdx

@@ -9,8 +9,10 @@ import { EntropyTable } from "../../../src/components/EntropyTable";
 ## Mainnets
 
 <InfoBox variant="warning">
-  The fees for mainnet are dynamically set. Always use the on-chain method
-  `entropy.getFeeV2()` to get the current fee.
+  <div>
+    The fees for mainnet are dynamically set. Always use the on-chain method
+    `entropy.getFeeV2()` to get the current fee.
+  </div>
 </InfoBox>
 
 The following tables shows the total fees payable when using the **default provider**.
@@ -31,8 +33,10 @@ Entropy callbacks the consumer as part of this transaction.
 ## Testnets
 
 <InfoBox variant="info">
-  The fees for testnets kept deliberately low and different from the mainnet
-  fees.
+  <div>
+    The fees for testnets kept deliberately low and different from the mainnet
+    fees.
+  </div>
 </InfoBox>
 
 The Entropy contract is deployed on the following testnet chains:

apps/developer-hub/content/docs/meta.json

@@ -5,5 +5,7 @@
     "oracle-integrity-staking",
     "express-relay",
     "entropy"
+    "whitepaper",
+    "security"
   ]
 }

apps/developer-hub/content/docs/pyth-core/api-instances-and-providers/hermes.mdx

@@ -24,9 +24,9 @@ Network:
 URL: https://hermes.pyth.network
 
 <InfoBox variant="warning">
-For developers building on **Aptos testnet**, **Sui testnet** or **Near testnet**, please use the Hermes Beta endpoint:
+<div>For developers building on **Aptos testnet**, **Sui testnet** or **Near testnet**, please use the Hermes Beta endpoint:</div>
 
-URL: https://hermes-beta.pyth.network
+<div>URL: https://hermes-beta.pyth.network</div>
 
 </InfoBox>
 

apps/developer-hub/content/docs/pyth-core/contract-addresses/pythnet.mdx

@@ -11,12 +11,15 @@ index: false
 # Price Feed Program Addresses on Pythnet
 
 <InfoBox variant="warning">
-  **Important:** The addresses on this page are for the Pythnet network itself,
-  which is used to construct and deliver Pyth prices to other blockchains. If
-  you are building an application on EVM, Solana, SVM, or another chain, you
-  should use the Pyth program deployed on your target chain instead. Please
-  refer to the [Contract Addresses](/price-feeds/contract-addresses) page and
-  select your specific blockchain environment.
+  <div>
+    **Important:** The addresses on this page are for the Pythnet network
+    itself, which is used to construct and deliver Pyth prices to other
+    blockchains. If you are building an application on EVM, Solana, SVM, or
+    another chain, you should use the Pyth program deployed on your target chain
+    instead. Please refer to the [Contract
+    Addresses](/price-feeds/contract-addresses) page and select your specific
+    blockchain environment.
+  </div>
 </InfoBox>
 
 The following table contains the addresses of the programs deployed on Pythnet that operate together to construct Pyth prices and deliver them to other blockchains:

apps/developer-hub/content/docs/pyth-core/create-your-first-pyth-app.mdx

@@ -14,9 +14,11 @@ This tutorial walks through creating a complete application that uses Pyth Price
 The application includes a smart contract and an off-chain code invoking the contract.
 
 <InfoBox variant="info">
-  The tutorial is an in-depth walkthrough of contract development; more
-  experienced developers may want to refer to [Use Real-time Price
-  Data](./use-real-time-data) for a more concise version.
+  <div>
+    The tutorial is an in-depth walkthrough of contract development; more
+    experienced developers may want to refer to [Use Real-time Price
+    Data](./use-real-time-data) for a more concise version.
+  </div>
 </InfoBox>
 
 Please choose your environment to get started:

apps/developer-hub/content/docs/pyth-core/create-your-first-pyth-app/evm/part-2.mdx

@@ -19,8 +19,10 @@ This part of the tutorial will conver the following:
 - Update and fetch the price from the contract using [hermes-client](https://github.com/pyth-network/pyth-crosschain/tree/main/apps/hermes/client/js).
 
 <InfoBox variant="info">
-  This tutorial is continuation of the [Part 1: Create a Contract](./part-1). If
-  you haven't completed that part yet, please do so before continuing.
+  <div>
+    This tutorial is continuation of the [Part 1: Create a Contract](./part-1).
+    If you haven't completed that part yet, please do so before continuing.
+  </div>
 </InfoBox>
 
 ## Deploy the contract

apps/developer-hub/content/docs/pyth-core/current-fees.mdx

@@ -13,9 +13,11 @@ The following tables shows the total fees payable when updating a price feed.
 Please note the fees shown below is the amount paid in `msg.value` per price feed update.
 
 <InfoBox variant="info">
-  **Note**: The default fee of all chains **not** mentioned below is **1(one)**
-  unit of the smallest denomination of the blockchain's native token (e.g., **1
-  wei on Ethereum**).
+  <div>
+    **Note**: The default fee of all chains **not** mentioned below is
+    **1(one)** unit of the smallest denomination of the blockchain's native
+    token (e.g., **1 wei on Ethereum**).
+  </div>
 </InfoBox>
 
 | **Network** | **Fees**         |

apps/developer-hub/content/docs/pyth-core/fetch-price-updates.mdx

@@ -21,10 +21,12 @@ provides three different ways to fetch price updates:
 1. [SDK](#sdk)
 
 <InfoBox variant="info">
-  Fetching a price from Hermes requires a price feed ID. This ID serves as a
-  unique identifier for each price feed (e.g., BTC/USD). The complete list of
-  Pyth price feed IDs is available at
-  https://pyth.network/developers/price-feed-ids
+  <div>
+    Fetching a price from Hermes requires a price feed ID. This ID serves as a
+    unique identifier for each price feed (e.g., BTC/USD). The complete list of
+    Pyth price feed IDs is available at
+    https://pyth.network/developers/price-feed-ids
+  </div>
 </InfoBox>
 
 ## REST API

apps/developer-hub/content/docs/pyth-core/pythnet-reference/schedule-format.mdx

@@ -32,7 +32,7 @@ If `weekly_schedule` is also undefined, pyth-agent will default to 24/7 publishi
 - `Timezone` - A human-readable tz database TZ identifier of the market’s local timezone, such as `America/New_York`.
   **Full list of identifiers can be found [here](https://en.wikipedia.org/wiki/List_of_tz_database_time_zones)**.
   <InfoBox variant="info">
-    Daylight-saving time is automatically handled by the pyth-agent.
+    <div>Daylight-saving time is automatically handled by the pyth-agent.</div>
   </InfoBox>
 - `WeeklySchedule` - A list of seven comma-separated `DaySchedule` entries that define the recurring weekly schedule of a product’s market hours.
   Each `DaySchedule` entry corresponds to a day of the week, starting from Monday.
@@ -71,7 +71,7 @@ If `weekly_schedule` is also undefined, pyth-agent will default to 24/7 publishi
 ## Weekly Schedule Format (Deprecated)
 
 <InfoBox variant="warning">
-  This field is deprecated in favor of `schedule`.
+  <div>This field is deprecated in favor of `schedule`.</div>
 </InfoBox>
 
 This document outlines the rules for specifying contents of a new Pyth product metadata field - `weekly_schedule` . The field specifies the recurring weekly schedule of a product’s market hours. It serves as a reference for `pyth-agent` to stop publishing outside the hours specified in the schedule. Notable use cases include:

apps/developer-hub/content/docs/pyth-core/sponsored-feeds.mdx

@@ -23,11 +23,13 @@ The sponsored feeds can vary by network. Please see the relevant section below f
 - [Movement](sponsored-feeds/movement)
 
 <InfoBox variant="warning">
-  DISCLAIMER: While the Pyth Data Association strives to deliver timely updates,
-  these sponsored feeds may occasionally experience delays in updates caused by
-  chain halts, gas estimations and other issues. Applications are advised to run
-  their own scheduler. Find out how you can run your own scheduler
-  [here](/price-feeds/schedule-price-updates/using-scheduler).
+  <div>
+    DISCLAIMER: While the Pyth Data Association strives to deliver timely
+    updates, these sponsored feeds may occasionally experience delays in updates
+    caused by chain halts, gas estimations and other issues. Applications are
+    advised to run their own scheduler. Find out how you can run your own
+    scheduler [here](/price-feeds/schedule-price-updates/using-scheduler).
+  </div>
 </InfoBox>
 
 If you would like to see additional feeds on this list, please fill in this [form](https://tally.so/r/nGz2jj) to signal your interest.