Updated Release planning process (markdown)

Release-planning-process.md

@@ -1,6 +1,6 @@
 We often get questions about how we choose specific features to go into a particular release. 
 
-Of course we have a [roadmap](roadmap), which defines a set of important features we want to support, and we have [a backlog milestone in our issue tracker](https://github.com/aspnet/EntityFrameworkCore/issues?q=is%3Aopen+is%3Aissue+milestone%3ABacklog+sort%3Areactions-%2B1-desc) in which issues can be up-voted, and a few other sources of ideas like [our UserVoice page](https://data.uservoice.com/forums/72025-entity-framework-core-feature-suggestions), but that doesn't automatically translate into a release plan.
+Of course we have a [roadmap](roadmap), which defines a set of important features we want to support, and we have [a backlog milestone in our issue tracker](https://github.com/aspnet/EntityFrameworkCore/issues?q=is%3Aopen+is%3Aissue+milestone%3ABacklog+sort%3Areactions-%2B1-desc) in which issues can be up-voted, and a few other sources of ideas like [our UserVoice page](https://data.uservoice.com/forums/72025-entity-framework-core-feature-suggestions). But all that that doesn't automatically translate into a release plan.
 
 It is difficult to detail here the whole process we follow to plan a release, partly because a lot of it is discussing the specific features, opportunities and priorities, and partly because the process itself usually evolves with every release. However, it is relatively easy to summarize the common questions we try to answer when deciding what to work on next: