Updated Roadmap (markdown)

Roadmap.md

@@ -9,7 +9,7 @@ This page contains a prioritized backlog of upcoming vcpkg work and completion s
   - [ ] **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. 
-- [ ] ** New vcpkg experience in Visual Studio**
+- [ ] **New vcpkg experience in Visual Studio**
   - [ ] **Description:** vcpkg will be included for all Visual Studio C++ workloads. vcpkg will be localized for all the languages VS supports. Potentially some productivity features to make it easy to install and manage libraries from the IDE. vcpkg artifacts will also work in a VS context for MSBuild and Open Folder (including CMake) projects. 
   - [ ] **Status:** Our team has made some investments in this space. We have a special binary distribution of the vcpkg tool that we can add to VS installations. We are working on localization for different languages, as we need to support all languages VS supports to ship with the IDE. We are also exploring some productivity features, like quick action lightbulbs to help VS users install missing libraries. We are in the design phase for the Open Folder integration and the MSBuild integration is currently being coded. This work is still in flux and has been pushed back somewhat by the higher prioritization of vcpkg artifacts, which was introduced to the backlog at a later time. 
   - [ ] **Timeline:** To be determined. 
@@ -18,6 +18,6 @@ This page contains a prioritized backlog of upcoming vcpkg work and completion s
   - [ ] **Status:** Same progress as VS in terms of producing the vcpkg tool binary and localization. We plan to ship the VS Code extension no earlier than the VS experience. 
 
 ### Other Ideas (Unprioritized)
-- [ ] vcpkg artifacts integration in VS Code - use vcpkg to install a compiler, debugger, and other tools that VS Code doesn't provide by default. 
-- [ ] Better integration with GitHub (GitHub Packages, Actions, etc.)
-- [ ] Better integration with Azure services (e.g. Azure DevOps, Azure Artifacts, etc.)
+- vcpkg artifacts integration in VS Code - use vcpkg to install a compiler, debugger, and other tools that VS Code doesn't provide by default. 
+- Better integration with GitHub (GitHub Packages, Actions, etc.)
+- Better integration with Azure services (e.g. Azure DevOps, Azure Artifacts, etc.)