Skip to content

Commit 6ebaf63

Browse files
amirelemamDonJayamanne
authored andcommitted
Markdown correction (DonJayamanne#887)
1 parent 354dd6d commit 6ebaf63

1 file changed

Lines changed: 5 additions & 5 deletions

File tree

CONTRIBUTING.md

Lines changed: 5 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -20,23 +20,23 @@ Run the build Task from the [Command Palette](https://code.visualstudio.com/docs
2020
### Errors and Warnings
2121
TypeScript errors and warnings will be displayed in VS Code in the Problems Panel (CTRL+SHIFT+M or ⇧⌘M)
2222

23-
###Validate your changes
23+
### Validate your changes
2424
To test the changes you launch a development version of VS Code on the workspace vscode, which you are currently editing.
2525
Use the "Launch Extension" launch option.
2626

27-
###Unit Tests
27+
### Unit Tests
2828
Run the Unit Tests via the "Launch Test" launch option.
2929
Currently unit tests only run on [Travis](https://travis-ci.org/DonJayamanne/pythonVSCode)
3030

3131
_Requirements_
3232
1. Ensure you have disabled breaking into 'Uncaught Exceptions' when running the Unit Tests
3333
2. For the linters and formatters tests to pass successfully, you will need to have those corresponding Python libraries installed locally
3434

35-
##Debugging the extension
36-
###Standard Debugging
35+
## Debugging the extension
36+
### Standard Debugging
3737
Clone the repo into any directory and start debugging.
3838
From there use the "Launch Extension" launch option.
3939

40-
###Debugging the Python Extension Debugger
40+
### Debugging the Python Extension Debugger
4141
The easiest way to debug the Python Debugger (in my opinion) is to clone this git repo directory into [your](https://code.visualstudio.com/docs/extensions/install-extension#_your-extensions-folder) extensions directory.
4242
From there use the ```Launch Extension as debugserver``` launch option.

0 commit comments

Comments
 (0)