@mysten/docs 0.1.17 → 0.1.19

package/dist/sui/clients/core.md

@@ -1,12 +1,12 @@
 # Core API
 
-> Transport-agnostic Core API shared by all Sui clients
+> Transport-agnostic Core API shared by all Sui clients.
 
 The Core API is the transport-agnostic interface that all Sui clients implement. It provides a
 consistent set of methods for interacting with the Sui blockchain, regardless of whether you're
 using gRPC, GraphQL, or JSON-RPC.
 
-## ClientWithCoreApi
+## `ClientWithCoreApi`
 
 The `ClientWithCoreApi` type represents any client that implements the Core API. Use this type when
 building SDKs or libraries that should work with any transport:
@@ -24,7 +24,7 @@ class MySDK {
 }
 ```
 
-## Object Methods
+## Object methods
 
 Object methods accept an optional `include` parameter to control what data is returned. By default,
 every object comes with `objectId`, `version`, `digest`, `owner`, and `type`. The following fields
@@ -32,13 +32,13 @@ are only populated when requested:
 
 | Option                | Type      | Description                                                               |
 | --------------------- | --------- | ------------------------------------------------------------------------- |
-| `content`             | `boolean` | BCS-encoded Move struct content — pass this to generated BCS type parsers |
+| `content`             | `boolean` | BCS-encoded Move struct content (pass this to generated BCS type parsers) |
 | `previousTransaction` | `boolean` | Digest of the transaction that last mutated this object                   |
 | `json`                | `boolean` | JSON representation of the object's Move struct content                   |
-| `objectBcs`           | `boolean` | Full BCS-encoded object envelope (rarely needed, see [below](#objectbcs)) |
+| `objectBcs`           | `boolean` | Full BCS-encoded object envelope (rarely needed; see [below](#objectbcs)) |
 | `display`             | `boolean` | [Sui Display Standard](https://docs.sui.io/standards/display) metadata    |
 
-### getObject
+### `getObject`
 
 Fetch a single object by ID.
 
@@ -57,7 +57,7 @@ console.log(object.digest);
 console.log(object.type); // e.g., "0x2::coin::Coin<0x2::sui::SUI>"
 ```
 
-### getObjects
+### `getObjects`
 
 Fetch multiple objects in a single request.
 
