@mysten/docs 0.1.18 → 0.1.19

package/dist/bcs/index.md

@@ -1,6 +1,6 @@
 # BCS - Binary Canonical Serialization
 
-> Encode and decode Sui Move types with Binary Canonical Serialization
+> Encode and decode Sui Move types with Binary Canonical Serialization.
 
 This small and lightweight library implements
 [Binary Canonical Serialization (BCS)](https://github.com/zefchain/bcs) in TypeScript, making BCS

package/dist/bcs/llms-index.md

@@ -1,4 +1,4 @@
 # BCS
 > Encoding and decoding Sui objects
 
-- [BCS - Binary Canonical Serialization](..md): Encode and decode Sui Move types with Binary Canonical Serialization
+- [BCS - Binary Canonical Serialization](..md): Encode and decode Sui Move types with Binary Canonical Serialization.

package/dist/codegen/index.md

@@ -1,17 +1,17 @@
 # Sui TypeScript Codegen
 
-> Generate type-safe TypeScript bindings from on-chain Sui Move packages
+> Generate type-safe TypeScript bindings from onchain Sui Move packages.
 
 The `@mysten/codegen` package automatically generates type-safe TypeScript code from your Move
 packages, enabling seamless interaction with your smart contracts from TypeScript applications.
 
-> **Warning:** This package is currently in development and may have breaking changes.
+> **Warning:** This package is currently in development and might have breaking changes.
 
 ## Features
 
 - **Type-safe Move calls**: Generate TypeScript functions with full type safety for calling your
   Move functions
-- **BCS type definitions**: Automatic BCS struct definitions for parsing on-chain data
+- **BCS type definitions**: Automatic BCS struct definitions for parsing onchain data
 - **Auto-completion**: IDE support with intelligent code completion for Move function arguments
 - **Package resolution**: Support for both MVR-registered packages and local packages
 
@@ -23,9 +23,9 @@ Install the codegen package as a dev dependency:
 npm install -D @mysten/codegen
 ```
 
-## Quick Start
+## Quick start
 
-### 1. Create a configuration file
+### Step 1: Create a configuration file
 
 Create a `sui-codegen.config.ts` file in your project root:
 
@@ -43,7 +43,7 @@ const config: SuiCodegenConfig = {
 
 ```
 
-### 2. Generate TypeScript code
+### Step 2: Generate TypeScript code
 
 Add a script to your `package.json`:
 
@@ -61,35 +61,35 @@ Then run:
 pnpm codegen
 ```
 
-This generates TypeScript code in your configured output directory (e.g., `./src/contracts`).
+This generates TypeScript code in your configured output directory (for example, `./src/contracts`).
 
-## Configuration Options
+## Configuration options
 
 The `SuiCodegenConfig` type supports the following options:
 
 | Option                         | Type                   | Default | Description                                                                                                                                                           |
 | ------------------------------ | ---------------------- | ------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| `output`                       | `string`               | —       | The directory where generated code will be written                                                                                                                    |
-| `packages`                     | `PackageConfig[]`      | —       | Array of Move packages to generate code for                                                                                                                           |
+| `output`                       | `string`               | -       | The directory where generated code will be written                                                                                                                    |
+| `packages`                     | `PackageConfig[]`      | -       | Array of Move packages to generate code for                                                                                                                           |
 | `prune`                        | `boolean`              | `true`  | When enabled, only generates code for the main package and omits dependency modules (dependency types referenced by included types are still generated under `deps/`) |
 | `generateSummaries`            | `boolean`              | `true`  | Automatically run `sui move summary` before generating code. Creates a `package_summaries` directory in your Move package which can be added to `.gitignore`          |
-| `generate`                     | `GenerateOptions`      | —       | Default [generate options](#the-generate-option) (types, functions) for all packages                                                                                  |
+| `generate`                     | `GenerateOptions`      | -       | Default [generate options](#the-generate-option) (types, functions) for all packages                                                                                  |
 | `importExtension`              | `'.js' \| '.ts' \| ''` | `'.js'` | File extension used in generated import statements                                                                                                                    |
 | `includePhantomTypeParameters` | `boolean`              | `false` | Include [phantom type parameters](#phantom-types) as function arguments in generated BCS types                                                                        |
 
-### Package Configuration
+### Package configuration
 
 Each entry in the `packages` array configures a Move package to generate code from. Packages can be
-local (from source) or on-chain (fetched from a network).
+local (from source) or onchain (fetched from a network).
 
-#### Local Packages
+#### Local packages
 
-| Option        | Type                     | Required | Description                                        |
-| ------------- | ------------------------ | -------- | -------------------------------------------------- |
-| `package`     | `string`                 | yes      | Package identifier (e.g., `@local-pkg/my-package`) |
-| `path`        | `string`                 | yes      | Path to the Move package directory                 |
-| `packageName` | `string`                 | no       | Custom name for generated code directory           |
-| `generate`    | `PackageGenerateOptions` | no       | Control what gets generated from this package      |
+| Option        | Type                     | Required | Description                                               |
+| ------------- | ------------------------ | -------- | --------------------------------------------------------- |
+| `package`     | `string`                 | yes      | Package identifier (for example, `@local-pkg/my-package`) |
+| `path`        | `string`                 | yes      | Path to the Move package directory                        |
+| `packageName` | `string`                 | no       | Custom name for generated code directory                  |
+| `generate`    | `PackageGenerateOptions` | no       | Control what gets generated from this package             |
 
 ```typescript
 {
@@ -98,9 +98,9 @@ local (from source) or on-chain (fetched from a network).
 }
 ```
 
-#### On-Chain Packages
+#### Onchain packages
 
-For packages already deployed on-chain, generate code directly from a package ID or MVR name without
+For packages already deployed onchain, generate code directly from a package ID or MVR name without
 needing local source code:
 
 | Option        | Type                     | Required | Description                                   |
@@ -126,7 +126,7 @@ settings override less specific ones.
 
 When no `generate` option is set, everything is generated (all types and functions). Package-level
 `types` and `functions` also default to `true`. In the record form of `modules`, per-module `types`
-and `functions` default to `false` — you opt in to exactly what you need from each module. Use
+and `functions` default to `false`, so you opt in to exactly what you need from each module. Use
 `true` as a shorthand to include everything from a module with package-level defaults.
 
 At the **global** and **package** levels, `types` and `functions` only accept boolean values (or an
@@ -156,30 +156,30 @@ modules: {
 
 Controls which BCS type definitions (structs and enums) are generated:
 
-- `true` — generate all types
-- `false` — skip type generation
-- `string[]` — generate only the listed types by name _(module level only)_
+- `true`: generate all types
+- `false`: skip type generation
+- `string[]`: generate only the listed types by name (module level only)
 
 ### Functions
 
 Controls which Move function wrappers are generated:
 
-- `true` — generate all public functions and private entry functions
-- `false` — skip function generation
-- `string[]` — generate only the listed functions by name; includes private functions _(module level
-  only)_
-- `{ private: 'entry' }` — generate public functions plus private entry functions
-- `{ private: true }` — generate all functions including private
-- `{ private: false }` — only generate public functions
+- `true`: generate all public functions and private entry functions
+- `false`: skip function generation
+- `string[]`: generate only the listed functions by name; includes private functions (module level
+  only)
+- `{ private: 'entry' }`: generate public functions plus private entry functions
+- `{ private: true }`: generate all functions including private
+- `{ private: false }`: only generate public functions
 
 ### Modules
 
 Controls which modules from the package are included. Only available at the package level, not at
 the global level.
 
-- Not set (default) — include all modules
-- `string[]` — only include the listed modules
-- `Record<string, true | { types?, functions? }>` — only include the listed modules, with per-module
+- Not set (default): include all modules
+- `string[]`: only include the listed modules
+- `Record<string, true | { types?, functions? }>`: only include the listed modules, with per-module
   overrides for `types` and `functions`. Use `true` as a shorthand to include everything from a
   module with package-level defaults
 
@@ -198,8 +198,8 @@ Only generate code from specific modules of the Sui framework:
 }
 ```
 
-Only generate a single type from a dependency (functions are omitted automatically since `generate`
-is configured and `functions` is not specified):
+Only generate a single type from a dependency (functions are omitted automatically because
+`generate` is configured and `functions` is not specified):
 
 ```typescript
 {
@@ -267,7 +267,7 @@ src/contracts/
 
 Set `prune: false` to generate all dependency modules with their full types and functions.
 
-## Phantom Types
+## Phantom types
 
 In Move, phantom type parameters are type parameters that only appear at the type level and don't
 affect the runtime data layout of a struct. For example, `Balance<T>` has a phantom type parameter
@@ -279,9 +279,9 @@ public struct Balance<phantom T> has store {
 }
 ```
 
-### Default Behavior
+### Default behavior
 
-By default, codegen excludes phantom type parameters from the generated BCS type functions since
+By default, codegen excludes phantom type parameters from the generated BCS type functions because
 they don't affect serialization. The generated type is a constant rather than a function:
 
 ```typescript
@@ -293,13 +293,13 @@ they don't affect serialization. The generated type is a constant rather than a
 });
 ```
 
-This works correctly for parsing on-chain data because phantom types don't change the binary layout.
+This works correctly for parsing onchain data because phantom types don't change the binary layout.
 
-> **Note:** With the default behavior, phantom parameters appear as literals in the type name (e.g.,
-> `Balance<phantom T>`). These names are useful for debugging but are not valid on-chain type tags. If
+> **Note:** With the default behavior, phantom parameters appear as literals in the type name (for example,
+> `Balance<phantom T>`). These names are useful for debugging but are not valid onchain type tags. If
 > you need valid type names with resolved phantom parameters, enable `includePhantomTypeParameters`.
 
-### Including Phantom Type Parameters
+### Including phantom type parameters
 
 If you need the phantom type parameters as function arguments (for example, to preserve type
 information for other tooling), enable `includePhantomTypeParameters`:
@@ -327,9 +327,9 @@ With this option enabled, phantom type parameters become function arguments:
 }
 ```
 
-## Using Generated Code
+## Using generated code
 
-### Calling Move Functions
+### Calling Move functions
 
 The generated code provides type-safe functions for calling Move functions:
 
@@ -346,9 +346,9 @@ tx.add(
 );
 ```
 
-### Parsing BCS Data
+### Parsing BCS data
 
-Use generated BCS types to parse on-chain object data. Fetch the object with
+Use generated BCS types to parse onchain object data. Fetch the object with
 `include: { content: true }` and pass `object.content` to the generated type's `.parse()` method:
 
 ```typescript
@@ -372,13 +372,13 @@ async function readCounter(client: ClientWithCoreApi, id: string) {
 > contains a full object envelope with additional metadata that will cause parsing to fail. See the
 > [Core API docs](/sui/clients/core#objectbcs) for details.
 
-## Client Configuration
+## Client configuration
 
 ### Using with MVR (Move Version Registry)
 
 If your package is registered on MVR, the generated code works without additional configuration.
 
-### Local Packages
+### Local packages
 
 For local packages using `@local-pkg/*` identifiers, configure your client with package overrides:
 
@@ -431,9 +431,9 @@ const dAppKit = createDAppKit({
 });
 ```
 
-## Related Resources
+## Related resources
 
-- [create-dapp](/dapp-kit/getting-started/create-dapp) - Bootstrap a working dApp with codegen
+- [create-dapp](/dapp-kit/getting-started/create-dapp) - Bootstrap a working app with codegen
   already configured
 - [Sui Move documentation](https://docs.sui.io/concepts/sui-move-concepts)
 - [BCS documentation](/bcs)

package/dist/codegen/llms-index.md

@@ -1,4 +1,4 @@
 # TypeScript Codegen
 > Generate type-safe TypeScript code from Sui Move packages
 
-- [Sui TypeScript Codegen](..md): Generate type-safe TypeScript bindings from on-chain Sui Move packages
+- [Sui TypeScript Codegen](..md): Generate type-safe TypeScript bindings from onchain Sui Move packages.

package/dist/dapp-kit/actions/connect-wallet.md

@@ -1,6 +1,6 @@
 # Connect Wallet
 
-> Programmatically connect to a Sui wallet
+> Programmatically connect to a Sui wallet using the dApp Kit connectWallet action.
 
 The dApp Kit SDK provides an action for wallet connection, allowing users to connect, disconnect,
 and switch between wallets and accounts.
@@ -33,15 +33,15 @@ console.log('Connected accounts:', result.accounts);
 
 ## Parameters
 
-- **`wallet`** - The `UiWallet` instance to connect to
+- **`wallet`:** The `UiWallet` instance to connect to
 - **`account`** (optional) - A specific `UiWalletAccount` to set as the selected account. Defaults
   to the first authorized account
 
-## Return Value
+## Return value
 
 Returns a `Promise` that resolves to an object containing:
 
-- **`accounts`** - Array of authorized `UiWalletAccount` instances
+- **`accounts`:** Array of authorized `UiWalletAccount` instances
 
 ## Example
 

package/dist/dapp-kit/actions/disconnect-wallet.md

@@ -1,6 +1,6 @@
 # Disconnect Wallet
 
-> Programmatically disconnect from a Sui wallet
+> Programmatically disconnect from a Sui wallet using the dApp Kit disconnectWallet action.
 
 The `disconnectWallet` action terminates the connection with the currently connected wallet.
 
@@ -13,9 +13,9 @@ The `disconnectWallet` action terminates the connection with the currently conne
 > if the wallet notification fails, the local state is always cleared to ensure a clean
 > disconnection.
 > 
-> Note that wallets may or may not implement the `disconnect` feature. Calling `disconnectWallet`
-> doesn't necessarily mean that the wallet accounts will be disconnected from the dApp within the
-> wallet itself - this is determined by each wallet's implementation.
+> Wallets might or might not implement the `disconnect` feature. Calling `disconnectWallet`
+> does not necessarily mean that the wallet accounts are disconnected from the app within the
+> wallet itself. This is determined by each wallet's implementation.
 
 ```typescript
 
@@ -30,9 +30,10 @@ await dAppKit.disconnectWallet();
 
 None.
 
-## Return Value
+## Return value
 
 Returns a `Promise` that resolves to `void` when the disconnection is complete.
 
-> The action may throw `WalletNotConnectedError` if no wallet is connected. However, wallet-specific
-> disconnect failures are logged but don't prevent the local connection state from being cleared.
+> The action might throw `WalletNotConnectedError` if no wallet is connected. However,
+> wallet-specific disconnect failures are logged but don't prevent the local connection state from
+> being cleared.

package/dist/dapp-kit/actions/sign-and-execute-transaction.md

@@ -1,9 +1,9 @@
 # Sign and Execute Transaction
 
-> Sign and execute a transaction using the connected wallet
+> Sign and execute a transaction on the Sui network using the connected wallet.
 
 The `signAndExecuteTransaction` action prompts the connected wallet to sign and immediately execute
-a transaction on the Sui network. This is the most common way to execute transactions in your dApp.
+a transaction on the Sui network. This is the most common way to execute transactions in your app.
 
 ## Usage
 
@@ -30,11 +30,11 @@ console.log('Transaction digest:', result.Transaction.digest);
 
 ## Parameters
 
-- **`transaction`** - `Transaction | string` - The transaction to sign and execute. Can be either a
+- **`transaction`:** `Transaction | string`: The transaction to sign and execute. Can be either a
   Transaction instance or base64-encoded bcs bytes for the transaction.
-- **`signal`** (optional) - `AbortSignal` - An abort signal to cancel the transaction request.
+- **`signal`** (optional): `AbortSignal`: An abort signal to cancel the transaction request.
 
-## Return Value
+## Return value
 
 Returns a `Promise` that resolves to a `TransactionResult` discriminated union:
 
@@ -46,14 +46,14 @@ type TransactionResult =
 
 The `Transaction` object contains:
 
-- **`digest`** - `string` - The transaction digest (unique identifier for the executed transaction)
-- **`signatures`** - `string[]` - The signatures as base64-encoded strings
-- **`epoch`** - `string | null` - The epoch in which the transaction was executed
-- **`status`** - `ExecutionStatus` - The execution status with `success: boolean` and
+- **`digest`:** `string`: The transaction digest (unique identifier for the executed transaction)
+- **`signatures`:** `string[]`: The signatures as base64-encoded strings
+- **`epoch`:** `string | null`: The epoch in which the transaction was executed
+- **`status`:** `ExecutionStatus`: The execution status with `success: boolean` and
   `error: string | null`
-- **`effects`** - `TransactionEffects | null` - The parsed transaction effects (may be `null` if
+- **`effects`:** `TransactionEffects | null`: The parsed transaction effects (may be `null` if
   effects parsing fails for unknown effect versions)
-- **`transaction`** - `TransactionData` - The parsed transaction data
+- **`transaction`:** `TransactionData`: The parsed transaction data
 
 ```typescript
 const result = await dAppKit.signAndExecuteTransaction({ transaction });
@@ -70,7 +70,7 @@ console.log('Signatures:', tx.signatures);
 console.log('Epoch:', tx.epoch);
 ```
 
-## Transaction Building
+## Transaction building
 
 When passing a Transaction instance, the action automatically:
 
@@ -79,12 +79,12 @@ When passing a Transaction instance, the action automatically:
 3. Converts it to the appropriate format for the wallet
 4. Submits the transaction to the network
 
-## Wallet Compatibility
+## Wallet compatibility
 
 - The action transparently handles both `sui:signAndExecuteTransaction` and
   `sui:signAndExecuteTransactionBlock` wallet-standard features
 - The wallet handles network submission and response
-- Some wallets (Enoki, Enoki Connect, WalletConnect) may use the dApp Kit client and execute
+- Some wallets (Enoki, Enoki Connect, and WalletConnect) might use the dApp Kit client and execute
   transactions within the application as an implementation detail
 
 ```typescript

package/dist/dapp-kit/actions/sign-personal-message.md

@@ -1,6 +1,6 @@
 # Sign Personal Message
 
-> Sign an arbitrary message with the connected wallet
+> Sign an arbitrary message with the connected wallet for authentication or proof of ownership.
 
 The `signPersonalMessage` action prompts the connected wallet to sign a personal message. This is
 useful for authentication, proof of ownership, or other scenarios where you need cryptographic proof
@@ -25,16 +25,16 @@ console.log('Signature:', result.signature);
 
 ## Parameters
 
-- **`message`** - `Uint8Array` - The message to sign as a byte array
+- **`message`:** `Uint8Array` - The message to sign as a byte array
 
-## Return Value
+## Return value
 
 Returns a `Promise` that resolves to an object containing:
 
-- **`bytes`** - `string` - Base64 encoded message bytes
-- **`signature`** - `string` - Base64 encoded signature
+- **`bytes`:** `string` - Base64 encoded message bytes
+- **`signature`:** `string` - Base64 encoded signature
 
-## Message Format
+## Message format
 
 The message parameter must be a `Uint8Array`. Common patterns for creating byte arrays:
 
@@ -48,9 +48,9 @@ const jsonMessage = new TextEncoder().encode(
 await dAppKit.signPersonalMessage({ message: jsonMessage });
 ```
 
-## Security Considerations
+## Security considerations
 
-### Message Content
+### Message content
 
 - Always display the message content clearly to users before signing
 - Avoid signing opaque or encoded data that users cannot understand

package/dist/dapp-kit/actions/sign-transaction.md

@@ -1,6 +1,6 @@
 # Sign Transaction
 
-> Sign a transaction without executing it
+> Sign a Sui transaction without executing it for deferred or multi-signature scenarios.
 
 The `signTransaction` action prompts the connected wallet to sign a transaction without executing
 it. This is useful when you need a signed transaction for later execution or for multi-signature
@@ -26,16 +26,16 @@ const { bytes, signature } = await dAppKit.signTransaction({
 
 ## Parameters
 
-- **`transaction`** - `Transaction | string` - The transaction to sign. Can be either a Transaction
+- **`transaction`:** `Transaction | string` - The transaction to sign. Can be either a Transaction
   instance or base64-encoded bcs bytes for the transaction.
 - **`signal`** (optional) - `AbortSignal` - An abort signal to cancel the signing request.
 
-## Return Value
+## Return value
 
 Returns a `Promise` that resolves to an object containing:
 
-- **`bytes`** - `string` - The signed transaction as a base64-encoded BCS string
-- **`signature`** - `string` - The signature as a base64-encoded string
+- **`bytes`:** `string` - The signed transaction as a base64-encoded BCS string
+- **`signature`:** `string` - The signature as a base64-encoded string
 
 ```typescript
 const result = await dAppKit.signTransaction({ transaction });
@@ -43,7 +43,7 @@ console.log('Signed transaction bytes:', result.bytes);
 console.log('Signature:', result.signature);
 ```
 
-## Transaction Building
+## Transaction building
 
 When passing a Transaction instance, the action automatically:
 
@@ -51,7 +51,7 @@ When passing a Transaction instance, the action automatically:
 2. Builds the transaction using the current network's client
 3. Converts it to the appropriate format for the wallet
 
-## Wallet Compatibility
+## Wallet compatibility
 
 - The action transparently handles both `sui:signTransaction` and `sui:signTransactionBlock`
   wallet-standard features

package/dist/dapp-kit/actions/switch-account.md

@@ -1,13 +1,13 @@
 # Switch Account
 
-> Switch the active account in the connected wallet
+> Switch the active account in the connected wallet using the dApp Kit switchAccount action.
 
 The `switchAccount` action changes the currently selected account to a different account from the
 connected wallet.
 
-> **Note:** The "current account" is a dApp Kit concept that tracks which account is active within your
-> application. Changing the active account in the dApp does not affect the wallet itself, and
-> wallets are not notified when the active account changes.
+> **Note:** The current account is a dApp Kit concept that tracks which account is active within your
+> application. Changing the active account in the app does not affect the wallet itself, and wallets
+> are not notified when the active account changes.
 
 > Account switching is integrated into the [Connect Button](../web-components/connect-button) Web
 > Component. When a wallet is connected with multiple accounts, the button provides an account
@@ -29,9 +29,9 @@ dAppKit.switchAccount({
 
 ## Parameters
 
-- **`account`** - `UiWalletAccount` - The account to switch to. Must be an account that belongs to
+- **`account`:** `UiWalletAccount` - The account to switch to. Must be an account that belongs to
   the currently connected wallet.
 
-## Return Value
+## Return value
 
 Returns `void`. The action completes synchronously and updates the connection state immediately.

package/dist/dapp-kit/actions/switch-network.md

@@ -1,12 +1,12 @@
 # Switch Network
 
-> Switch the active network for the dApp Kit instance
+> Switch the active network for the dApp Kit instance between mainnet, testnet, and other networks.
 
 The `switchNetwork` action changes the currently selected network that the dApp Kit client is
 configured to use.
 
-> **Note:** Network switching only affects your dApp's client connection. The wallet itself is not affected by
-> this change, and wallets are not notified when the network changes in the dApp.
+> **Note:** Network switching only affects your app's client connection. The wallet itself is not affected by
+> this change, and wallets are not notified when the network changes in the app.
 
 ## Usage
 
@@ -29,9 +29,9 @@ dAppKit.switchNetwork('testnet');
 
 ## Parameters
 
-- **`network`** - `TNetworks[number]` - The network to switch to. Must be one of the networks
+- **`network`:** `TNetworks[number]`: The network to switch to. Must be one of the networks
   configured when creating the dApp Kit instance.
 
-## Return Value
+## Return value
 
 Returns `void`. The action completes synchronously and updates the network state immediately.

package/dist/dapp-kit/dapp-kit-instance.md

@@ -2,13 +2,13 @@
 
 > Create and configure a DAppKit instance for wallet and client management
 
-The `createDAppKit` function is the foundation of your Sui dApp. It creates an instance that manages
+The `createDAppKit` function is the foundation of your Sui app. It creates an instance that manages
 wallet connections, network configuration, and provides access to the Sui client.
 
-## Creating a dApp Kit Instance
+## Creating a dApp Kit instance
 
 The core of the dApp Kit SDK is the `createDAppKit` function, which creates an instance that manages
-all dApp functionality:
+all app functionality:
 
 ```typescript
 
@@ -35,22 +35,23 @@ This instance provides:
 
 ## Parameters
 
-- **autoConnect** (optional) - Enables automatically connecting to the most recently used wallet
+- **autoConnect** (optional): Enables automatically connecting to the most recently used wallet
   account (default: `true`)
-- **networks** - A list of networks supported by the application (e.g. `['mainnet', 'testnet']`)
-- **defaultNetwork** (optional) - Initial network to use (default: first network in the array)
-- **createClient** - Creates a new client instance for the given network
-- **enableBurnerWallet** (optional) - Enable development-only burner wallet (default: `false`)
-- **storage** (optional) - Configures how the most recently connected to wallet account is stored
+- **networks:** A list of networks supported by the application (for example,
+  `['mainnet', 'testnet']`)
+- **defaultNetwork** (optional): Initial network to use (default: first network in the array)
+- **createClient:** Creates a new client instance for the given network
+- **enableBurnerWallet** (optional): Enable development-only burner wallet (default: `false`)
+- **storage** (optional): Configures how the most recently connected to wallet account is stored
   (default: `localStorage`, set to `null` to disable)
-- **storageKey** (optional) - The key to use to store the most recently connected wallet account
+- **storageKey** (optional): The key to use to store the most recently connected wallet account
   (default: `'mysten-dapp-kit:selected-wallet-and-address'`)
-- **walletInitializers** (optional) - A list of wallet initializers used for registering additional
+- **walletInitializers** (optional): A list of wallet initializers used for registering additional
   wallet standard wallets.
-- **slushWalletConfig** (optional) - Configuration for Slush wallet (set to `null` to disable the
+- **slushWalletConfig** (optional): Configuration for Slush wallet (set to `null` to disable the
   wallet)
 
-## Return Value
+## Return value
 
 ```ts
 {
@@ -77,7 +78,7 @@ This instance provides:
 
 Read more about [actions](./actions/connect-wallet) and [stores](./state).
 
-## Basic Usage
+## Basic usage
 
 ```ts
 // dapp-kit.ts
@@ -111,7 +112,7 @@ const GRPC_URLS = {
 > If you use the React bindings, see [Getting Started in React](./getting-started/react) and
 > [DAppKitProvider](./react/dapp-kit-provider).
 
-## Development Configuration
+## Development configuration
 
 For development environments, enable the burner wallet:
 
@@ -124,11 +125,11 @@ For development environments, enable the burner wallet:
 });
 ```
 
-## Auto-Connect Behavior
+## Auto-connect behavior
 
 By default, dApp Kit automatically reconnects to the previously connected wallet.
 
-### Disabling Auto-Connect
+### Disabling auto-connect
 
 ```typescript
 
@@ -139,7 +140,7 @@ By default, dApp Kit automatically reconnects to the previously connected wallet
 });
 ```
 
-## Custom Wallet Integration
+## Custom wallet integration
 
 Add support for custom wallets using wallet initializers: