Skip to content

Commit

Permalink
Update usage.md (#8)
Browse files Browse the repository at this point in the history
changed "transactions that should be submit in order" to "transactions that should be submitted in order" and "newly created intents that can be submit onchain" to "newly created intents that can be submitted onchain"
  • Loading branch information
palocu authored Jun 26, 2024
1 parent 946af93 commit a2aa7f4
Showing 1 changed file with 2 additions and 2 deletions.
4 changes: 2 additions & 2 deletions developers/usage.md
Original file line number Diff line number Diff line change
Expand Up @@ -45,7 +45,7 @@ With just one line of code, you've instantiated everything that is needed to cre

## Signing an Intent

When creating an intent, you'll create a set of constraints that define the limits of execution as well as any transactions that should be submit in order to execute the intent.
When creating an intent, you'll create a set of constraints that define the limits of execution as well as any transactions that should be submitted in order to execute the intent.

In practice, this is as simple as:

Expand Down Expand Up @@ -76,7 +76,7 @@ await plug.submit(plugs);

## Streaming Intents

On the other side of things, Solvers have the ability to listen for newly created intents that can be submit onchain. Using the same framework used to sign intents, a Solver can open a connection to the distribution channel with:
On the other side of things, Solvers have the ability to listen for newly created intents that can be submitted onchain. Using the same framework used to sign intents, a Solver can open a connection to the distribution channel with:

::: code-group

Expand Down

0 comments on commit a2aa7f4

Please sign in to comment.