@@ -76,7 +76,7 @@ for (const obj of objects) {
 }
 ```
 
-### listOwnedObjects
+### `listOwnedObjects`
 
 List objects owned by an address.
 
@@ -121,31 +121,32 @@ const parsed = MyStruct.parse(object.content);
 
 You can also fetch a JSON representation of the object's content with `include: { json: true }`.
 
-> **Warning:** The `json` field structure may vary between API implementations. For example, JSON-RPC returns
+> **Warning:** The `json` field structure might vary between API implementations. For example, JSON-RPC returns
 > UID fields as nested objects (`{ "id": { "id": "0x..." } }`), while gRPC and GraphQL flatten
 > them (`{ "id": "0x..." }`). For consistent data across all clients, use `content` and parse BCS
 > directly.
 
 ### `objectBcs`
 
-The `objectBcs` option returns the full BCS-encoded object envelope — the struct content wrapped in
-metadata (type, `hasPublicTransfer`, version, owner, previous transaction, storage rebate). Most of
-this metadata is already available as fields on the object response, so you typically only need
-`content`. If you do need `objectBcs`, parse it with `bcs.Object` from `@mysten/sui/bcs`:
+The `objectBcs` option returns the full BCS-encoded object envelope, which is the struct content
+wrapped in metadata (type, `hasPublicTransfer`, version, owner, previous transaction, and storage
+rebate). Most of this metadata is already available as fields on the object response, so you
+typically only need `content`. If you do need `objectBcs`, parse it with `bcs.Object` from
+`@mysten/sui/bcs`:
 
 ```typescript
 
 const envelope = bcs.Object.parse(object.objectBcs);
 ```
 
-> **Error:** Do not pass `objectBcs` to a Move struct parser — it contains wrapping metadata that will cause
+> **Error:** Do not pass `objectBcs` to a Move struct parser. It contains wrapping metadata that will cause
 > parsing to fail or produce incorrect results. Use `content` for parsing Move struct fields.
 
 ### `display` include option
 
 The `display` option fetches [Sui Display Standard](https://docs.sui.io/standards/display) metadata
-for an object. Display templates define how an object should be presented in wallets and explorers —
-fields like `name`, `description`, and `image_url`.
+for an object. Display templates define how an object should be presented in wallets and explorers,
+including fields like `name`, `description`, and `image_url`.
 
 ```typescript
 const { object } = await client.core.getObject({
@@ -170,9 +171,9 @@ The `display` field is `null` when the object's type has no registered Display t
 
 `display` works with `getObject`, `getObjects`, and `listOwnedObjects`.
 
-## Coin and Balance Methods
+## Coin and balance methods
 
-### getBalance
+### `getBalance`
 
 Get the balance of a specific coin type for an owner.
 
@@ -186,7 +187,7 @@ console.log(balance.totalBalance); // Total balance as bigint
 console.log(balance.coinObjectCount); // Number of coin objects
 ```
 
-### listBalances
+### `listBalances`
 
 List all coin balances for an owner.
 
@@ -200,7 +201,7 @@ for (const balance of balances) {
 }
 ```
 
-### listCoins
+### `listCoins`
 
 List coin objects of a specific type owned by an address.
 
@@ -216,7 +217,7 @@ for (const coin of result.coins) {
 }
 ```
 
-### getCoinMetadata
+### `getCoinMetadata`
 
 Get metadata for a coin type, including its name, symbol, decimals, and description.
 
@@ -231,9 +232,9 @@ if (coinMetadata) {
 }
 ```
 
-## Dynamic Field Methods
+## Dynamic field methods
 
-### listDynamicFields
+### `listDynamicFields`
 
 List dynamic fields on an object.
 
@@ -248,7 +249,7 @@ for (const field of result.dynamicFields) {
 }
 ```
 
-### getDynamicField
+### `getDynamicField`
 
 Get a specific dynamic field by name.
 
@@ -267,7 +268,7 @@ console.log(dynamicField.value.type);
 console.log(dynamicField.value.bcs); // BCS-encoded value
 ```
 
-### getDynamicObjectField
+### `getDynamicObjectField`
 
 Get a dynamic object field, returning the referenced object. Supports the same
 [object include options](#object-methods) as `getObject`.
@@ -283,20 +284,20 @@ const { object } = await client.core.getDynamicObjectField({
 });
 ```
 
-## Transaction Methods
+## Transaction methods
 
 Transaction methods accept an optional `include` parameter to control what data is returned. By
 default, every transaction result includes `digest`, `signatures`, `epoch`, and `status`. The
 following fields are only populated when requested:
 
-| Option           | Type      | Description                                                          |
-| ---------------- | --------- | -------------------------------------------------------------------- |
-| `effects`        | `boolean` | Parsed transaction effects (gas used, changed objects, status, etc.) |
-| `events`         | `boolean` | Events emitted during execution                                      |
-| `transaction`    | `boolean` | Parsed transaction data (sender, gas config, inputs, commands)       |
-| `balanceChanges` | `boolean` | Balance changes caused by the transaction                            |
-| `objectTypes`    | `boolean` | Map of object IDs to their types for all changed objects             |
-| `bcs`            | `boolean` | Raw BCS-encoded transaction bytes                                    |
+| Option           | Type      | Description                                                        |
+| ---------------- | --------- | ------------------------------------------------------------------ |
+| `effects`        | `boolean` | Parsed transaction effects (gas used, changed objects, and status) |
+| `events`         | `boolean` | Events emitted during execution                                    |
+| `transaction`    | `boolean` | Parsed transaction data (sender, gas config, inputs, commands)     |
+| `balanceChanges` | `boolean` | Balance changes caused by the transaction                          |
+| `objectTypes`    | `boolean` | Map of object IDs to their types for all changed objects           |
+| `bcs`            | `boolean` | Raw BCS-encoded transaction bytes                                  |
 
 `simulateTransaction` also supports:
 
@@ -304,7 +305,7 @@ following fields are only populated when requested:
 | ---------------- | --------- | ------------------------------------------------------ |
 | `commandResults` | `boolean` | Return values and mutated references from each command |
 
-### executeTransaction
+### `executeTransaction`
 
 Execute a signed transaction.
 
@@ -326,7 +327,7 @@ if (result.Transaction) {
 }
 ```
 
-### simulateTransaction
+### `simulateTransaction`
 
 Simulate a transaction without executing it.
 
@@ -345,7 +346,7 @@ console.log(result.effects);
 console.log(result.balanceChanges);
 ```
 
-#### Disabling Checks
+#### Disabling checks
 
 By default, `simulateTransaction` runs with full transaction validation. For example when inspecting
 non-public or non-entry Move functions set `checksEnabled: false`:
@@ -360,7 +361,7 @@ const result = await client.core.simulateTransaction({
 });
 ```
 
-### signAndExecuteTransaction
+### `signAndExecuteTransaction`
 
 Sign and execute a transaction in one step.
 
@@ -383,7 +384,7 @@ if (result.FailedTransaction) {
 console.log('Digest:', result.Transaction.digest);
 ```
 
-### getTransaction
+### `getTransaction`
 
 Fetch a transaction by digest.
 
@@ -414,7 +415,7 @@ const result = await client.core.getTransaction({
 console.log(result.Transaction?.bcs); // Uint8Array
 ```
 
-### waitForTransaction
+### `waitForTransaction`
 
 Wait for a transaction to be available.
 
@@ -437,9 +438,9 @@ const finalResult = await client.core.waitForTransaction({
 });
 ```
 
-## System Methods
+## System methods
 
-### getReferenceGasPrice
+### `getReferenceGasPrice`
 
 Get the current reference gas price.
 
@@ -448,7 +449,7 @@ const { referenceGasPrice } = await client.core.getReferenceGasPrice();
 console.log(referenceGasPrice); // bigint
 ```
 
-### getCurrentSystemState
+### `getCurrentSystemState`
 
 Get the current system state including epoch information.
 
@@ -458,7 +459,7 @@ console.log(systemState.epoch);
 console.log(systemState.systemStateVersion);
 ```
 
-### getChainIdentifier
+### `getChainIdentifier`
 
 Get the chain identifier for the network.
 
@@ -467,9 +468,9 @@ const { chainIdentifier } = await client.core.getChainIdentifier();
 console.log(chainIdentifier); // e.g., "4c78adac"
 ```
 
-## Move Methods
+## Move methods
 
-### getMoveFunction
+### `getMoveFunction`
 
 Get information about a Move function.
 
@@ -485,9 +486,9 @@ console.log(fn.parameters);
 console.log(fn.typeParameters);
 ```
 
-## Name Service Methods
+## Name service methods
 
-### defaultNameServiceName
+### `defaultNameServiceName`
 
 Resolve an address to its default SuiNS name.
 
@@ -499,11 +500,11 @@ const { name } = await client.core.defaultNameServiceName({
 console.log(name); // e.g., "example.sui"
 ```
 
-## MVR Methods
+## MVR methods
 
 The client also exposes MVR (Move Registry) methods through `client.core.mvr`:
 
-### resolveType
+### `resolveType`
 
 Resolve a type name (including `.move` names) to a fully qualified type.
 
@@ -515,9 +516,9 @@ const { type } = await client.core.mvr.resolveType({
 console.log(type); // "0x2::coin::Coin<0x2::sui::SUI>"
 ```
 
-## Error Handling
+## Error handling
 
-Methods that fetch objects may return errors in the result:
+Methods that fetch objects might return errors in the result:
 
 ```typescript
 const { objects } = await client.core.getObjects({
@@ -549,7 +550,7 @@ if (result.Transaction) {
 }
 ```
 
-## SuiClientTypes Namespace
+## `SuiClientTypes` Namespace
 
 The `SuiClientTypes` namespace contains all type definitions for the Core API. Import it when you
 need to type function parameters, return values, or variables:
@@ -577,7 +578,7 @@ const options: SuiClientTypes.GetObjectOptions<{ content: true }> = {
 };
 ```
 
-### Common Types
+### Common types
 
 | Type                   | Description                                 |
 | ---------------------- | ------------------------------------------- |
@@ -595,7 +596,7 @@ const options: SuiClientTypes.GetObjectOptions<{ content: true }> = {
 | `FunctionResponse`     | Move function metadata                      |
 | `Network`              | Network identifier type                     |
 
-### Include Options Types
+### Include options types
 
 | Type                         | Description                             |
 | ---------------------------- | --------------------------------------- |
@@ -603,7 +604,7 @@ const options: SuiClientTypes.GetObjectOptions<{ content: true }> = {
 | `TransactionInclude`         | Options for transaction data inclusion  |
 | `SimulateTransactionInclude` | Extended options for simulation results |
 
-### Method Options Types
+### Method options types
 
 | Type                               | Description                             |
 | ---------------------------------- | --------------------------------------- |

package/dist/sui/clients/graphql.md

@@ -1,6 +1,6 @@
 # SuiGraphQLClient
 
-> Connect to Sui via GraphQL with SuiGraphQLClient
+> Connect to Sui through GraphQL with SuiGraphQLClient.
 
 The `SuiGraphQLClient` enables type-safe GraphQL queries against the Sui GraphQL API.
 
@@ -50,7 +50,7 @@ async function getChainIdentifier() {
 
 ## Type-safety for GraphQL queries
 
-You may have noticed the example above does not include any type definitions for the query. The
+You might have noticed the example above does not include any type definitions for the query. The
 `graphql` function used in the example is powered by [`gql.tada`](https://gql-tada.0no.co/) and will
 automatically provide the required type information to ensure that your queries are properly typed
 when executed through `SuiGraphQLClient`.
@@ -82,7 +82,7 @@ async function getDefaultSuinsName(address: string) {
 ## Using typed GraphQL queries with other GraphQL clients
 
 The `graphql` function returns document nodes that implement the
-[TypedDocumentNode](https://github.com/dotansimha/graphql-typed-document-node) standard, and will
+[`TypedDocumentNode`](https://github.com/dotansimha/graphql-typed-document-node) standard, and will
 work with the majority of popular GraphQL clients to provide queries that are automatically typed.
 
 ```typescript

package/dist/sui/clients/grpc.md

@@ -1,6 +1,6 @@
 # SuiGrpcClient
 
-> Connect to Sui via gRPC with SuiGrpcClient
+> Connect to Sui through gRPC with SuiGrpcClient.
 
 The `SuiGrpcClient` provides access to the Full Node gRPC API.
 
@@ -31,8 +31,8 @@ const grpcClient = new SuiGrpcClient({
 ## Transport options
 
 By default, `SuiGrpcClient` uses `GrpcWebFetchTransport` from
-[protobuf-ts](https://github.com/timostamm/protobuf-ts), which works in browsers and Node.js via the
-Fetch API. You can also provide a custom transport for advanced use cases.
+[protobuf-ts](https://github.com/timostamm/protobuf-ts), which works in browsers and Node.js through
+the Fetch API. You can also provide a custom transport for advanced use cases.
 
 The `GrpcWebFetchTransport` class, `GrpcWebOptions` type, and `RpcTransport` type are all
 re-exported from `@mysten/sui/grpc` for convenience.
@@ -58,7 +58,7 @@ const grpcClient = new SuiGrpcClient({
 
 ### Native gRPC transport
 
-For server-side applications (Node.js, Bun, etc.), you can use the native gRPC transport with
+For server-side applications (Node.js, Bun, and others), you can use the native gRPC transport with
 `@protobuf-ts/grpc-transport` and `@grpc/grpc-js`. This uses HTTP/2 with the native gRPC protocol
 rather than the gRPC-web translation layer.
 
@@ -123,7 +123,7 @@ await grpcClient.getCoins({
 
 To query additional data not available in the core API, you can use the service clients directly:
 
-### Transaction Execution Service
+### Transaction execution service
 
 ```typescript
 const { response } = await grpcClient.transactionExecutionService.executeTransaction({
@@ -145,7 +145,7 @@ if (!response.finality?.effects?.status?.success) {
 }
 ```
 
-### Ledger Service
+### Ledger service
 
 ```typescript
 // Get transaction by digest
@@ -157,7 +157,7 @@ const { response } = await grpcClient.ledgerService.getTransaction({
 const { response: epochInfo } = await grpcClient.ledgerService.getEpoch({});
 ```
 
-### State Service
+### State service
 
 ```typescript
 // List owned objects
@@ -172,7 +172,7 @@ const { response: fields } = await grpcClient.stateService.listDynamicFields({
 });
 ```
 
-### Move Package Service
+### Move package service
 
 ```typescript
 // Get function information
@@ -183,7 +183,7 @@ const { response } = await grpcClient.movePackageService.getFunction({
 });
 ```
 
-### Name Service
+### Name service
 
 ```typescript
 // Reverse lookup address to get name
@@ -192,7 +192,7 @@ const { response } = await grpcClient.nameService.reverseLookupName({
 });
 ```
 
-### Signature Verification Service
+### Signature verification service
 
 ```typescript
 // Verify a signature

package/dist/sui/clients/index.md

@@ -1,30 +1,30 @@
 # Sui Clients
 
-> Choose and configure gRPC, GraphQL, or JSON-RPC clients
+> Choose and configure gRPC, GraphQL, or JSON-RPC clients for the Sui network.
 
 The Sui TypeScript SDK provides multiple client implementations for interacting with the Sui
 network. Each client connects to a different API but provides two levels of access:
 
-- **Native API** - Full access to everything the underlying API offers
-- **[Core API](/sui/clients/core)** - A consistent interface across all clients for common
-  operations
+- Native API: Full access to everything the underlying API offers
+- [Core API](/sui/clients/core): A consistent interface across all clients for common operations
 
-## Available Clients
+## Available clients
 
-| Client                                                 | API                                                                |
-| ------------------------------------------------------ | ------------------------------------------------------------------ |
-| [SuiGrpcClient](/sui/clients/grpc) (recommended)       | [Full Node gRPC](https://docs.sui.io/references/fullnode-protocol) |
-| [SuiGraphQLClient](/sui/clients/graphql)               | [GraphQL](https://docs.sui.io/references/sui-graphql)              |
-| [SuiJsonRpcClient](/sui/clients/json-rpc) (deprecated) | [JSON-RPC (deprecated)](https://docs.sui.io/sui-api-ref)           |
+| Client                                                   | API                                                                |
+| -------------------------------------------------------- | ------------------------------------------------------------------ |
+| [`SuiGrpcClient`](/sui/clients/grpc) (recommended)       | [Full Node gRPC](https://docs.sui.io/references/fullnode-protocol) |
+| [`SuiGraphQLClient`](/sui/clients/graphql)               | [GraphQL](https://docs.sui.io/references/sui-graphql)              |
+| [`SuiJsonRpcClient`](/sui/clients/json-rpc) (deprecated) | [JSON-RPC (deprecated)](https://docs.sui.io/sui-api-ref)           |
 
 All clients are compatible with Mysten SDKs like `@mysten/walrus`, `@mysten/seal` and
 `@mysten/suins`.
 
 For most application gRPC is a good default. The JSON RPC API has been deprecated and will be
 decommissioned soon. The GraphQL can be used for more advanced query patterns that can not be
-supported directly on full nodes (eg, querying for transactions or events with various filters).
+supported directly on full nodes (for example, querying for transactions or events with various
+filters).
 
-## Quick Start
+## Quick start
 
 ```typescript
 
@@ -40,7 +40,7 @@ const { response } = await client.ledgerService.getTransaction({ digest: '0x...'
 const { object } = await client.core.getObject({ objectId: '0x...' });
 ```
 
-## Native vs Core API
+## Native vs core API
 
 ### Native API
 
@@ -80,7 +80,7 @@ await client.core.executeTransaction({ transaction, signatures });
 The Core API is essential for [building SDKs](/sui/sdk-building) that work with any client the user
 chooses.
 
-## Client Extensions
+## Client extensions
 
 All clients support extensions through the `$extend` method, enabling SDKs like
 [@mysten/walrus](https://www.npmjs.com/package/@mysten/walrus) to add functionality:

package/dist/sui/clients/json-rpc.md

@@ -1,9 +1,9 @@
 # SuiJsonRpcClient
 
-> Connect to Sui via JSON-RPC with SuiJsonRpcClient
+> Connect to Sui through JSON-RPC with SuiJsonRpcClient.
 
 > **Warning:** The Sui JSON-RPC API has been deprecated. We recommend migration to
-> [SuiGrpcClient](/sui/clients/grpc) or [SuiGraphQLClient](/sui/clients/graphql) as soon as
+> [`SuiGrpcClient`](/sui/clients/grpc) or [`SuiGraphQLClient`](/sui/clients/graphql) as soon as
 > possible.
 
 The `SuiJsonRpcClient` connects to a Sui network's JSON-RPC server. It implements the
@@ -100,9 +100,9 @@ const client = new SuiJsonRpcClient({
 `SuiJsonRpcClient` exposes a number of RPC methods that return paginated results. These methods
 return a result object with 3 fields:
 
-- data: The list of results for the current page
-- nextCursor: a cursor pointing to the next page of results
-- hasNextPage: a boolean indicating whether there are more pages of results
+- `data`: The list of results for the current page
+- `nextCursor`: A cursor pointing to the next page of results
+- `hasNextPage`: A boolean indicating whether there are more pages of results
 
 Some APIs also accept an `order` option that can be set to either `ascending` or `descending` to
 change the order in which the results are returned.
@@ -150,10 +150,10 @@ const result = await client.executeTransactionBlock({
 
 #### Arguments
 
-- `transactionBlock` - either a Transaction or BCS serialized transaction data bytes as a Uint8Array
+- `transactionBlock`: either a Transaction or BCS serialized transaction data bytes as a Uint8Array
   or as a base-64 encoded string.
-- `signature` - A signature, or list of signatures committed to the intent message of the
-  transaction data, as a base-64 encoded string.
+- `signature`: A signature, or list of signatures committed to the intent message of the transaction
+  data, as a base-64 encoded string.
 - `options`:
   - `showBalanceChanges`: Whether to show balance_changes. Default to be False
   - `showEffects`: Whether to show transaction effects. Default to be False
@@ -185,9 +185,9 @@ if (result.$kind === 'FailedTransaction') {
 
 #### Arguments
 
-- `transaction` - BCS serialized transaction data bytes as a Uint8Array or as a base-64 encoded
+- `transaction`: BCS serialized transaction data bytes as a Uint8Array or as a base-64 encoded
   string.
-- `signer` - A `Keypair` instance to sign the transaction
+- `signer`: A `Keypair` instance to sign the transaction
 - `options`:
   - `showBalanceChanges`: Whether to show balance_changes. Default to be False
   - `showEffects`: Whether to show transaction effects. Default to be False
@@ -199,8 +199,8 @@ if (result.$kind === 'FailedTransaction') {
 ### `waitForTransaction`
 
 Wait for a transaction result to be available over the API. This can be used in conjunction with
-`signAndExecuteTransaction` to wait for the transaction to be available via the API. This currently
-polls the `getTransactionBlock` API to check for the transaction.
+`signAndExecuteTransaction` to wait for the transaction to be available through the API. This
+currently polls the `getTransactionBlock` API to check for the transaction.
 
 ```tsx
 const tx = new Transaction();
@@ -225,10 +225,10 @@ const transaction = await client.waitForTransaction({
 
 #### Arguments
 
-- `digest` - the digest of the queried transaction
-- `signal` - An optional abort signal that can be used to cancel the request
-- `timeout` - The amount of time to wait for a transaction. Defaults to one minute.
-- `pollInterval` - The amount of time to wait between checks for the transaction. Defaults to 2
+- `digest`: the digest of the queried transaction
+- `signal`: An optional abort signal that can be used to cancel the request
+- `timeout`: The amount of time to wait for a transaction. Defaults to one minute.
+- `pollInterval`: The amount of time to wait between checks for the transaction. Defaults to 2
   seconds.
 - `options`:
   - `showBalanceChanges`: Whether to show balance_changes. Default to be False

package/dist/sui/cryptography/keypairs.md

@@ -1,6 +1,6 @@
 # Key pairs
 
-> Create and manage Ed25519, Secp256k1, and Secp256r1 keypairs
+> Create and manage Ed25519, Secp256k1, and Secp256r1 keypairs for Sui transaction signing.
 
 The Sui TypeScript SDK provides `Keypair` classes that handle logic for signing and verification
 using the cryptographic key pairs associated with a Sui address.
@@ -134,10 +134,10 @@ await verifyTransactionSignature(bytes, signature, {
 ## Verifying zkLogin signatures
 
 ZkLogin signatures can't be verified purely on the client. When verifying a zkLogin signature, the
-SDK uses the GraphQL API to verify the signature. This will work for mainnet signatures without any
+SDK uses the GraphQL API to verify the signature. This works for Mainnet signatures without any
 additional configuration.
 
-For testnet signatures, you will need to provide a testnet GraphQL Client:
+For Testnet signatures, you need to provide a Testnet GraphQL Client:
 
 ```typescript
 
@@ -148,9 +148,9 @@ const publicKey = await verifyPersonalMessageSignature(message, zkSignature, {
 });
 ```
 
-For some zklogin accounts, there are 2 valid addresses for a given set of inputs. This means you may
-run into issues if you try to compare the address returned by `publicKey.toSuiAddress()` directly
-with an expected address.
+For some zklogin accounts, there are two valid addresses for a given set of inputs. This means you
+might run into issues if you try to compare the address returned by `publicKey.toSuiAddress()`
+directly with an expected address.
 
 Instead, you can either pass in the expected address during verification, or use the
 `publicKey.verifyAddress(address)` method:

package/dist/sui/cryptography/multisig.md

@@ -1,6 +1,6 @@
 # Multi-Signature Transactions
 
-> Create multi-signature transactions with multiple signers
+> Create multi-signature transactions with multiple signers on Sui.
 
 The Sui TypeScript SDK provides a `MultiSigPublicKey` class to support
 [Multi-Signature](https://docs.sui.io/concepts/cryptography/transaction-auth/multisig) (MultiSig)
@@ -69,7 +69,7 @@ const isValid = await multiSigPublicKey.verifyPersonalMessage(message, combinedS
 
 The `MultiSigSigner` class allows you to create a Signer that can be used to sign personal messages
 and Transactions like any other keypair or signer class. This is often easier than manually
-combining signatures, since many methods accept Signers and handle signing directly.
+combining signatures, because many methods accept Signers and handle signing directly.
 
 A `MultiSigSigner` is created by providing the underlying Signers to the `getSigner` method on the
 `MultiSigPublicKey`. You can provide a subset of the Signers that make up the public key, so long as
@@ -147,7 +147,7 @@ const zkLoginSig = getZkLoginSignature({
 const multisig = multiSigPublicKey.combinePartialSignatures([zkLoginSig]);
 ```
 
-### Benefits and Design for zkLogin in Multisig
+### Benefits and design for zkLogin in multisig
 
 Because zkLogin assumes the application client ID and its issuer (such as Google) liveliness, using
 zkLogin with multisig provides improved recoverability to a zkLogin account. In the previous example
@@ -168,7 +168,7 @@ In this case, Charlie can always use their Google account for transactions out o
 address for the threshold. At the same time, Charlie still has access to his account by combining
 partial signatures from Alice and Bob.
 
-## Multisig with Passkey
+## Multisig with passkey
 
 You can use a `PasskeyKeypair` (a `Keypair`) and `PasskeyPublicKey` (a `PublicKey`) as components in
 a Multisig setup. Once initialized, they support both Multisig address derivation and transaction