feat: update to include approval flow for paymaster onboarding (#17)

# What 💻 
* Adds approval paymaster flow guide
* Makes small edits / fixes 

# Why ✋
* Distinction between approval flow and general flow paymasters

# Evidence 📷
Include screenshots, screen recordings, or `console` output here
demonstrating that your changes work as intended

<!-- All sections below are optional. You can uncomment any section
applicable to your Pull Request. -->

<!-- # Notes 📝
* Any notes/thoughts that the reviewers should know prior to reviewing
the code? -->

content/10.quick-start/40.upgrading.md

@@ -34,9 +34,7 @@ items: [{
 ---
 ::
 
-## Takeaways and Next Steps
-
-### Takeaways
+## Takeaways
 
 - **Upgradability:** The guide highlights the critical aspect of smart contract upgradability, introducing techniques
 for using transparent, beacon, and UUPS proxies.
@@ -46,7 +44,7 @@ This ensures your contracts remain adaptable, allowing for seamless updates to b
 contracts maintain continuity of state and fund security, even as underlying
 functionalities evolve. This approach provides a resilient framework for your dApps to grow and adapt over time.
 
-### Next Steps
+## Next Steps
 
 - **Exploring Paymasters:** Continue on to the next guide focused on [using paymasters](/quick-start/paymaster)
 with your smart contracts. Paymasters abstract gas payments in transactions,

content/10.quick-start/50.paymaster.md

@@ -63,8 +63,22 @@ items: [{
 
 ## Takeaways
 
--
-
-## Next steps
-
--
+- **Comprehensive Understanding of Paymaster Contracts:** This guide has provided a detailed look at both the
+`ApprovalFlowPaymaster` and the `GeneralPaymaster` contracts, illustrating how they manage transaction fees
+in zkSync. These paymasters are pivotal in handling gas payments, offering a more accessible transaction
+experience for users.
+- **Flexibility and User Empowerment:** By covering the transaction fees through ERC20 tokens or general subsidies, these
+paymaster contracts offer significant flexibility and reduce the friction typically associated with on-chain
+interactions. This feature enhances user engagement and adoption of dApps.
+
+## Next Steps
+
+- **Experiment with Different Paymaster Contracts:** Now that you are familiar with both approval-based and general
+paymaster flows, you can experiment with these contracts by deploying them under various conditions
+and with different types validations, restrictions and enhancements.
+- **Develop a Front-End Interface:** Consider building a user interface that interacts with the paymaster contracts
+you have deployed. This will not only improve the usability of your contracts but also provide practical insights
+into how end-users interact with your dApps in real-world scenarios.
+- **Community Engagement and Contribution:** Join the vibrant zkSync community.
+Participate in forums, Discord, or GitHub discussions. Sharing insights, asking queries,
+and contributing can enrich the ecosystem and your understanding of zkSync.