Updated Release planning process (markdown)

Release-planning-process.md

@@ -14,6 +14,6 @@ It is difficult to detail here the whole process we follow to plan a release, pa
 
 5. **What is the synergy of the feature when used in combination with other products?** We tend to favor features that allow EF Core to be used with other products or to significantly improve the experience of using other products, such as .NET Core, the latest version of Visual Studio, Microsoft Azure, etc.
 
-6. **What are the capabilities of the people available to work on a feature, and how to best leverage these resources?** Each member of the EF team and even our community contributors have different amounts of experience in different areas and we have to plan accordingly. Even if we wanted to have “all hands on deck” to work on a feature like GroupBy translations, or many-to-many, that wouldn’t be practical.
+6. **What are the capabilities of the people available to work on a feature, and how to best leverage these resources?** Each member of the EF team and even our community contributors have different levels of experience in different areas and we have to plan accordingly. Even if we wanted to have “all hands on deck” to work on a feature like GroupBy translations, or many-to-many, that wouldn’t be practical.
 
-In the future we would like to add more opportunities for members of the developer community to provide an input into release plans, e.g. by making it easier to review proposed drafts of the features and of the release plan itself.
+In the future we would like to add more opportunities for members of the developer community to provide inputs into release plans, e.g. by making it easier to review proposed drafts of the features and of the release plan itself.