Fix docs build and fix typos

tsconfig.json

@@ -16,5 +16,5 @@
     "jsx": "preserve"
   },
   "include": ["next-env.d.ts", "**/*.ts", "**/*.tsx"],
-  "exclude": ["node_modules"]
+  "exclude": ["node_modules", "vocs-docs"]
 }

vocs-docs/docs/pages/interaction/deposits-withdrawals/other.mdx

@@ -15,11 +15,11 @@
 5. **Enter the amount** you wish to transfer
 6. **Confirm the transaction** in Coinbase
 7. **Wait for confirmation** (typically 1-3 minutes)
-   - _Note: This process relies on Coinbase's infrastructure and Noble's IBC integration_
-   - _Coinbase handles the initial funds transfer to Noble's USDC hub_
+   - Note: This process relies on Coinbase's infrastructure and Noble's IBC integration
+   - Coinbase handles the initial funds transfer to Noble's USDC hub
 8. **Funds will automatically route** through Noble to dYdX via IBC
-   - _This automatic routing uses the IBC relayer network_
-   - _No swaps occur in this process as USDC moves directly between compatible chains_
+   - This automatic routing uses the IBC relayer network
+   - No swaps occur in this process as USDC moves directly between compatible chains
 
 ### Example Deposit
 Coinbase → dYdX
@@ -55,8 +55,8 @@ Supported Cosmos Chains: Osmosis, Cosmos Hub, Kujira, Noble, Injective and other
 5. **Enter the amount** you wish to transfer
 6. **Confirm the transaction**
 7. **IBC relayer network processes the transfer:**
-   - _IBC relayers run by validators and third-party services handle the cross-chain message delivery_
-   - _No centralized entity controls this process; it's based on the Cosmos IBC protocol_
-   - _If transferring a non-native token, ensure it's an IBC-supported asset on both chains_
+   - IBC relayers run by validators and third-party services handle the cross-chain message delivery
+   - No centralized entity controls this process; it's based on the Cosmos IBC protocol
+   - If transferring a non-native token, ensure it's an IBC-supported asset on both chains
 8. **Wait for confirmation** (typically 15-30 seconds)
-   - _Faster than bridging solutions as it doesn't require multi-chain consensus_
+   - Faster than bridging solutions as it doesn't require multi-chain consensus

vocs-docs/docs/pages/interaction/deposits-withdrawals/troubleshooting.mdx

@@ -85,8 +85,8 @@ Remember to include transaction details, wallet addresses, and a clear descripti
 6. **For large transfers, use Skip Go** instead of Skip Go Fast for better reliability
 7. **Always move funds from sub account to main account** before initiating withdrawals
 8. **Understand third-party dependencies** in your chosen transfer route:
-   - _Skip relies on their own solver network and DEX integrations_
-   - _IBC transfers depend on the Cosmos relayer infrastructure_
-   - _Coinbase deposits rely on Coinbase's infrastructure and Noble's IBC integration_
+   - Skip relies on their own solver network and DEX integrations
+   - IBC transfers depend on the Cosmos relayer infrastructure
+   - Coinbase deposits rely on Coinbase's infrastructure and Noble's IBC integration
 9. **Monitor relayer and bridge status** during high network congestion periods
 10. **Have backup withdrawal methods** in case one bridge or relayer network experiences issues

vocs-docs/docs/pages/interaction/integration/integration-portfolio.mdx

@@ -46,8 +46,8 @@ This represents the user's maximum buying power if all remaining free collateral
 ::::
 
 (d) `Account level risk`
-The account-level risk is derived from Indexer data via the WebSocket [v4_parent_subaccounts] channel.  [sample response][response](/types/parent_subaccounts_update_message).  
 This metric represents the `percentage of the user's total collateral` that has been allocated to support open positions (also referred to as `margin`).
+The account-level risk is derived from Indexer data via the WebSocket `v4_parent_subaccounts` channel. [sample response](/types/parent_subaccounts_update_message).  
 
 To compute `total collateral`, follow these steps: