Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

fix: docs typos #35

Open
wants to merge 6 commits into
base: main
Choose a base branch
from
Open
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions pages/bundler-api/api-reference/bundle.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -28,7 +28,7 @@ Enso Bundler offer developers a versatile approach to interacting with DeFi prot

#### Enso Router
Designed to simplify the process of executing transactions across various DeFi protocols, the Enso Router abstracts complex protocol interactions into a user-friendly interface. This allows developers to efficiently route transactions, swap tokens, and manage liquidity across multiple platforms with minimal effort.
**Example:**\
**Example:**
```json copy
[
{
Expand All @@ -46,7 +46,7 @@ Designed to simplify the process of executing transactions across various DeFi p

#### Contract Calls
For those seeking granular control over their DeFi interactions, The `call` action is a powerful tool to execute custom logic directly on the blockchain. This feature empowers developers to craft tailored transactions, interact with smart contracts beyond the predefined Enso Router pathways, and implement unique strategies that align with their specific objectives.
The usage is very similar to the route endpoint (which uses under the hood the same functionalities), and it's as simpler as Token A -> Token B where both can be base tokens or vaults, lps and so on.\
The usage is very similar to the route endpoint (which uses under the hood the same functionalities), and it's as simple as Token A -> Token B where both can be base tokens or vaults, lps and so on.\
**Example:**\
After routing to a specific token, transfer the swapped amount to a specific address
```json copy
Expand Down
2 changes: 1 addition & 1 deletion pages/bundler-api/introduction.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -8,7 +8,7 @@ The Bundle API is a powerful tool within the ENSO API suite that lets developers
With just one API call, you can trigger several operations, making your interaction with various DeFi simpler and cheaper.

When first used, it automatically deploys a minimal smart wallet which is then used to execute the bundled transactions.
The smart wallet can be controlled only by the user and is the execution contex when doing transactions.
The smart wallet can be controlled only by the user and is the execution context when doing transactions.

Moreover, the Bundle API excels in gas optimization. The more transactions you bundle, the more you can save on gas fees. This makes it an economical choice for users seeking to execute multiple operations efficiently in the DeFi space.

Expand Down
2 changes: 1 addition & 1 deletion pages/concepts/routingOptions.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -12,7 +12,7 @@ Recommended usecase:
1. EOAs

## Delegate
`delegate`: returns calldata in the form of delegateCalls, which allows [tokenized](./tokenized-nontokenized/tokenized.mdx) and [non-tokenized](./tokenized-nontokenized/nontokenized.mdx). Enabling all state of the smart account to remaiin in the smart account, and not in the router.
`delegate`: returns calldata in the form of delegateCalls, which allows [tokenized](./tokenized-nontokenized/tokenized.mdx) and [non-tokenized](./tokenized-nontokenized/nontokenized.mdx). Enabling all state of the smart account to remain in the smart account, and not in the router.

Recommended usecase:
1. Smart Account
Expand Down
2 changes: 1 addition & 1 deletion pages/introduction/intro-to-enso.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -69,7 +69,7 @@ All of these network participants can leverage Enso not only for execution, but
6. **Yield Farming Funds**: Rely upon Enso for providing you all the metadata and execution paths you need to make the best decisions for your fund.
7. **DeFi protocols**: Offer one-click deposits from any token into your protocol natively on your own interface to increase your TVL.
8. **Account Abstraction SDKs**: Natively bake within your SDK the ability to not only create Smart Wallets compatible with ERC4337 but also enable Enso API to supercharge your SDK users for building the next generation of DeFi applications.
9. **Strategy Platforms**: Enso is a highly flexible and versatile framework that allows you to create custom DeFi strategies where you can create your own custom workflows, and build your own interface and full product ontop of Enso! In theory you can replicate many DeFi products that exist as of today through this method and go to market extremely quick to test your product.
9. **Strategy Platforms**: Enso is a highly flexible and versatile framework that allows you to create custom DeFi strategies where you can create your own custom workflows, and build your own interface and full product on top of Enso! In theory you can replicate many DeFi products that exist as of today through this method and go to market extremely quick to test your product.



Expand Down
2 changes: 1 addition & 1 deletion pages/router-api/api-reference/route.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -51,7 +51,7 @@ The tx objects gives you the transaction to use in ethers. The other fields are
Spend Ether from the EOA and get stETH in return.

Specify a tokenIn (ETH), tokenOut (stETH) and either a sellAmount to get a route of 1 ETH for WETH.
The route endpoint will calculate the best route for you, choosing between all the avilable AMM's and protocols (E.g. depositing directly to Lido).
The route endpoint will calculate the best route for you, choosing between all the available AMM's and protocols (E.g. depositing directly to Lido).

If depositing directly to LIDO is the best route the tx object will contain the data to call the deposit function on the LIDO contract, otherwise it will contain the data to call the best AMM.

Expand Down