chore: fixed broken links week 15

alerts/quick-start.mdx

@@ -116,7 +116,7 @@ cd alerts-tutorial
 npm run dev
 ```
 
-Open [http://localhost:3000](http://localhost:3000) to verify your scaffold is running correctly.
+Open `http://localhost:3000` in your browser to verify your scaffold is running correctly.
 
 ## Step 3: Add Notification Bell (4 minutes)
 

blinks/blinks-provider/advanced/forms.mdx

@@ -35,7 +35,7 @@ export const GET = async (req: Request) => {
     label: "Send SOL",
     title: "Send SOL with a Blink",
     description:
-      "This Blink demonstrates how to send SOL on the Solana blockchain. It is a part of the official Blink Starter Guides by Dialect Labs.  \n\nLearn how to build this Blink: https://dialect.to/docs/guides/transfer-sol",
+      "This Blink demonstrates how to send SOL on the Solana blockchain. It is a part of the official Blink Starter Guides by Dialect Labs.  \n\nLearn how to build this Blink: https://docs.dialect.to/blinks/blinks-provider/build-your-first-blink",
     // If you have multiple inputs
     links: {
       actions: [

markets/rewards.mdx

@@ -298,7 +298,7 @@ When you query the Positions API with your wallet address, you get:
 2. **Nested market data** - Current market information (including the reward rules from the Markets API) for convenience, so you don't need a separate API call
 3. **Open positions** - The open positions you have in the market incl. market data, etc.
 
-### The "reward" Position Type (recommended)
+### The "reward" Position Type (recommended) {#the-reward-position-type-recommended}
 
 When calling our Positions API, you will receive active positions, e.g. positions with the type `yield` or `lending` and positions with the type `reward` that reflects the rewards you have earned from those positions.
 
@@ -480,7 +480,7 @@ The nested `market` object includes:
 <Warning>
   This array is deprecated and will be removed in the future. Please migrate to
   using the [`reward` position
-  type](/markets/rewards#the-“reward”-position-type-recommended) instead, which
+  type](/markets/rewards#the-reward-position-type-recommended) instead, which
   provides the same data with better reliability and additional features.
 </Warning>
 
@@ -553,4 +553,4 @@ const newRewards = positions.filter((p) => p.type === "reward");
 | **Claim action**     | Must find separately        | Included in nested `market.actions.claimRewards`  |
 | **Parent position**  | Implicit (part of position) | Explicit `position` field linking to parent       |
 
-See the [reward position type section](/markets/rewards#the-“reward”-position-type-recommended) for detailed examples of the recommended approach.
+See the [reward position type section](/markets/rewards#the-reward-position-type-recommended) for detailed examples of the recommended approach.

standard-blinks-library/quick-start.mdx

@@ -69,7 +69,7 @@ On a high level, the process of using blinks is as follows:
 Blink metadata provides the title, description, icon, and parameters needed to interact with a blink. This information helps you understand the link structure and can be used to build custom UIs (if you don't want to use our [UI components](/blinks/blinks-client/integrate/ui-components/blinks)).
 
 <Tip>
-**Tip:** All SBL blinks include an OpenAPI specification that lets you test them directly in your browser and explore the response structure. You can use these interactive docs instead of fetching metadata manually - jump to [Step 2](#step-2-execute-action-post-request) if you prefer this approach.
+**Tip:** All SBL blinks include an OpenAPI specification that lets you test them directly in your browser and explore the response structure. You can use these interactive docs instead of fetching metadata manually - jump to [Step 2](#step-2-build-the-post-request) if you prefer this approach.
 </Tip>
 
 ### Fetching Metadata Programmatically