GITBOOK-13: added What's New? section

Author: eric-stackslabs

docs/build/SUMMARY.md

@@ -16,7 +16,7 @@
 
 ## What's New?
 
-* [✅ Clarity 4 is now LIVE! ](whats-new/clarity-4-is-now-live.md)
+* [✅ Clarity 4 is now LIVE!](whats-new/clarity-4-is-now-live.md)
 
 ## Learn Clarinet
 
@@ -79,20 +79,17 @@
 * [Pyth Oracle Integration](stacks.js-integrations/pyth-oracle-integration.md)
 * [React Native Integration](stacks.js-integrations/react-native-integration.md)
 
-***
-
-* [Bitcoin Integration](bitcoin-integration/README.md)
-  * [Sending Bitcoin with Leather](bitcoin-integration/sending-bitcoin-with-leather.md)
-  * [Verifying a Bitcoin Transaction](bitcoin-integration/verifying-a-bitcoin-transaction.md)
-  * [Parsing a Bitcoin Transaction](bitcoin-integration/parsing-a-bitcoin-transaction.md)
-* [sBTC](sbtc/README.md)
-  * [sBTC Builder Quickstart](sbtc/sbtc-builder-quickstart.md)
-  * [How to Use the sBTC JS Library for Bridging](sbtc/how-to-use-the-sbtc-js-library-for-bridging/README.md)
-    * [Depositing: Pegging BTC into sBTC](sbtc/how-to-use-the-sbtc-js-library-for-bridging/btc-to-sbtc.md)
-    * [Withdrawing: Pegging sBTC into BTC](sbtc/how-to-use-the-sbtc-js-library-for-bridging/sbtc-to-btc.md)
-* [Price Oracles](price-oracles.md)
-
 ## Misc. Guides
 
+* [sBTC](misc.-guides/sbtc/README.md)
+  * [sBTC Builder Quickstart](misc.-guides/sbtc/sbtc-builder-quickstart.md)
+  * [How to Use the sBTC JS Library for Bridging](misc.-guides/sbtc/how-to-use-the-sbtc-js-library-for-bridging/README.md)
+    * [Depositing: Pegging BTC into sBTC](misc.-guides/sbtc/how-to-use-the-sbtc-js-library-for-bridging/btc-to-sbtc.md)
+    * [Withdrawing: Pegging sBTC into BTC](misc.-guides/sbtc/how-to-use-the-sbtc-js-library-for-bridging/sbtc-to-btc.md)
+* [Price Oracles](misc.-guides/price-oracles.md)
 * [Build a Borrowing & Lending Protocol](misc.-guides/build-a-borrowing-and-lending-protocol.md)
+* [Bitcoin Integration](misc.-guides/bitcoin-integration/README.md)
+  * [Sending Bitcoin with Leather](misc.-guides/bitcoin-integration/sending-bitcoin-with-leather.md)
+  * [Verifying a Bitcoin Transaction](misc.-guides/bitcoin-integration/verifying-a-bitcoin-transaction.md)
+  * [Parsing a Bitcoin Transaction](misc.-guides/bitcoin-integration/parsing-a-bitcoin-transaction.md)
 * [Community Tutorials](misc.-guides/community-tutorials.md)

docs/build/clarinet-integrations/chainhook-integration.md

@@ -20,7 +20,7 @@ Prerequisites
 
 {% stepper %}
 {% step %}
-### Create your Chainhook predicates
+#### Create your Chainhook predicates
 
 Create predicate files in a `chainhooks/` directory alongside your contracts:
 
@@ -63,7 +63,7 @@ Example predicate for monitoring increment events:
 {% endstep %}
 
 {% step %}
-### Start devnet with Chainhooks
+#### Start devnet with Chainhooks
 
 From your project root, start devnet. Clarinet registers every predicate automatically:
 
@@ -83,7 +83,7 @@ INFO Feb  5 15:20:07.233382 2 chainhooks registered
 {% endstep %}
 
 {% step %}
-### Monitor Chainhook activity
+#### Monitor Chainhook activity
 
 Trigger contract actions and watch for Chainhook alerts:
 

docs/build/clarinet-integrations/sbtc-integration.md

