p -> div

Author: alexandratran

src/scss/custom.scss

@@ -370,7 +370,7 @@ ol {
 .collapsibleContent_i85q {
   padding-top: 0 !important;
 
-  > p {
+  > div {
     font-weight: normal;
   }
 }

wallet/how-to/send-transactions/send-batch-transactions.md

@@ -89,7 +89,7 @@ If you don't specify any chain IDs in `wallet_getCapabilities`, MetaMask will re
 
 <details>
 <summary>Supported networks</summary>
-<p>
+<div>
 MetaMask currently supports atomic batch transactions on the following networks:
 
 - Ethereum Mainnet
@@ -101,7 +101,7 @@ MetaMask currently supports atomic batch transactions on the following networks:
 - Base
 
 MetaMask will support this feature on more networks as they adopt EIP-7702.
-</p>
+</div>
 </details>
 
 :::note Atomic batch unsupported

wallet/tutorials/react-dapp-global-state.md

@@ -498,8 +498,8 @@ will still execute.
 :::
 
 <details>
-<summary><b>Use of `useCallback`</b></summary>
-<p>
+<summary>Use of `useCallback`</summary>
+<div>
 Both of the previous functions use `useCallback`.
 It is used to memoize the `connectWallet` function, optimize performance, and prevent unnecessary re-renders.
 It ensures the function instance remains consistent between renders if its dependencies are changed.
@@ -514,8 +514,7 @@ re-renders of child components.
 Although `useCallback` is not necessary, it demonstrates best practices.
 Predicting how a context provider will be used or how the dapp might change or scale is difficult.
 Using `useCallback` can improve performance in some cases by reducing unnecessary re-renders.
-
-</p>
+</div>
 </details>
 
 Add the following code to `src/hooks/WalletProvider.tsx` to bundle the state and functions using `contextValue`: