1- # Contributing to iText 7 Community
1+ # Contributing to iText Community
22
3- We'd love for you to contribute to our source code and to make ** iText 7 Community** even better than it is
3+ We'd love for you to contribute to our source code and to make ** iText Community** even better than it is
44today! Here are the guidelines we'd like you to follow:
55
66 - [ Question or Problem?] ( #question )
@@ -15,7 +15,7 @@ today! Here are the guidelines we'd like you to follow:
1515
1616## <a name =" question " >Got a Question or Problem?</a >
1717
18- If you have questions about how to use ** iText 7 Community** , please direct these to [ Stack Overflow] [ stackoverflow ] .
18+ If you have questions about how to use ** iText Community** , please direct these to [ Stack Overflow] [ stackoverflow ] .
1919
2020If you are a customer with a [ support agreement] [ support ] , you also have direct access to our JIRA and our developers.
2121
@@ -55,7 +55,7 @@ chances of your issue being dealt with quickly:
5555* ** Related Issues** - has a similar issue been reported before?
5656* ** Suggest a Fix** - if you can't fix the bug yourself, perhaps you can point to what might be
5757 causing the problem (line of code or commit)
58- * ** Tag the question** - add the tag ` itext7 ` to your question so we can find it.
58+ * ** Tag the question** - add the tag ` itext ` to your question so we can find it.
5959
6060** If you get help, help others. Good karma rulez!**
6161
@@ -79,7 +79,7 @@ Before you submit your pull request consider the following guidelines:
7979* Build your changes locally to ensure all the tests pass.
8080* Push your changes to your GitHub account.
8181* Create a pull request in GitHub.
82- "Head fork" should be your repository, and the "base fork" should be the iText7 official repository.
82+ "Head fork" should be your repository, and the "base fork" should be the iText official repository.
8383* If we suggest changes then:
8484 * Make the required updates.
8585 * Fix up your commits if needed, with an interactive rebase.
@@ -111,7 +111,7 @@ To ensure consistency throughout the source code, keep these rules in mind as yo
111111
112112We have guidelines on how our git commit messages should be formatted. This leads to ** more
113113readable messages** that are easy to follow when looking through the ** project history** . But also,
114- we use the git commit messages to ** generate the iText 7 Community change log** .
114+ we use the git commit messages to ** generate the iText Community change log** .
115115
116116These guidelines were taken from Chris Beams' blog post [ How to Write a Git Commit Message] [ git-commit ] .
117117
@@ -169,7 +169,7 @@ We use the [Stack Exchange][stackoverflow] network for free support and [GitHub]
169169[ javadocs ] : https://itextpdf.com/api
170170[ pull ] : https://github.com/itext/i7j-pdfhtml/pulls
171171[ sscce ] : http://sscce.org/
172- [ stackoverflow ] : https://stackoverflow.com/questions/tagged/itext7
172+ [ stackoverflow ] : https://stackoverflow.com/questions/tagged/itext
173173[ good-questions ] : https://stackoverflow.com/help/how-to-ask
174174[ mcve ] : https://stackoverflow.com/help/mcve
175175[ support ] : https://itextpdf.com/support
0 commit comments