Skip to content

Commit 95ad436

Browse files
committed
chore: grammer and links
1 parent eb302b1 commit 95ad436

File tree

3 files changed

+14
-14
lines changed

3 files changed

+14
-14
lines changed

docs/src/content/docs/integrations/typescript/guided-tutorial/cosmos-call.mdx

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -3,7 +3,7 @@ title: Cross Chain Contract Calls
33
description: Example call on Babylon to Ethereum contract.
44
---
55

6-
This guide walk's you through writing our example ["Call"](/integrations/typescript/examples/cosmos/call/). The goal of this guide is to show you how to conduct a cross chain contract call using [USC03 - ZKGM](/ucs/03/). In this case we will be calling a contract on Ethereum from Babylon.
6+
This guide walks you through writing our example ["Call"](/integrations/typescript/examples/cosmos/call/). The goal of this guide is to show you how to conduct a cross chain contract call using [ucs03-zkgm](/ucs/03/). In this case we will be calling a contract on Ethereum from Babylon.
77

88
Relevant imports will be included with each step. Outside of libraries provided by Union, this guide uses [Effect](https://effect.website/).
99

@@ -50,14 +50,14 @@ const program = Effect.gen(function*() {
5050
```
5151

5252
:::note
53-
The ID's provided here are Universal Chain ID's as defined by [UCS04](/ucs/04).
53+
The IDs provided here are Universal Chain IDs as defined by [ucs04](/ucs/04).
5454
:::
5555

5656
### 3. Call
5757

5858
To create a `Call`, we supply the `sender`, `contractAddress`, and `contractCalldata`.
5959

60-
More information about `Call` and its fields can be found in the [UCS03 - 0x01 Call Docs](/ucs/03/#0x01---call).
60+
More information about `Call` and its fields can be found in the [Call](/ucs/03/#0x01---call) docs.
6161

6262
```ts
6363
import { Call, Ucs05, ZkgmClientRequest, ZkgmClientResponse } from "@unionlabs/sdk"
@@ -103,7 +103,7 @@ const program = Effect.gen(function*() {
103103
```
104104

105105
:::note
106-
UCS03 addresses can be found on the [Deployments page](/protocol/deployments/)
106+
ucs03 addresses can be found on the [Deployments page](/protocol/deployments/)
107107
:::
108108

109109
### 5. zkgm Execution and Response

docs/src/content/docs/integrations/typescript/guided-tutorial/cosmos-union-sepolia.mdx

Lines changed: 5 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -3,7 +3,7 @@ title: Send Funds Union → Sepolia
33
description: Example transfer from Union to Sepolia.
44
---
55

6-
This guide walk's you through writing our example ["Send Funds Union -> Sepolia"](/integrations/typescript/examples/cosmos/send-funds-union-to-sepolia/). The goal of this guide it to show you how to create a token order and submit it to the [UCS03 - ZKGM](/ucs/04) interface.
6+
This guide walks you through writing our example ["Send Funds Union -> Sepolia"](/integrations/typescript/examples/cosmos/send-funds-union-to-sepolia/). The goal of this guide it to show you how to create a token order and submit it to the [ucs03-zkgm](/ucs/03) interface.
77

88
Relevant imports will be included with each step. Outside of libraries provided by Union, this guide uses [Effect](https://effect.website/).
99

@@ -41,7 +41,7 @@ const program = Effect.gen(function*() {
4141
```
4242

4343
:::note
44-
The ID's provided here are Universal Chain ID's as defined by [UCS04](/ucs/04).
44+
The ID's provided here are Universal Chain ID's as defined by [ucs04](/ucs/04).
4545
:::
4646

4747
### 3. Token Order
@@ -50,7 +50,7 @@ Now you can define the token order that will be responsible for the transfer. Th
5050

5151
To construct the token order, you will need the token contract/denom on both the source chain (`baseToken`) and the destination chain (`quoteToken`). In this case, we are using the relevant denom and contract address for U.
5252

53-
We also need to determine the `Kind` for the `TokenOrder`. In this case, we use `solve`. Though kind can be `initialize`, `escrow`, `unescrow`, or `solve`. To understand which kind of token order to use, refer to the [UCS03 EVM Token Order Examples docs](/ucs/03/#evm-token-order-examples).
53+
We also need to determine the `Kind` for the `TokenOrder`. In this case, we use `solve`. Though kind can be `initialize`, `escrow`, `unescrow`, or `solve`. To understand which kind of token order to use, refer to the [ucs03 EVM Token Order Examples docs](/ucs/03/#evm-token-order-examples).
5454

5555
```ts
5656
import { TokenOrder, ZkgmClient, ZkgmClientRequest, ZkgmClientResponse } from "@unionlabs/sdk"
@@ -78,7 +78,7 @@ const program = Effect.gen(function*() {
7878
```
7979

8080
:::note
81-
Solver metadata is supplied here in accordance with [UCS03](/ucs/03)
81+
Solver metadata is supplied here in accordance with [ucs03](/ucs/03)
8282
:::
8383

8484
### 4. zkgm Request
@@ -105,7 +105,7 @@ const program = Effect.gen(function*() {
105105
```
106106

107107
:::note
108-
UCS03 addresses can be found on the [Deployments page](/protocol/deployments/)
108+
ucs03 addresses can be found on the [Deployments page](/protocol/deployments/)
109109
:::
110110

111111
### 5. zkgm Execution & Response

docs/src/content/docs/integrations/typescript/guided-tutorial/evm-holesky-sepolia.mdx

Lines changed: 5 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -3,7 +3,7 @@ title: "Send Funds Holesky → Sepolia"
33
description: Guide for transfers from Holesky to Sepolia.
44
---
55

6-
This guide walk's you through writing our example ["Send Funds Holesky -> Sepolia"](/integrations/typescript/examples/evm/send-funds-holesky-to-sepolia/). The goal of this guide it to show you how to create a token order and submit it to the [UCS03 - ZKGM](/ucs/04) interface.
6+
This guide walks you through writing our example ["Send Funds Holesky -> Sepolia"](/integrations/typescript/examples/evm/send-funds-holesky-to-sepolia/). The goal of this guide it to show you how to create a token order and submit it to the [ucs03-zkgm](/ucs/03) interface.
77

88
Relevant imports will be included with each step. Outside of libraries provided by Union, this guide uses [viem](https://viem.sh/) and [Effect](https://effect.website/).
99

@@ -40,7 +40,7 @@ const program = Effect.gen(function*() {
4040
```
4141

4242
:::note
43-
The ID's provided here are Universal Chain ID's as defined by [UCS04](/ucs/04).
43+
The IDs provided here are Universal Chain IDs as defined by [ucs04](/ucs/04).
4444
:::
4545

4646
### 3. Token Order
@@ -49,7 +49,7 @@ Now you can define the token order that will be responsible for the transfer. Th
4949

5050
To construct the token order, you will need the token contract/denom on both the source chain (`baseToken`) and the destination chain (`quoteToken`). In this case, we are using the relevant contract addresses for LINK.
5151

52-
We also need to determine the `Kind` for the `TokenOrder`. In this case, we use `esccrow`. Though kind can be `initialize`, `escrow`, `unescrow`, or `solve`. To understand which kind of token order to use, refer to the [UCS03 EVM Token Order Examples docs](/ucs/03/#evm-token-order-examples).
52+
We also need to determine the `Kind` for the `TokenOrder`. In this case, we use `esccrow`. Though kind can be `initialize`, `escrow`, `unescrow`, or `solve`. To understand which kind of token order to use, refer to the [ucs03 EVM Token Order Examples docs](/ucs/03/#evm-token-order-examples).
5353

5454
```ts
5555
import * as TokenOrder from "@unionlabs/sdk/TokenOrder"
@@ -102,7 +102,7 @@ const program = Effect.gen(function*() {
102102
```
103103

104104
:::note
105-
UCS03 addresses can be found on the [Deployments page](/protocol/deployments/)
105+
ucs03 addresses can be found on the [Deployments page](/protocol/deployments/)
106106
:::
107107

108108
### 5. zkgm Execution & Response
@@ -144,7 +144,7 @@ const program = Effect.gen(function*() {
144144

145145
:::note
146146
***NOTE #1*** -
147-
In this example, it does not matter, as we manually provide the key and specify the transport in [Execution](#execution). If you were developing a web app with a wallet client - you would need to switch the chains here.
147+
In this example, it does not matter, as we manually provide the key and specify the transport in [Execution](#execution). If you were developing a web app with a wallet client, you would need to switch the chains here.
148148
:::
149149

150150
## Execution

0 commit comments

Comments
 (0)