]> git.madduck.net Git - etc/vim.git/blobdiff - .vim/bundle/vim-markdown/CONTRIBUTING.md

madduck's git repository

Every one of the projects in this repository is available at the canonical URL git://git.madduck.net/madduck/pub/<projectpath> — see each project's metadata for the exact URL.

All patches and comments are welcome. Please squash your changes to logical commits before using git-format-patch and git-send-email to patches@git.madduck.net. If you'd read over the Git project's submission guidelines and adhered to them, I'd be especially grateful.

SSH access, as well as push access can be individually arranged.

If you use my repositories frequently, consider adding the following snippet to ~/.gitconfig and using the third clone URL listed for each project:

[url "git://git.madduck.net/madduck/"]
  insteadOf = madduck:

Merge commit 'c58a4f3586473f7476510714698e60835fcb94ef'
[etc/vim.git] / .vim / bundle / vim-markdown / CONTRIBUTING.md
index 86912a4a67ac6b7f9f33041e17539c0eaca3f2ed..736f0238071a1c02f584a042c4a155761bbd8ec9 100644 (file)
@@ -34,7 +34,7 @@ There are many flavors of markdown, each one with an unique feature set. This pl
 
 ## Style
 
 
 ## Style
 
-When choosing between multiple valid Markdown syntaxes, the default behavior must be that specified at: <http://www.cirosantilli.com/markdown-styleguide>
+When choosing between multiple valid Markdown syntaxes, the default behavior must be that specified at: <https://cirosantilli.com/markdown-style-guide>
 
 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.
 
 
 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.
 
 
 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:
 
 ```
 Minimal example: