@stasadev suggestions, thanks

Co-authored-by: Stanislav Zhuk <[email protected]>

src/content/blog/2025-plans.md

@@ -28,7 +28,7 @@ We'd love to have your input as daily users as we work through these this month.
 ## Sustainability and Finance
 
 - **Improve our Marketing CTA and information**: The [ddev.com "Support DDEV"](https://ddev.com/support-ddev/) page says lots of things, but the financial CTA gets lost there. We need to make it completely clear that for the project to be sustainable, the community will need to support the two developers who are working full-time on it, and make clear the many ways that this can be done.
-- **Continue to develop contributors and maintainers**: As the project grows, we need more skilled contributors and maintainers. (The only difference between those is that maintainers typically have a higher level of direct access to project resources, but as a wide-open source project, almost all interested contributors can accomplish almost anything without enhanced privileges.) In the last two years, we [quite a lot of contributor trainings](/blog/category/training), and anecdotes indicate that people are using those recordings and blogs for training, but the actual attendance at them was not impressive. I'm thinking that this year these topics should probably be addressed with screenshare recordings and updated blogs instead of calendar-scheduled events. Given the financial struggles in our contributors' world, I doubt that we'll be able to add paid maintainers in 2025, I'm most interested right now in the reasonable goal of retaining and paying the two amazing maintainers we currently have.
+- **Continue to develop contributors and maintainers**: As the project grows, we need more skilled contributors and maintainers. (The only difference between those is that maintainers typically have a higher level of direct access to project resources, but as a wide-open source project, almost all interested contributors can accomplish almost anything without enhanced privileges.) In the last two years, we've had [quite a lot of contributor trainings](/blog/category/training), and anecdotes indicate that people are using those recordings and blogs for training, but the actual attendance at them was not impressive. I'm thinking that this year these topics should probably be addressed with screenshare recordings and updated blogs instead of calendar-scheduled events. Given the financial struggles in our contributors' world, I doubt that we'll be able to add paid maintainers in 2025, I'm most interested right now in the reasonable goal of retaining and paying the two amazing maintainers we currently have.
 
 ## Features and Initiatives
 
@@ -40,7 +40,7 @@ We'd love to have your input as daily users as we work through these this month.
 
 ### Proposed Features and Initiatives
 
-1. We have applied to the [Google Summer of Code](https://summerofcode.withgoogle.com/) but have more work to do. We have to have a list of proposed projects that potential mentees can take on. The features in this section would be possibilities. We'll also be looking for community mentors, and maybe some of you would like to sign up for being mentees via Google this summer!
+1. We have applied to the [Google Summer of Code](https://summerofcode.withgoogle.com/) but there's still more work to do. We need to prepare a list of proposed projects that potential mentees can take on. The features in this section would be possibilities. We'll also be looking for community mentors, and maybe some of you would like to sign up for being mentees via Google this summer!
 2. The TYPO3 community has a [Q2 Community Budget Ideas](https://typo3.org/article/call-for-community-budget-ideas-q2-2025) call out, and we plan to propose one of the ideas discussed here.
 3. [Implement mDNS as an alternate name resolution technique](https://github.com/ddev/ddev/issues/6663) in addition to DNS and hosts file manipulation. Our traditional use of DNS and hosts-file manipulation have been successful, but mDNS might allow avoiding hosts-file manipulation, especially with non-ddev.site URLs and when internet DNS is not available.
 4. [Allow Add-ons to include other add-ons](https://github.com/ddev/ddev/issues/6912): Add-ons can already require other add-ons, but they should be able to automatically result in a download.