@@ -31,17 +31,17 @@ high quality, we request that contributions adhere to the following guidelines.
3131- ** Provide a link to the application or project’s homepage** . Unless it’s
3232 extremely popular, there’s a chance the maintainers don’t know about or use
3333 the language, framework, editor, app, or project your change applies to.
34-
34+
3535- ** Provide links to documentation** supporting the change you’re making.
3636 Current, canonical documentation mentioning the files being ignored is best.
3737 If documentation isn’t available to support your change, do the best you can
3838 to explain what the files being ignored are for.
39-
39+
4040- ** Explain why you’re making a change** . Even if it seems self-evident, please
4141 take a sentence or two to tell us why your change or addition should happen.
4242 It’s especially helpful to articulate why this change applies to * everyone*
4343 who works with the applicable technology, rather than just you or your team.
44-
44+
4545- ** Please consider the scope of your change** . If your change specific to a
4646 certain language or framework, then make sure the change is made to the
4747 template for that language or framework, rather than to the template for an
@@ -70,9 +70,9 @@ Here’s how we suggest you go about proposing a change to this project:
7070Using the web-based interface to make changes is fine too, and will help you
7171by automatically forking the project and prompting to send a pull request too.
7272
73- [ fork ] : http ://help.github.com/forking /
73+ [ fork ] : https ://help.github.com/articles/fork-a-repo /
7474[ branch ] : https://help.github.com/articles/creating-and-deleting-branches-within-your-repository
75- [ pr ] : http ://help.github.com/pull-requests/
75+ [ pr ] : https ://help.github.com/articles/using- pull-requests/
7676
7777## License
7878
0 commit comments