Fix markdown in documentation in 'Manually specifying an interpreter' #511

Activity

1. Don Jayamanne (DonJayamanne)

   added

   awaiting 2-PR

   feature-documentation

   bugIssue identified by VS Code Team member as probable bugIssue identified by VS Code Team member as probable bug

   on Jan 2, 2018
2. Don Jayamanne (DonJayamanne)

   added this to the January 2018 milestone on Jan 2, 2018
3. Don Jayamanne (DonJayamanne)

   added

   good first issue

   on Jan 2, 2018
4. gaurikholkar-zz commented on Jan 9, 2018

   

   Gauri Kholkar (gaurikholkar-zz)

   on Jan 9, 2018

   Last edited by gaurikholkar-zz

   More actions

   Can I pick this up?
5. DonJayamanne commented on Jan 9, 2018

   

   Don Jayamanne (DonJayamanne)

   on Jan 9, 2018

   Author

   More actions

   Anyone can pick an issue and submit a PR. specially those takes with 'Good first issue'.
   So to answer your question, most certainly yes.
6. Brett Cannon (brettcannon)

   assigned

   Dan Taylor (qubitron)

   and

   Brett Cannon (brettcannon)

   and unassigned

   Dan Taylor (qubitron)

   on Jan 9, 2018
7. Brett Cannon (brettcannon)

   added

   closed-fixed

   on Jan 12, 2018
8. brettcannon commented on Jan 12, 2018

   

   Brett Cannon (brettcannon)

   on Jan 12, 2018

   Member

   More actions

   Sorry, gaurikholkar , but we went ahead and fixed this while dealing with other doc bugs that were in the same file.

   Fixed in microsoft/vscode-docs#1350 .
9. Brett Cannon (brettcannon)

   closed this as completedon Jan 12, 2018
10. Brett Cannon (brettcannon)

    added

    awaiting 4-validation

    and removed

    awaiting 1-decision

    awaiting 2-PR

    awaiting 4-validation

    on Jan 29, 2018
11. Don Jayamanne (DonJayamanne)

    removed

    awaiting 4-validation

    on Jan 29, 2018
12. Brett Cannon (brettcannon)

    added

    closed-verified fixed

    and removed

    closed-fixed

    on Feb 1, 2018
13. lock

    locked as resolved and limited conversation to collaborators on Jul 12, 2018