update readme

Author: dglowinski

README.md

@@ -41,7 +41,7 @@ Swagger UI is served at the root, it is also available at [swap.euler.finance](h
 
 ## Fetching quotes and executing trades
 
-The `/swap` endpoint fetches token trade quotes which can be used with the swapping peripheries in the Euler Vault Kit [periphery contracts](https://github.com/euler-xyz/evk-periphery/tree/master/src/Swaps). See [periphery docs](https://github.com/euler-xyz/evk-periphery/blob/master/docs/swaps.md) for detailed description of the swapping architecture in Euler V2. The API response includes both encoded payloads as well as raw data for calls to the `Swapper` (`swap` field of the response) and `SwapVerifier` (`verify` field) contracts. These payloads can be used directly in EVC batches.
+The `/swaps` endpoint fetches token trade quotes which can be used with the swapping peripheries in the Euler Vault Kit [periphery contracts](https://github.com/euler-xyz/evk-periphery/tree/master/src/Swaps). See [periphery docs](https://github.com/euler-xyz/evk-periphery/blob/master/docs/swaps.md) for detailed description of the swapping architecture in Euler V2. The API response includes both encoded payloads as well as raw data for calls to the `Swapper` (`swap` field of the response) and `SwapVerifier` (`verify` field) contracts. These payloads can be used directly in EVC batches.
 
 Example of fetching a swap and repay quote to use e.g. in liquidation:
 
@@ -101,7 +101,7 @@ const batchItems =
     value: 0,
     data: response.data.swap.swapperData
   },
-  // execut SwapVerifier payload from the API response
+  // execute SwapVerifier payload from the API response
   {
     targetContract: response.data.verify.verifierAddress,
     onBehalfOfAccount: connectedAccount,
@@ -124,11 +124,18 @@ const evcBatch = encodeFunctionData({
 
 To handle an incoming swap request, the API processes the query through a series of strategies until one of them provides a valid response. The strategy pipelines are defined per chain in `/swapService/config` folder. The strategies can handle requests in multiple ways. The basic one is the balmy SDK strategy, which queries multiple DEXes and aggregators for a swap quote and picks the best one. Strategies can themselves run the pipelines recursively. ERC4626 wrapper can be configured for assets which are vault shares and are not supported by aggregators. The strategy will deposit or redeem vault shares and run the pipeline again, this time using the underlying asset of the vault. For a list of available strategies see `swapService/strategies` folder.
 
-The pipeline definition consits of an array of objects, each of which designates a strategy with its configuration and an optional matching logic. In the following example, the pipeline is configured to query Pendle and LI.FI for swap of the Pendle PT tokens, and 1Inch and LI.FI for all other tokens.
+The pipeline definition consits of an array of objects, each of which designates a strategy with its configuration and an optional matching logic. In the following example, the pipeline is configured to query Pendle and LI.FI for swap of the Pendle PT tokens, and 1Inch and LI.FI for all other tokens. There's also a repay wrapper strategy, which processes a regular exact input quote to include a repay on the receiver vault.
 
 ```js
 const pipeline = [
-    {
+  {
+    strategy: StrategyRepayWrapper.name(),
+    match: {
+      isRepay: true,
+      swapperModes: [SwapperMode.EXACT_IN],
+    },
+  },
+  {
     strategy: StrategyBalmySDK.name(),
     config: {
       sourcesFilter: {