@mysten/sui 2.16.0 → 2.16.2

package/docs/bcs.md

@@ -1,6 +1,6 @@
 # BCS
 
-> Binary Canonical Serialization for encoding Sui Move types
+> Binary Canonical Serialization for encoding Sui Move types.
 
 The `@mysten/sui/bcs` package extends `@mysten/bcs` with Sui specific scheme definitions.
 
@@ -41,15 +41,16 @@ the following pre-defined schemes:
 - `TransactionExpiration`
 - `TransactionKind`
 - `TypeTag`
-- `Object` - Complete object with data, owner, previousTransaction, and storageRebate
-- `TransactionEffects` - Transaction execution effects (supports both V1 and V2)
-- `TransactionEffectsV1` - Legacy transaction effects format
-- `TransactionEffectsV2` - Current transaction effects format with detailed object changes
+- `Object`: Complete object with data, owner, previousTransaction, and storageRebate
+- `TransactionEffects`: Transaction execution effects (supports both V1 and V2)
+- `TransactionEffectsV1`: Legacy transaction effects format
+- `TransactionEffectsV2`: Current transaction effects format with detailed object changes
 
 All the upper-cased values are `BcsType` instances, and can be used directly to parse and serialize
 data.
 
 ```typescript
+
 bcs.U8.serialize(1);
 bcs.Address.serialize('0x1');
 bcs.TypeTag.serialize({
@@ -59,13 +60,14 @@ bcs.TypeTag.serialize({
 });
 ```
 
-## Working with Objects
+## Working with objects
 
-To parse on-chain objects, fetch them with `include: { content: true }` and pass `object.content` to
+To parse onchain objects, fetch them with `include: { content: true }` and pass `object.content` to
 a generated BCS type or a manual struct definition. The `content` field contains only the inner Move
 struct bytes:
 
 ```typescript
+
 const { object } = await client.core.getObject({
 	objectId: '0x123...',
 	include: { content: true },
@@ -74,9 +76,9 @@ const { object } = await client.core.getObject({
 const parsed = MyStruct.parse(object.content);
 ```
 
-### `bcs.Object` — Full object envelope
+### `bcs.Object`: Full object envelope
 
-The `bcs.Object` schema represents the complete on-chain object, including metadata (type, owner,
+The `bcs.Object` schema represents the complete onchain object, including metadata (type, owner,
 version, previous transaction, storage rebate) wrapping the inner struct bytes. This is what the
 `objectBcs` include option returns. Most of this metadata is already available as fields on the
 object response, so you typically only need `content`.
@@ -104,15 +106,16 @@ const serialized = bcs.Object.serialize({
 });
 ```
 
-> **Warning:** Do not pass `objectBcs` bytes to a Move struct parser — it contains wrapping metadata
-> that will cause parsing to fail. Use `content` for parsing Move struct fields. See the
-> [Core API docs](/sui/clients/core#objectbcs) for details.
+> **Warning:** Do not pass `objectBcs` bytes to a Move struct parser. It contains wrapping metadata that will
+> cause parsing to fail. Use `content` for parsing Move struct fields. See the [Core API
+> docs](/sui/clients/core#objectbcs) for details.
 
-## Working with Transaction Effects
+## Working with transaction effects
 
 The `bcs.TransactionEffects` schema can be used to parse transaction effects:
 
 ```typescript
+
 // Parse transaction effects
 const effects = bcs.TransactionEffects.parse(effectsBytes);
 
@@ -128,4 +131,4 @@ for (const [objectId, change] of effects.V2.changedObjects) {
 	console.log('Object:', objectId);
 	console.log('Output state:', change.outputState.$kind);
 }
-```
+```

package/docs/clients/core.md

@@ -1,17 +1,18 @@
 # 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:
 
 ```typescript
+
 // Your SDK works with any client
 class MySDK {
 	constructor(private client: ClientWithCoreApi) {}
@@ -23,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
@@ -31,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.
 
@@ -56,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.
 
@@ -75,7 +76,7 @@ for (const obj of objects) {
 }
 ```
 
-### listOwnedObjects
+### `listOwnedObjects`
 
 List objects owned by an address.
 
@@ -107,6 +108,7 @@ Use `include: { content: true }` to get the BCS-encoded Move struct bytes, then
 generated types (from `@mysten/codegen`) or manual BCS definitions:
 
 ```typescript
+
 const { object } = await client.core.getObject({
 	objectId: '0x123...',
 	include: { content: true },
@@ -119,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 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.
+> **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 parsing to fail or produce incorrect results. Use `content` for parsing Move struct
-> fields.
+> **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({
@@ -168,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.
 
@@ -184,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.
 
@@ -198,7 +201,7 @@ for (const balance of balances) {
 }
 ```
 
-### listCoins
+### `listCoins`
 
 List coin objects of a specific type owned by an address.
 
@@ -214,7 +217,7 @@ for (const coin of result.coins) {
 }
 ```
 
-### getCoinMetadata
+### `getCoinMetadata`
 
 Get metadata for a coin type, including its name, symbol, decimals, and description.
 
@@ -229,9 +232,9 @@ if (coinMetadata) {
 }
 ```
 
-## Dynamic Field Methods
+## Dynamic field methods
 
-### listDynamicFields
+### `listDynamicFields`
 
 List dynamic fields on an object.
 
@@ -246,11 +249,12 @@ for (const field of result.dynamicFields) {
 }
 ```
 
-### getDynamicField
+### `getDynamicField`
 
 Get a specific dynamic field by name.
 
 ```typescript
+
 const { dynamicField } = await client.core.getDynamicField({
 	parentId: '0x123...',
 	name: {
@@ -264,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`.
@@ -280,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:
 
@@ -301,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.
 
@@ -323,7 +327,7 @@ if (result.Transaction) {
 }
 ```
 
-### simulateTransaction
+### `simulateTransaction`
 
 Simulate a transaction without executing it.
 
@@ -342,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`:
@@ -357,11 +361,12 @@ const result = await client.core.simulateTransaction({
 });
 ```
 
-### signAndExecuteTransaction
+### `signAndExecuteTransaction`
 
 Sign and execute a transaction in one step.
 
 ```typescript
+
 const tx = new Transaction();
 tx.transferObjects([tx.object('0x123...')], '0xrecipient...');
 
@@ -379,7 +384,7 @@ if (result.FailedTransaction) {
 console.log('Digest:', result.Transaction.digest);
 ```
 
-### getTransaction
+### `getTransaction`
 
 Fetch a transaction by digest.
 
@@ -410,7 +415,7 @@ const result = await client.core.getTransaction({
 console.log(result.Transaction?.bcs); // Uint8Array
 ```
 
-### waitForTransaction
+### `waitForTransaction`
 
 Wait for a transaction to be available.
 
@@ -433,9 +438,9 @@ const finalResult = await client.core.waitForTransaction({
 });
 ```
 
-## System Methods
+## System methods
 
-### getReferenceGasPrice
+### `getReferenceGasPrice`
 
 Get the current reference gas price.
 
@@ -444,7 +449,7 @@ const { referenceGasPrice } = await client.core.getReferenceGasPrice();
 console.log(referenceGasPrice); // bigint
 ```
 
-### getCurrentSystemState
+### `getCurrentSystemState`
 
 Get the current system state including epoch information.
 
@@ -454,7 +459,7 @@ console.log(systemState.epoch);
 console.log(systemState.systemStateVersion);
 ```
 
-### getChainIdentifier
+### `getChainIdentifier`
 
 Get the chain identifier for the network.
 
@@ -463,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.
 
@@ -481,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.
 
@@ -495,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.
 
@@ -511,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({
@@ -545,12 +550,13 @@ 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:
 
 ```typescript
+
 // Type function parameters
 function processObject(obj: SuiClientTypes.Object<{ content: true }>) {
 	console.log(obj.objectId, obj.content);
@@ -572,7 +578,7 @@ const options: SuiClientTypes.GetObjectOptions<{ content: true }> = {
 };
 ```
 
-### Common Types
+### Common types
 
 | Type                   | Description                                 |
 | ---------------------- | ------------------------------------------- |
@@ -590,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                             |
 | ---------------------------- | --------------------------------------- |
@@ -598,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                             |
 | ---------------------------------- | --------------------------------------- |
@@ -613,4 +619,4 @@ const options: SuiClientTypes.GetObjectOptions<{ content: true }> = {
 | `SimulateTransactionOptions`       | Options for `simulateTransaction`       |
 | `SignAndExecuteTransactionOptions` | Options for `signAndExecuteTransaction` |
 | `GetTransactionOptions`            | Options for `getTransaction`            |
-| `WaitForTransactionOptions`        | Options for `waitForTransaction`        |
+| `WaitForTransactionOptions`        | Options for `waitForTransaction`        |

package/docs/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.
 
@@ -10,6 +10,7 @@ For more details on the Sui GraphQL API, see the
 The `SuiGraphQLClient` implements all the the [Core API](/sui/clients/core) methods:
 
 ```typescript
+
 const client = new SuiGraphQLClient({
 	url: 'https://sui-mainnet.mystenlabs.com/graphql',
 	network: 'mainnet',
@@ -26,6 +27,7 @@ queries.
 We'll start by creating our client, and executing a very basic query:
 
 ```typescript
+
 const gqlClient = new SuiGraphQLClient({
 	url: 'https://graphql.testnet.sui.io/graphql',
 	network: 'testnet',
@@ -48,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`.
@@ -80,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
@@ -96,4 +98,4 @@ function ChainIdentifier() {
 
 	return <div>{data?.chainIdentifier}</div>;
 }
-```
+```

package/docs/clients/grpc.md

@@ -1,17 +1,18 @@
 # 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.
 
 For more complete details on what is available through this API see the
-[gRPC API docs](https://docs.sui.io/concepts/data-access/grpc-overview).
+[gRPC API docs](https://docs.sui.io/develop/accessing-data/grpc/what-is-grpc).
 
 ## Creating a gRPC client
 
 To get started, create a `SuiGrpcClient` instance by specifying a network and base URL:
 
 ```typescript
+
 const grpcClient = new SuiGrpcClient({
 	network: 'testnet',
 	baseUrl: 'https://fullnode.testnet.sui.io:443',
@@ -30,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.
@@ -42,6 +43,7 @@ The default transport uses the gRPC-web protocol over HTTP/1.1 or HTTP/2. You ca
 passing `GrpcWebFetchTransport` options directly:
 
 ```typescript
+
 const transport = new GrpcWebFetchTransport({
 	baseUrl: 'https://your-custom-grpc-endpoint.com',
 	format: 'binary', // default is 'text' (base64-encoded)
@@ -56,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.
 
@@ -69,6 +71,7 @@ npm install @protobuf-ts/grpc-transport @grpc/grpc-js
 Then create the client with a `GrpcTransport`:
 
 ```typescript
+
 const transport = new GrpcTransport({
 	host: 'fullnode.testnet.sui.io:443',
 	channelCredentials: ChannelCredentials.createSsl(),
@@ -83,6 +86,7 @@ const grpcClient = new SuiGrpcClient({
 For local development without TLS:
 
 ```typescript
+
 const transport = new GrpcTransport({
 	host: '127.0.0.1:9000',
 	channelCredentials: ChannelCredentials.createInsecure(),
@@ -99,13 +103,14 @@ const grpcClient = new SuiGrpcClient({
 The `SuiGrpcClient` exposes several service clients for lower-level access to the gRPC API. These
 service clients are generated using [protobuf-ts](https://github.com/timostamm/protobuf-ts), which
 provides type-safe gRPC clients for TypeScript. For more details on how to use gRPC with Sui, see
-the [gRPC overview](https://docs.sui.io/concepts/data-access/grpc-overview).
+the [gRPC overview](https://docs.sui.io/develop/accessing-data/grpc/what-is-grpc).
 
 ### With the core API
 
 The gRPC client implements all the [`core`](./core) API methods:
 
 ```typescript
+
 const grpcClient = new SuiGrpcClient({
 	network: 'testnet',
 	baseUrl: 'https://fullnode.testnet.sui.io:443',
@@ -118,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({
@@ -140,7 +145,7 @@ if (!response.finality?.effects?.status?.success) {
 }
 ```
 
-### Ledger Service
+### Ledger service
 
 ```typescript
 // Get transaction by digest
@@ -152,7 +157,7 @@ const { response } = await grpcClient.ledgerService.getTransaction({
 const { response: epochInfo } = await grpcClient.ledgerService.getEpoch({});
 ```
 
-### State Service
+### State service
 
 ```typescript
 // List owned objects
@@ -167,7 +172,7 @@ const { response: fields } = await grpcClient.stateService.listDynamicFields({
 });
 ```
 
-### Move Package Service
+### Move package service
 
 ```typescript
 // Get function information
@@ -178,7 +183,7 @@ const { response } = await grpcClient.movePackageService.getFunction({
 });
 ```
 
-### Name Service
+### Name service
 
 ```typescript
 // Reverse lookup address to get name
@@ -187,7 +192,7 @@ const { response } = await grpcClient.nameService.reverseLookupName({
 });
 ```
 
-### Signature Verification Service
+### Signature verification service
 
 ```typescript
 // Verify a signature
@@ -202,4 +207,4 @@ const { response } = await grpcClient.signatureVerificationService.verifySignatu
 	},
 	jwks: [],
 });
-```
+```