@@ -17,7 +17,7 @@ Clarinet can automatically wire up the official sBTC contracts so you can build
 
 {% stepper %}
 {% step %}
-### Add sBTC to your project
+#### Add sBTC to your project
 
 Add the sBTC contracts to your project requirements:
 
@@ -35,7 +35,7 @@ Clarinet auto-funds devnet wallets with sBTC when these are present.
 {% endstep %}
 
 {% step %}
-### Create an sBTC-enabled contract
+#### Create an sBTC-enabled contract
 
 Example NFT marketplace that accepts sBTC payments:
 
@@ -63,7 +63,7 @@ Example NFT marketplace that accepts sBTC payments:
 {% endstep %}
 
 {% step %}
-### Test in the Clarinet console
+#### Test in the Clarinet console
 
 Launch the console and try the contract using auto-funded wallets:
 
@@ -79,7 +79,7 @@ clarinet console
 {% endstep %}
 
 {% step %}
-### Write unit tests
+#### Write unit tests
 
 Sample Vitest test for sBTC payments:
 
@@ -124,7 +124,7 @@ describe('NFT Marketplace', () => {
 {% endstep %}
 
 {% step %}
-### Deploy to testnet
+#### Deploy to testnet
 
 Generate a plan to confirm remapped addresses for official sBTC contracts:
 

docs/build/clarinet-integrations/stacks.js-integration.md

@@ -13,7 +13,7 @@ Use Stacks.js to interact with your Clarinet devnet from JavaScript applications
 
 {% stepper %}
 {% step %}
-### Install Stacks.js packages
+#### Install Stacks.js packages
 
 Add the required libraries to your frontend project:
 
@@ -23,7 +23,7 @@ npm install @stacks/transactions @stacks/network
 {% endstep %}
 
 {% step %}
-### Configure for devnet
+#### Configure for devnet
 
 Create a network helper:
 
@@ -48,7 +48,7 @@ export const accounts = {
 {% endstep %}
 
 {% step %}
-### Test STX transfers
+#### Test STX transfers
 
 Send a transfer between devnet accounts:
 
@@ -76,7 +76,7 @@ Run the transfer with `ts-node stx-transfer.ts`.
 {% endstep %}
 
 {% step %}
-### Call smart contracts
+#### Call smart contracts
 
 Interact with contracts deployed on devnet:
 
@@ -120,7 +120,7 @@ readCount().catch(console.error);
 {% endstep %}
 
 {% step %}
-### Deploy contracts programmatically
+#### Deploy contracts programmatically
 
 Deploy a contract from your application code:
 

docs/build/clarinet-integrations/vscode-extension.md

@@ -76,25 +76,25 @@ When implementing traits (like SIP-009 NFTs or SIP-010 tokens), the extension ve
 
 {% stepper %}
 {% step %}
-### Set breakpoints
+#### Set breakpoints
 
 Set breakpoints by clicking line numbers in the editor.
 {% endstep %}
 
 {% step %}
-### Start debugging
+#### Start debugging
 
 Press `F5` or use Run → Start Debugging to begin a debugging session.
 {% endstep %}
 
 {% step %}
-### Step through code
+#### Step through code
 
 Step through code line-by-line to follow execution.
 {% endstep %}
 
 {% step %}
-### Inspect state
+#### Inspect state
 
 Inspect variables and stack state while paused at breakpoints.
 {% endstep %}

docs/build/clarinet-js-sdk/mainnet-execution-simulation.md

@@ -55,7 +55,7 @@ use_mainnet_wallets = true  # !mark
 This is particularly useful when:
 
 * Testing against mainnet-only contracts like DEX protocols
-* Your contract includes [`(is-standard standard-or-contract-principal)`](mainnet-execution-simulation.md#) validation
+* Your contract includes [`(is-standard standard-or-contract-principal)`](mainnet-execution-simulation.md) validation
 * Simulating transactions that require mainnet address formats
 
 ## Configure API access
@@ -139,13 +139,13 @@ Solution: Check the contract exists at your block height.
 
 {% stepper %}
 {% step %}
-### Visit the playground
+#### Visit the playground
 
 Go to: https://play.hiro.so/?remote\_data=true
 {% endstep %}
 
 {% step %}
-### Run a mainnet contract call
+#### Run a mainnet contract call
 
 Example Clarity call:
 
@@ -154,4 +154,3 @@ Example Clarity call:
 ```
 {% endstep %}
 {% endstepper %}
-

docs/build/clarinet-js-sdk/unit-testing.md

@@ -11,7 +11,7 @@ Unit testing verifies that individual contract functions behave as expected. The
 
 {% stepper %}
 {% step %}
-### Set up your project
+#### Set up your project
 
 Create a new Clarinet project and install dependencies:
 
@@ -23,7 +23,7 @@ npm install
 {% endstep %}
 
 {% step %}
-### Create the contract
+#### Create the contract
 
 Generate a contract stub:
 
@@ -72,7 +72,7 @@ clarinet check
 {% endstep %}
 
 {% step %}
-### Write your unit test
+#### Write your unit test
 
 Create `tests/defi.test.ts` with a basic happy-path test:
 
@@ -122,7 +122,7 @@ Key calls:
 {% endstep %}
 
 {% step %}
-### Try it out
+#### Try it out
 
 Run the tests:
 
@@ -138,7 +138,7 @@ Test Files  1 passed (1)
 {% endstep %}
 
 {% step %}
-### Generate coverage reports
+#### Generate coverage reports
 
 ```bash
 npm run test:report

docs/build/clarinet/clarity-formatter.md

@@ -16,13 +16,13 @@ You can customize these defaults to match your preferences.
 
 {% stepper %}
 {% step %}
-### Clarity VS Code Extension
+#### Clarity VS Code Extension
 
 Format directly in the editor.
 {% endstep %}
 
 {% step %}
-### Clarinet CLI
+#### Clarinet CLI
 
 Format via command line, including entire projects.
 {% endstep %}

docs/build/clarinet/quickstart.md

@@ -19,7 +19,7 @@ description: >-
 
 {% stepper %}
 {% step %}
-### Create your project
+#### Create your project
 
 Let's start by creating a new Clarinet project. The `clarinet new` command sets up everything you need for smart contract development, including a testing framework, deployment configurations, and a local development environment:
 
@@ -44,7 +44,7 @@ Clarinet creates a complete project structure for you. Each folder serves a spec
 {% endstep %}
 
 {% step %}
-### Generate your contract
+#### Generate your contract
 
 Now that we have our project structure, let's create a smart contract. Navigate into your project directory and use Clarinet's contract generator:
 
@@ -69,7 +69,7 @@ Notice that Clarinet also updated your `Clarinet.toml` file. This configuration
 {% endstep %}
 
 {% step %}
-### Write your contract code
+#### Write your contract code
 
 Open `contracts/counter.clar` and replace its contents with our counter implementation. This contract will maintain a separate count for each user who interacts with it:
 
@@ -99,7 +99,7 @@ Let's understand what each part does:
 {% endstep %}
 
 {% step %}
-### Validate your contract
+#### Validate your contract
 
 Before we can test our contract, let's make sure it's syntactically correct and type-safe. Clarinet's check command analyzes your contract without deploying it:
 
@@ -117,7 +117,7 @@ If you see errors instead, here are the most common issues and how to fix them:
 {% endstep %}
 
 {% step %}
-### Test in the console
+#### Test in the console
 
 Now for the exciting part—let's interact with our contract! Clarinet provides an interactive console where you can call functions and see results immediately. Start the console with:
 
@@ -139,4 +139,3 @@ u2
 ```
 {% endstep %}
 {% endstepper %}
-

docs/build/clarinet/validation-and-analysis.md

@@ -45,7 +45,7 @@ Error in contracts/token.clar:15:10
 
 {% stepper %}
 {% step %}
-### Run basic checks
+#### Run basic checks
 
 Use `clarinet check` to validate your contracts and catch type/syntax errors before deployment.
 
@@ -55,7 +55,7 @@ clarinet check
 {% endstep %}
 
 {% step %}
-### Check a specific contract
+#### Check a specific contract
 
 Focus validation during development on a single contract file:
 
@@ -65,7 +65,7 @@ clarinet check contracts/nft.clar
 {% endstep %}
 
 {% step %}
-### Integrate into CI
+#### Integrate into CI
 
 Automate validation in continuous integration pipelines. Example GitHub Actions workflow: