@mysten/sui 2.16.0 → 2.16.2

package/docs/migrations/sui-2.0/dapp-kit.md

@@ -1,30 +1,30 @@
 # @mysten/dapp-kit
 
-> Migrate @mysten/dapp-kit to 2.0
+> Migrate @mysten/dapp-kit to the new dapp-kit-react package in 2.0.
 
 This guide helps you migrate from the original `@mysten/dapp-kit` (legacy) to the new
 `@mysten/dapp-kit-react` package.
 
-> **Note:** The legacy `@mysten/dapp-kit` package will continue to work with the latest SDK, but it
-> only supports JSON-RPC and will not receive further updates. We recommend migrating to
+> **Note:** The legacy `@mysten/dapp-kit` package will continue to work with the latest SDK, but it only
+> supports JSON-RPC and will not receive further updates. We recommend migrating to
 > `@mysten/dapp-kit-react` for new features and gRPC support.
 
 ## Overview
 
-The new dApp Kit SDK represents a complete rewrite with these key changes:
+The new dApp kit SDK represents a complete rewrite with these key changes:
 
-- **Framework agnostic**: Split into `@mysten/dapp-kit-core` (framework-agnostic) and
+- Framework agnostic: Split into `@mysten/dapp-kit-core` (framework-agnostic) and
   `@mysten/dapp-kit-react` (React bindings)
-- **No React Query dependency**: Direct promise-based API instead of mutation hooks
-- **Web Components**: UI components built with Lit Elements for cross-framework compatibility
-- **Smaller bundle size**: No React Query dependency, lighter state management with nanostores
-- **Better SSR support**: Compatible with SSR frameworks like Next.js
-- **Cross-framework compatibility**: Core functionality can be used in vanilla JS, Vue, React, and
-  other frameworks
+- No React Query dependency: Direct promise-based API instead of mutation hooks
+- Web Components: UI components built with Lit Elements for cross-framework compatibility
+- Smaller bundle size: No React Query dependency, lighter state management with nanostores
+- Better SSR support: Compatible with SSR frameworks like Next.js
+- Cross-framework compatibility: Core functionality can be used in vanilla JS, Vue, React, and other
+  frameworks
 
-## Step-by-Step Migration
+## Step-by-step migration
 
-### 1. Update Dependencies
+### Step 1: Update dependencies
 
 Remove the old package and install the new ones:
 
@@ -33,9 +33,9 @@ npm uninstall @mysten/dapp-kit
 npm i @mysten/dapp-kit-react @mysten/dapp-kit-core @mysten/sui
 ```
 
-### 2. Create dApp Kit Instance
+### Step 2: Create dApp Kit instance
 
-Create a new instance of the dApp Kit using the `createDAppKit` function and register the global
+Create a new instance of the dApp kit using the `createDAppKit` function and register the global
 type.
 
 ```tsx
@@ -59,12 +59,12 @@ declare module '@mysten/dapp-kit-react' {
 }
 ```
 
-### 3. Register Types
+### Step 3: Register types
 
-The `declare module` block in the previous step registers your dApp Kit instance's type globally.
+The `declare module` block in the previous step registers your dApp kit instance's type globally.
 This enables all hooks like `useDAppKit()`, `useCurrentNetwork()`, and `useCurrentClient()` to
-automatically infer the correct types based on your configuration (e.g., your specific networks and
-client type).
+automatically infer the correct types based on your configuration (for example, your specific
+networks and client type).
 
 ```tsx
 declare module '@mysten/dapp-kit-react' {
@@ -83,9 +83,9 @@ const connection = useWalletConnection({ dAppKit });
 const network = useCurrentNetwork({ dAppKit });
 ```
 
-### 4. Replace Provider Setup
+### Step 4: Replace provider setup
 
-Replace the nested dApp Kit providers with a single unified provider. You can keep your existing
+Replace the nested dApp kit providers with a single unified provider. You can keep your existing
 `QueryClientProvider` for data fetching.
 
 ```diff
@@ -117,7 +117,7 @@ Replace the nested dApp Kit providers with a single unified provider. You can ke
   }
 ```
 
-### 5. Configuration Option Changes
+### Step 5: Configuration option changes
 
 The `createDAppKit` function has different configuration options than the old `WalletProvider`:
 
@@ -136,24 +136,24 @@ The `createDAppKit` function has different configuration options than the old `W
 | `theme`                | -                     | Removed (UI components are now web components with built-in styling) |
 | -                      | `walletInitializers`  | New option for registering custom wallets                            |
 
-### 6. Update Hook Usage
+### Step 6: Update hook usage
 
-The new dApp Kit has a dramatically simplified hook API. Most hooks from the original version have
+The new dApp kit has a dramatically simplified hook API. Most hooks from the original version have
 been replaced with direct action calls through `useDAppKit()`.
 
 **Available hooks in the new version:**
 
-- `useDAppKit()` - Access the dAppKit instance for calling actions
-- `useCurrentClient()` - Get the blockchain client (renamed from `useSuiClient`)
-- `useCurrentAccount()` - Get the current connected account
-- `useCurrentWallet()` - Get the current connected wallet
-- `useWallets()` - Get the list of available wallets
-- `useWalletConnection()` - Get the current wallet connection status
-- `useCurrentNetwork()` - Get the current network
+- `useDAppKit()`: Access the dAppKit instance for calling actions
+- `useCurrentClient()`: Get the blockchain client (renamed from `useSuiClient`)
+- `useCurrentAccount()`: Get the current connected account
+- `useCurrentWallet()`: Get the current connected wallet
+- `useWallets()`: Get the list of available wallets
+- `useWalletConnection()`: Get the current wallet connection status
+- `useCurrentNetwork()`: Get the current network
 
 **Removed hooks:**
 
-All wallet action hooks have been replaced with direct action calls via `useDAppKit()`:
+All wallet action hooks have been replaced with direct action calls through `useDAppKit()`:
 
 - `useConnectWallet` -> Use `dAppKit.connectWallet()`
 - `useDisconnectWallet` -> Use `dAppKit.disconnectWallet()`
@@ -176,16 +176,16 @@ Other removed hooks:
 - `useAccounts` -> Use `useWalletConnection()` to access `connection.wallet.accounts`
 - `useWalletStore` -> Use specific hooks like `useWalletConnection()` instead
 
-### 7. Replace Mutation Patterns
+### Step 7: Replace mutation patterns
 
 The built-in mutation hooks have been removed. Use TanStack Query's `useMutation` with
 `useDAppKit()` to get similar functionality.
 
 **Chain parameter replaced with network:**
 
-In the old dapp-kit, you could optionally pass a `chain` parameter (e.g., `sui:mainnet`) to methods
-like `signTransaction` and `signAndExecuteTransaction`. In the new dapp-kit, use the `network`
-parameter instead - the chain is automatically derived from the network.
+In the old dApp kit, you could optionally pass a `chain` parameter (for example, `sui:mainnet`) to
+methods like `signTransaction` and `signAndExecuteTransaction`. In the new dApp kit, use the
+`network` parameter instead - the chain is automatically derived from the network.
 
 ```diff
 - const { mutateAsync: signAndExecute } = useSignAndExecuteTransaction();
@@ -249,7 +249,7 @@ If you don't need React Query's state management, you can call `dAppKit` methods
 }
 ```
 
-### 8. Replace Data Fetching Patterns
+### Step 8: Replace data fetching patterns
 
 The built-in data fetching hooks have been removed. Use TanStack Query's `useQuery` with
 `useCurrentClient()` to get similar functionality:
@@ -295,17 +295,17 @@ If you don't need React Query's caching and state management, you can fetch data
 }
 ```
 
-### 9. Update The Remaining Code
+### Step 9: Update the remaining code
 
-The following hooks from the original dApp Kit are not available anymore:
+The following hooks from the original dApp kit are not available anymore:
 
 - `useSuiClientQuery` → Use `useQuery` from `@tanstack/react-query`
 - `useSuiClientMutation` → Use `useMutation` from `@tanstack/react-query`
 - `useSuiClientInfiniteQuery` → Use `useInfiniteQuery` from `@tanstack/react-query`
 - `useResolveSuiNSNames` → Use `useCurrentClient()` with the suins extension
 
-> **Warning:** The `reportTransactionEffects` feature is planned for deprecation in the
-> [Wallet Standard](https://docs.sui.io/standards/wallet-standard) and so the dApp Kit provides no
+> **Warning:** The `reportTransactionEffects` feature is planned for deprecation in the [Wallet
+> Standard](https://docs.sui.io/standards/wallet-standard) and so the dApp kit provides no
 > replacement.
 
 The following have been removed:
@@ -314,18 +314,18 @@ The following have been removed:
 - `reportTransactionEffects` callback from `useSignTransaction`
 - Automatic transaction effects reporting from `useSignAndExecuteTransaction`
 
-## CSS and Theming Changes
+## CSS and theming changes
 
-The new dApp Kit no longer bundles a CSS file. If you were importing the old CSS file, remove the
+The new dApp kit no longer bundles a CSS file. If you were importing the old CSS file, remove the
 import:
 
 ```diff
 - import '@mysten/dapp-kit/dist/full/index.css';
 ```
 
-The new dApp Kit uses web components with built-in styling that can be customized using CSS custom
+The new dApp kit uses web components with built-in styling that can be customized using CSS custom
 properties. See the [Theming documentation](/dapp-kit/theming) for details on customizing the
-appearance of dApp Kit components.
+appearance of dApp kit components.
 
 **Quick theme setup:**
 
@@ -342,9 +342,9 @@ appearance of dApp Kit components.
 
 ## Removing TanStack Query
 
-If you were only using `@tanstack/react-query` for dApp Kit and don't need it for other parts of
+If you were only using `@tanstack/react-query` for dApp kit and don't need it for other parts of
 your application, you can now remove it:
 
 ```bash
 npm uninstall @tanstack/react-query
-```
+```

package/docs/migrations/sui-2.0/deepbook-v3.md

@@ -1,6 +1,6 @@
 # @mysten/deepbook-v3
 
-> Migrate @mysten/deepbook-v3 to 2.0
+> Migrate @mysten/deepbook-v3 to 2.0 with client extension pattern.
 
 This package now exports a client extension that integrates with Sui clients.
 
@@ -30,4 +30,4 @@ This package now exports a client extension that integrates with Sui clients.
 
 - await deepBookClient.checkManagerBalance(manager, asset);
 + await client.deepbook.checkManagerBalance(manager, asset);
-```
+```

package/docs/migrations/sui-2.0/index.md

@@ -1,6 +1,6 @@
 # Migrate to 2.0
 
-> Migration guide for Sui TypeScript SDK 2.0
+> Migration guide for Sui TypeScript SDK 2.0 covering all @mysten packages.
 
 This guide covers the breaking changes across the latest release of all the `@mysten/*` packages.
 
@@ -9,24 +9,24 @@ SDKs. These releases also include removals of deprecated APIs, some renaming for
 and significant internal refactoring to improve maintainability. Starting with this release, Mysten
 packages will now be published as ESM only packages.
 
-## Quick Reference
+## Quick reference
 
 | Package                                                               | Key Changes                                                                              |
 | --------------------------------------------------------------------- | ---------------------------------------------------------------------------------------- |
-| [@mysten/sui](/sui/migrations/sui-2.0/sui)                            | Client API stabilization, SuiClient removal, BCS schema alignment, transaction executors |
-| [@mysten/dapp-kit](/sui/migrations/sui-2.0/dapp-kit)                  | Complete rewrite with framework-agnostic core                                            |
-| [@mysten/kiosk](/sui/migrations/sui-2.0/kiosk)                        | Client extension pattern, low-level helpers removed, KioskTransaction pattern            |
-| [@mysten/zksend](/sui/migrations/sui-2.0/zksend)                      | Client extension pattern                                                                 |
-| [@mysten/suins](/sui/migrations/sui-2.0/suins)                        | Client extension pattern                                                                 |
-| [@mysten/deepbook-v3](/sui/migrations/sui-2.0/deepbook-v3)            | Client extension pattern                                                                 |
-| [@mysten/walrus](/sui/migrations/sui-2.0/walrus)                      | Client extension pattern, requires client instead of RPC URL                             |
-| [@mysten/seal](/sui/migrations/sui-2.0/seal)                          | Client extension pattern                                                                 |
-| [@mysten/wallet-standard](/sui/migrations/sui-2.0/wallet-builders)    | Removal of reportTransactionEffects, new core API response format                        |
+| [`@mysten/sui`](/sui/migrations/sui-2.0/sui)                          | Client API stabilization, SuiClient removal, BCS schema alignment, transaction executors |
+| [`@mysten/dapp-kit`](/sui/migrations/sui-2.0/dapp-kit)                | Complete rewrite with framework-agnostic core                                            |
+| [`@mysten/kiosk`](/sui/migrations/sui-2.0/kiosk)                      | Client extension pattern, low-level helpers removed, KioskTransaction pattern            |
+| [`@mysten/zksend`](/sui/migrations/sui-2.0/zksend)                    | Client extension pattern                                                                 |
+| [`@mysten/suins`](/sui/migrations/sui-2.0/suins)                      | Client extension pattern                                                                 |
+| [`@mysten/deepbook-v3`](/sui/migrations/sui-2.0/deepbook-v3)          | Client extension pattern                                                                 |
+| [`@mysten/walrus`](/sui/migrations/sui-2.0/walrus)                    | Client extension pattern, requires client instead of RPC URL                             |
+| [`@mysten/seal`](/sui/migrations/sui-2.0/seal)                        | Client extension pattern                                                                 |
+| [`@mysten/wallet-standard`](/sui/migrations/sui-2.0/wallet-builders)  | Removal of reportTransactionEffects, new core API response format                        |
 | [Migrating from JSON-RPC](/sui/migrations/sui-2.0/json-rpc-migration) | Migrate from deprecated JSON-RPC to gRPC and GraphQL                                     |
 
-## Common Migration Patterns
+## Common migration patterns
 
-### ESM Migration
+### ESM migration
 
 All `@mysten/*` packages are now ESM only. If your project does not already use ESM, you will need
 to add `"type": "module"` to your `package.json`:
@@ -49,13 +49,13 @@ need to update your `tsconfig.json` to use `"NodeNext"`, `"Node16"`, or `"Bundle
 }
 ```
 
-This enables proper resolution of the SDK's subpath exports (e.g., `@mysten/sui/client`,
+This enables proper resolution of the SDK's subpath exports (for example, `@mysten/sui/client`,
 `@mysten/sui/transactions`).
 
-If you maintain a library that depends on any of the `@mysten/*` packages, you may also need to
+If you maintain a library that depends on any of the `@mysten/*` packages, you might also need to
 update your library to be ESM only to ensure it works correctly everywhere.
 
-Applications using bundlers and recent Node.js versions (>=22) may still work when using `require`
+Applications using bundlers and recent Node.js versions (>=22) might still work when using `require`
 to load ESM packages, but we recommend migrating to ESM.
 
 **Why ESM only?** Many packages in the ecosystem (specifically critical cryptography dependencies)
@@ -63,7 +63,7 @@ are now published as ESM only. Supporting CommonJS has prevented us from using t
 of these dependencies, making our SDKs harder to maintain and risking missing critical security
 updates.
 
-### Client Migration
+### Client migration
 
 The most common change across all SDKs is migrating from `SuiClient` to `SuiJsonRpcClient`:
 
@@ -78,7 +78,7 @@ The most common change across all SDKs is migrating from `SuiClient` to `SuiJson
 + });
 ```
 
-We also recommend moving from the deprecated JSON RPC Apis to the new gRPC API as soon as possible:
+We also recommend moving from the deprecated JSON RPC APIs to the new gRPC API as soon as possible:
 
 ```diff
 - import { SuiJsonRpcClient } from '@mysten/sui/jsonRpc';
@@ -91,7 +91,7 @@ We also recommend moving from the deprecated JSON RPC Apis to the new gRPC API a
 The gRPC runs on full nodes so in most cases you should be able to use the same URLs when migrating
 to gRPC.
 
-### Network Parameter Required
+### Network parameter required
 
 All client constructors now require an explicit `network` parameter:
 
@@ -112,46 +112,47 @@ const grpcClient = new SuiGrpcClient({
 });
 ```
 
-### ClientWithCoreApi Interface
+### `ClientWithCoreApi` Interface
 
 Many SDK methods now accept any client implementing `ClientWithCoreApi`, enabling use with JSON-RPC,
 GraphQL, or gRPC transports:
 
 ```ts
+
 // All of these work with APIs that accept ClientWithCoreApi
 const jsonRpcClient = new SuiJsonRpcClient({ url, network: 'mainnet' });
 const graphqlClient = new SuiGraphQLClient({ url, network: 'mainnet' });
 const grpcClient = new SuiGrpcClient({ baseUrl, network: 'mainnet' });
 ```
 
-## Package-Specific Guides
+## Package-specific guides
 
 For detailed migration instructions, see the SDK-specific guides:
 
-- **[@mysten/sui](/sui/migrations/sui-2.0/sui)** - Core SDK changes including client API, BCS
+- **[`@mysten/sui`](/sui/migrations/sui-2.0/sui):** Core SDK changes including client API, BCS
   schemas, transactions, zkLogin, and GraphQL
-- **[@mysten/dapp-kit](/sui/migrations/sui-2.0/dapp-kit)** - Complete migration guide for the new
-  dApp Kit architecture
-- **[@mysten/kiosk](/sui/migrations/sui-2.0/kiosk)** - Kiosk SDK now exports a client extension,
+- **[`@mysten/dapp-kit`](/sui/migrations/sui-2.0/dapp-kit):** Complete migration guide for the new
+  dApp kit architecture
+- **[`@mysten/kiosk`](/sui/migrations/sui-2.0/kiosk):** Kiosk SDK now exports a client extension,
   low-level helpers removed
-- **[@mysten/zksend](/sui/migrations/sui-2.0/zksend)** - zkSend SDK now exports a client extension
-- **[@mysten/suins](/sui/migrations/sui-2.0/suins)** - SuiNS now exports a client extension
-- **[@mysten/deepbook-v3](/sui/migrations/sui-2.0/deepbook-v3)** - DeepBook DEX now exports a client
-  extension
-- **[@mysten/walrus](/sui/migrations/sui-2.0/walrus)** - Walrus storage now exports a client
+- **[`@mysten/zksend`](/sui/migrations/sui-2.0/zksend):** zkSend SDK now exports a client extension
+- **[`@mysten/suins`](/sui/migrations/sui-2.0/suins):** SuiNS now exports a client extension
+- **[`@mysten/deepbook-v3`](/sui/migrations/sui-2.0/deepbook-v3):** DeepBook DEX now exports a
+  client extension
+- **[`@mysten/walrus`](/sui/migrations/sui-2.0/walrus):** Walrus storage now exports a client
   extension
-- **[@mysten/seal](/sui/migrations/sui-2.0/seal)** - Seal encryption now exports a client extension
+- **[`@mysten/seal`](/sui/migrations/sui-2.0/seal):** Seal encryption now exports a client extension
 
-## Transport Migration
+## Transport migration
 
-- **[Migrating from JSON-RPC](/sui/migrations/sui-2.0/json-rpc-migration)** - Migrate from the
+- **[Migrating from JSON-RPC](/sui/migrations/sui-2.0/json-rpc-migration):** Migrate from the
   deprecated JSON-RPC client to gRPC and GraphQL
 
-## Ecosystem Migration Guides
+## Ecosystem migration guides
 
 For wallet builders and SDK maintainers building on the Sui ecosystem:
 
-- **[Wallet Builders](/sui/migrations/sui-2.0/wallet-builders)** - Guide for wallet implementations
+- **[Wallet builders](/sui/migrations/sui-2.0/wallet-builders):** Guide for wallet implementations
   adapting to `reportTransactionEffects` removal and new core API response format
-- **[SDK Maintainers](/sui/migrations/sui-2.0/sdk-maintainers)** - Guide for SDK authors migrating
-  to `ClientWithCoreApi` and the new transport-agnostic architecture
+- **[SDK maintainers](/sui/migrations/sui-2.0/sdk-maintainers):** Guide for SDK authors migrating to
+  `ClientWithCoreApi` and the new transport-agnostic architecture

package/docs/migrations/sui-2.0/json-rpc-migration.md

@@ -1,21 +1,21 @@
 # Migrating from JSON-RPC
 
-> Migrate from JSON-RPC to the new Core API
+> Migrate from JSON-RPC to the new Core API using SuiGrpcClient or SuiGraphQLClient.
 
 This guide covers migrating from `SuiJsonRpcClient` to the new client APIs. The JSON-RPC API is
 being deprecated in favor of `SuiGrpcClient` and `SuiGraphQLClient`.
 
-> **Note:** We recommend using `SuiGrpcClient` for most operations and `SuiGraphQLClient` for
-> complex queries like filtering transactions and events.
+> **Note:** We recommend using `SuiGrpcClient` for most operations and `SuiGraphQLClient` for complex queries
+> like filtering transactions and events.
 
-## Choosing a Client
+## Choosing a client
 
 | Client             | Best For                                                        |
 | ------------------ | --------------------------------------------------------------- |
 | `SuiGrpcClient`    | Most operations, SDK integrations, real-time data               |
 | `SuiGraphQLClient` | Complex queries, filtering transactions/events, historical data |
 
-## Quick Migration to gRPC
+## Quick migration to gRPC
 
 For most use cases, migrate to `SuiGrpcClient`:
 
@@ -35,13 +35,13 @@ For most use cases, migrate to `SuiGrpcClient`:
 
 Both clients use the same full node URLs, so you can use the same endpoint when migrating.
 
-## Core API Methods
+## Core API methods
 
 The gRPC client should work with almost all mysten SDKs as a drop in replacement for the JSON-RPC
 client. When using the client directly, the methods and data returned will not be exactly the same
 as what was available in JSON-RPC.
 
-## Methods Replaced by Core API
+## Methods replaced by core API
 
 These JSON-RPC methods have direct replacements in the core API:
 
@@ -88,30 +88,31 @@ These JSON-RPC methods have direct replacements in the core API:
 + });
 ```
 
-## Methods Replaced by gRPC Services
+## Methods replaced by gRPC services
 
 These JSON-RPC methods can be replaced by calling gRPC service clients directly:
 
-| JSON-RPC Method                     | gRPC Service Replacement          |
-| ----------------------------------- | --------------------------------- |
-| `getCheckpoint`                     | `ledgerService.getCheckpoint`     |
-| `getCheckpoints`                    | `ledgerService.listCheckpoints`   |
-| `getLatestCheckpointSequenceNumber` | `ledgerService.getCheckpoint`     |
-| `getEpochs`                         | `ledgerService.listEpochs`        |
-| `getCurrentEpoch`                   | `ledgerService.getEpoch`          |
-| `getLatestSuiSystemState`           | `ledgerService.getSystemState`    |
-| `getCommitteeInfo`                  | `ledgerService.getCommittee`      |
-| `getValidatorsApy`                  | `ledgerService.getValidators`     |
-| `getProtocolConfig`                 | `ledgerService.getProtocolConfig` |
-| `getNormalizedMoveModule`           | `movePackageService.getModule`    |
-| `getNormalizedMoveModulesByPackage` | `movePackageService.getPackage`   |
-| `getNormalizedMoveStruct`           | `movePackageService.getStruct`    |
-| `resolveNameServiceAddress`         | `nameService.lookupName`          |
-| `resolveNameServiceNames`           | `nameService.reverseLookupName`   |
-
-### Example: Using gRPC Service Clients
+| JSON-RPC Method                     | gRPC Service Replacement                                        |
+| ----------------------------------- | --------------------------------------------------------------- |
+| `getCheckpoint`                     | `ledgerService.getCheckpoint`                                   |
+| `getCheckpoints`                    | `ledgerService.listCheckpoints`                                 |
+| `getLatestCheckpointSequenceNumber` | `ledgerService.getCheckpoint`                                   |
+| `getEpochs`                         | `ledgerService.listEpochs`                                      |
+| `getCurrentEpoch`                   | `ledgerService.getEpoch`                                        |
+| `getLatestSuiSystemState`           | `ledgerService.getSystemState`                                  |
+| `getCommitteeInfo`                  | `ledgerService.getCommittee`                                    |
+| `getValidatorsApy`                  | `ledgerService.getValidators`                                   |
+| `getProtocolConfig`                 | `ledgerService.getProtocolConfig`                               |
+| `getNormalizedMoveModule`           | `movePackageService.getPackage` (response includes all modules) |
+| `getNormalizedMoveModulesByPackage` | `movePackageService.getPackage`                                 |
+| `getNormalizedMoveStruct`           | `movePackageService.getDatatype`                                |
+| `resolveNameServiceAddress`         | `nameService.lookupName`                                        |
+| `resolveNameServiceNames`           | `nameService.reverseLookupName`                                 |
+
+### Example: using gRPC service clients
 
 ```typescript
+
 const client = new SuiGrpcClient({
 	baseUrl: 'https://fullnode.mainnet.sui.io:443',
 	network: 'mainnet',
@@ -125,10 +126,16 @@ const { response } = await client.ledgerService.getCheckpoint({
 // Get current epoch
 const { response: epoch } = await client.ledgerService.getEpoch({});
 
-// Get Move module information
-const { response: module } = await client.movePackageService.getModule({
+// Get Move package information (includes all modules)
+const { response: pkg } = await client.movePackageService.getPackage({
+	packageId: '0x2',
+});
+
+// Get a specific Move datatype (struct or enum)
+const { response: datatype } = await client.movePackageService.getDatatype({
 	packageId: '0x2',
 	moduleName: 'coin',
+	name: 'Coin',
 });
 
 // Resolve SuiNS name
@@ -137,7 +144,7 @@ const { response: address } = await client.nameService.lookupName({
 });
 ```
 
-## Methods Requiring GraphQL
+## Methods requiring GraphQL
 
 Some JSON-RPC methods don't have gRPC equivalents and require using `SuiGraphQLClient` instead:
 
@@ -155,16 +162,17 @@ Some JSON-RPC methods don't have gRPC equivalents and require using `SuiGraphQLC
 | `getAddressMetrics`         | Use indexer                        |
 | `getMoveCallMetrics`        | Use indexer                        |
 
-### Setting Up GraphQL Client
+### Setting up GraphQL client
 
 ```typescript
+
 const graphqlClient = new SuiGraphQLClient({
 	url: 'https://sui-mainnet.mystenlabs.com/graphql',
 	network: 'mainnet',
 });
 ```
 
-### Querying Transactions
+### Querying transactions
 
 Replace `queryTransactionBlocks` with a GraphQL query:
 
@@ -200,14 +208,14 @@ const result = await graphqlClient.query({
 
 **Available transaction filters:**
 
-- `sentAddress` - Filter by sender address
-- `affectedAddress` - Filter by any address involved in the transaction
-- `affectedObject` - Filter by object ID that was affected
-- `function` - Filter by Move function called (e.g., `0x2::coin::transfer`)
-- `kind` - Filter by transaction kind (`SYSTEM` or `PROGRAMMABLE`)
+- `sentAddress`: Filter by sender address
+- `affectedAddress`: Filter by any address involved in the transaction
+- `affectedObject`: Filter by object ID that was affected
+- `function`: Filter by Move function called (for example, `0x2::coin::transfer`)
+- `kind`: Filter by transaction kind (`SYSTEM` or `PROGRAMMABLE`)
 - `atCheckpoint` / `beforeCheckpoint` / `afterCheckpoint` - Filter by checkpoint
 
-### Querying Events
+### Querying events
 
 Replace `queryEvents` with a GraphQL query:
 
@@ -247,12 +255,12 @@ const result = await graphqlClient.query({
 
 **Available event filters:**
 
-- `type` - Filter by event type (package, package::module, or full type)
-- `module` - Filter by emitting module
-- `sender` - Filter by transaction sender
-- `atCheckpoint` / `beforeCheckpoint` / `afterCheckpoint` - Filter by checkpoint
+- `type`: Filter by event type (package, package::module, or full type)
+- `module`: Filter by emitting module
+- `sender`: Filter by transaction sender
+- `atCheckpoint` / `beforeCheckpoint` / `afterCheckpoint`: Filter by checkpoint
 
-### Fetching Multiple Transactions
+### Fetching multiple transactions
 
 Replace `multiGetTransactionBlocks` with a GraphQL query:
 
@@ -276,7 +284,7 @@ const result = await graphqlClient.query({
 });
 ```
 
-### Querying Historical Objects
+### Querying historical objects
 
 Replace `tryGetPastObject` with a GraphQL query specifying a version:
 
@@ -304,7 +312,7 @@ const result = await graphqlClient.query({
 });
 ```
 
-### Querying Coin Metadata
+### Querying coin metadata
 
 Replace `getCoinMetadata` and `getTotalSupply` with a GraphQL query:
 
@@ -328,7 +336,7 @@ const result = await graphqlClient.query({
 });
 ```
 
-### Querying Staked SUI
+### Querying staked SUI
 
 Replace `getStakes` with a GraphQL query:
 
@@ -356,10 +364,10 @@ const result = await graphqlClient.query({
 });
 ```
 
-## Response Format Differences
+## Response format differences
 
 The gRPC client uses the core API response format, which differs from JSON-RPC responses. See the
-[@mysten/sui migration guide](/sui/migrations/sui-2.0/sui#transaction-executors-now-accept-any-client)
+[`@mysten/sui` migration guide](/sui/migrations/sui-2.0/sui#transaction-executors-now-accept-any-client)
 for details on the new response format.
 
 Key differences:
@@ -375,11 +383,12 @@ Key differences:
 + { effects: true, events: true }
 ```
 
-## Client Extensions
+## Client extensions
 
 Client extensions work the same way with both clients:
 
 ```typescript
+
 const client = new SuiGrpcClient({
 	baseUrl: 'https://fullnode.mainnet.sui.io:443',
 	network: 'mainnet',
@@ -390,10 +399,10 @@ await client.deepbook.checkManagerBalance(manager, asset);
 await client.suins.getName('0xabc...');
 ```
 
-## See Also
+## See also
 
 - [SuiGrpcClient Documentation](/sui/clients/grpc) - Full gRPC client documentation
 - [SuiGraphQLClient Documentation](/sui/clients/graphql) - GraphQL client documentation
 - [Core API](/sui/clients/core) - Transport-agnostic API methods
 - [gRPC Overview](https://docs.sui.io/concepts/data-access/grpc-overview) - Sui gRPC API
-  documentation
+  documentation