Updated Roadmap (markdown)

Roadmap.md

@@ -2,10 +2,10 @@ This page contains a prioritized backlog of upcoming vcpkg work and completion s
 
 ### Prioritized Backlog
 - **Documentation overhaul**
-  - **Description:** We have been getting lots of feedback about our documentation. There are a couple of areas where we need to brush up existing documentation, write new articles, and also make sure people find the articles relevant to their work. For the latter, we want to improve the internal search experience for our documentation. We also want vcpkg.io as the central hub for documentation, rather than duplicating between the website and GitHub. We also want to review how we describe what an official vs. a community triplet is, since there seems to be some confusion about what target platforms x architectures vcpkg can support. 
+  - **Description:** We have been getting lots of feedback about our documentation. There are a couple of areas where we need to brush up existing documentation, write new articles, and also make sure people find the articles relevant to their work. For the latter, we want to improve the internal search experience for our documentation. To avoid confusion about which documentation is correct, we want vcpkg.io to be treated as authoritative. We will provide the same kind of deep linking capabilities currently provided only on GitHub and use vcpkg.io in customer explanations of our behavior. We also want to review how we describe what an official vs. a community triplet is, since there seems to be some confusion about what target platforms x architectures vcpkg can support. 
   - **Status:** We are working on a plan for this experience, so we are still on the planning/design phase. 
   - **Timeline:** To be determined.
-- **vcpkg artifacts minimum viable product and Windows artifacts**
+- **MSVC and other Windows tools available in vcpkg artifacts**
   - **Description:** Finish implementing vcpkg commands for the artifacts experience and make sure it synergizes well with ports. Fix known issues. Provide vcpkg artifacts for MSVC toolset and Windows SDK. Add MSBuild integration for vcpkg artifacts and tweak the experience for ports as well for a better experience in Visual Studio. 
   - **Status:** We have engineers at Microsoft assigned to each area for this and are actively working on this. Someone is working on finishing up the core command line experience for artifacts and cleaning up remaining bugs. Our top MSBuild expert is working on that integration. A third person is designing the MSVC artifact story. We have also been talking to the Windows SDK team about incorporating their NuGet package editions of their SDK into vcpkg artifacts at some point in the future, but we need to finish preparing the rest of the story so it's clear to them exactly how they should organize their packages to work with vcpkg. 
   - **Timeline:** To be determined.