Merge pull request #124 from OpenZeppelin/add-fee-abstraction-stellar

chore: Update stellar fee abstraction guide

Author: tirumerla

content/relayer/1.3.x/guides/stellar-sponsored-transactions-guide.mdx

@@ -101,7 +101,7 @@ Additional fee margin added to estimated fees to account for price fluctuations
 
 Before users can pay fees in tokens, the relayer account must establish trustlines to those tokens. This is a one-time setup per token.
 
-For a complete example of how to create trustlines, see the [Relayer SDK example](https://github.com/OpenZeppelin/openzeppelin-relayer-sdk/tree/main/examples/relayer/stellar/sponsored/create-trustline.ts).
+For a complete example of how to create trustlines, see the [Relayer SDK example](https://github.com/OpenZeppelin/openzeppelin-relayer-sdk/tree/main/examples/relayers/stellar/src/sponsored/createTrustline.ts).
 
 
 ## Using the API
@@ -153,7 +153,7 @@ Or with operations:
 }
 ```
 
-For complete code examples, see the [Relayer SDK examples](https://github.com/OpenZeppelin/openzeppelin-relayer-sdk/tree/main/examples/relayers/stellar/sponsored).
+For complete code examples, see the [Relayer SDK examples](https://github.com/OpenZeppelin/openzeppelin-relayer-sdk/tree/main/examples/relayers/stellar/src/sponsored).
 
 ### Step 2: Build Sponsored Transaction
 
@@ -203,7 +203,7 @@ Or with operations:
 }
 ```
 
-For complete code examples, see the [Relayer SDK examples](https://github.com/OpenZeppelin/openzeppelin-relayer-sdk/tree/main/examples/relayers/stellar/sponsored).
+For complete code examples, see the [Relayer SDK examples](https://github.com/OpenZeppelin/openzeppelin-relayer-sdk/tree/main/examples/relayers/stellar/src/sponsored).
 
 ### Step 3: Sign Transaction
 
@@ -233,7 +233,7 @@ If the user's address is connected with another relayer configured in **relayer
 
 You can also use any Stellar SDK or signing library to sign the transaction programmatically with the user's private key.
 
-For complete code examples, see the [Relayer SDK examples](https://github.com/OpenZeppelin/openzeppelin-relayer-sdk/tree/main/examples/relayers/stellar/sponsored).
+For complete code examples, see the [Relayer SDK examples](https://github.com/OpenZeppelin/openzeppelin-relayer-sdk/tree/main/examples/relayers/stellar/src/sponsored).
 
 ### Step 4: Submit to Relayer
 
@@ -270,7 +270,7 @@ Submit the signed transaction to the relayer. The relayer will:
 }
 ```
 
-For complete code examples, see the [Relayer SDK examples](https://github.com/OpenZeppelin/openzeppelin-relayer-sdk/tree/main/examples/relayers/stellar/sponsored).
+For complete code examples, see the [Relayer SDK examples](https://github.com/OpenZeppelin/openzeppelin-relayer-sdk/tree/main/examples/relayers/stellar/src/sponsored).
 
 ## Request/Response Formats
 

content/relayer/1.3.x/stellar.mdx

@@ -253,7 +253,7 @@ The build endpoint returns a prepared transaction that includes:
 
 After receiving the prepared transaction, users must sign it and submit it through the standard transaction submission endpoint. The relayer will wrap it in a fee-bump transaction where the relayer pays the XLM fees, and the user pays the token fees.
 
-For detailed examples and code samples, see the [SDK Stellar examples](https://github.com/OpenZeppelin/openzeppelin-relayer-sdk/tree/main/examples/relayers/stellar/sponsored).
+For detailed examples and code samples, see the [SDK Stellar examples](https://github.com/OpenZeppelin/openzeppelin-relayer-sdk/tree/main/examples/relayers/stellar/src/sponsored).
 
 ## API Reference