X-Git-Url: https://git.madduck.net/etc/vim.git/blobdiff_plain/dc71922c768e543c9c3bbb1db5ea6d7fa801a814..0ee596c5c5e11fc79598407eaf22f83d279f7e9e:/.vim/bundle/vim-markdown/CONTRIBUTING.md diff --git a/.vim/bundle/vim-markdown/CONTRIBUTING.md b/.vim/bundle/vim-markdown/CONTRIBUTING.md index 86912a4a..736f0238 100644 --- a/.vim/bundle/vim-markdown/CONTRIBUTING.md +++ b/.vim/bundle/vim-markdown/CONTRIBUTING.md @@ -34,7 +34,7 @@ There are many flavors of markdown, each one with an unique feature set. This pl ## Style -When choosing between multiple valid Markdown syntaxes, the default behavior must be that specified at: +When choosing between multiple valid Markdown syntaxes, the default behavior must be that specified at: If you wish to have a behavior that differs from that style guide, add an option to turn it on or off, and leave it off by default. @@ -46,7 +46,7 @@ All new features must have unit tests. Issues are tracked within GitHub. -When reporting issues, your report is more effective if you include a minimal example file that reproduces the problem. Try to trim out as much as possible, until you have the smallest possible file that still reproduces the issue. Paste the example inline into your issue report, quoted using four spaces at the beginning of each line, like this example from issue [#189](https://github.com/plasticboy/vim-markdown/issues/189): +When reporting issues, your report is more effective if you include a minimal example file that reproduces the problem. Try to trim out as much as possible, until you have the smallest possible file that still reproduces the issue. Paste the example inline into your issue report, quoted using four spaces at the beginning of each line, like this example from issue [#189](https://github.com/preservim/vim-markdown/issues/189): ``` Minimal example: