Squashed 'src/main/resources/csl-styles/' changes from 4d4655e..c1793d2

c1793d2 Create isnad-metinici.csl (JabRef#4704)
099f4a1 Create isnad-dipnotlu.csl (JabRef#4703)
8e8639e Update norois.csl (JabRef#4706)
62f6221 Create amsterdam-university-press.csl (JabRef#4699)
c31d9ca Create tagungsberichte-der-historischen-kommission-fur-ost-und-westpr… (JabRef#4700)
34220d3 Change apa-fr-provost.csl to fr-CA locale (JabRef#4701)
bbdc9c4 Update to better match RMIT Easy Cite (JabRef#4697)
7c506d9 Create Anatomia Histologia Embryologia csl file (JabRef#4688)
61f3dc5 Update pravnik.csl, masarykova-univerzita-pravnicka-fakulta.csl and iso690-full-note-cs.csl (JabRef#4705)
449eaec add DOI to mdpi.csl back (JabRef#4695)
642002e Create muni-law.csl (JabRef#4691)
483d04a Create iso690-author-date-pt (JabRef#4694)
505c006 Update pravnik.csl (JabRef#4690)
eb260ef Update instituto-brasileiro-de-informacao-em-ciencia-e-tecnologia-abn… (JabRef#4692)
9279f0d Update instituto-brasileiro-de-informacao-em-ciencia-e-tecnologia-abn… (JabRef#4693)
70f7be6 Create iso690-full-note-cs-pravnik.csl (JabRef#4686)
db54e56 Update CONTRIBUTING.md
2f16a9b Update CONTRIBUTING.md
4cd05ba Create associacao-brasileira-de-normas-tecnicas-ufrgs-footnote-ibid.csl (JabRef#4369)

git-subtree-dir: src/main/resources/csl-styles
git-subtree-split: c1793d2

CONTRIBUTING.md

@@ -10,7 +10,7 @@ To submit a style, please follow the following steps (for locale files, follow t
 
 #### 1. Check that your style meets all our [style requirements](https://github.com/citation-style-language/styles/wiki/Style-Requirements)
 
-#### 2. [Validate](https://github.com/citation-style-language/styles/wiki/Validation) your style against the CSL schema, and correct any validation errors
+#### 2. [Validate](https://validator.citationstyles.org/) your style against the CSL schema, and correct any validation errors
 
 #### 3. Create a pull request
 
@@ -33,7 +33,7 @@ To start, create a GitHub account and sign in.
 ##### 3b. Submitting changes to an existing style
 
 1. Visit https://github.com/citation-style-language/styles and find the style you wish to change (dependent styles are stored in the [dependent](https://github.com/citation-style-language/styles/tree/master/dependent) subdirectory).
-   To search by file name press "t" (this activates GitHub’s [File Finder](https://github.com/blog/793-introducing-the-file-finder)) and start typing.
+   To search the repository by file name, click the "Find file" button or press <kbd>t</kbd> to activate GitHub’s [file finder](https://help.github.com/en/github/searching-for-information-on-github/finding-files-on-github) and start typing.
 2. Click on the style name, which will bring you to a page like https://github.com/citation-style-language/styles/blob/master/apa.csl.
 3. Click the edit icon (in the shape of a pencil).
    This opens a code editor in which you can make your changes (you can for example copy and paste your modified style into this window).
@@ -52,30 +52,30 @@ We often request you to make some changes to your pull request.
 Don't create a new pull request right away if your original submission has issues.
 It's much easier for us if you update your original pull request instead.
 
-After you create a pull request, our @csl-bot will first automatically run a number of tests to check whether your style validates and follows our style requirements.
+After you create a pull request, our [@csl-bot](https://github.com/csl-bot) will first automatically run a number of tests to check whether your style validates and follows our style requirements.
 These tests usually finish within a few minutes.
-If there are problems, @csl-bot will give a link to the test report, which contains the identified errors.
+If there are problems, [@csl-bot](https://github.com/csl-bot) will leave a comment with the identified errors.
 If you have trouble understanding these errors, please post a comment in the pull request and ask for help.
 
-We also have a handful of volunteers who review pull requests, usually within a day or two.
+We also have a handful of volunteers who review pull requests, usually within a week or two.
 
 To update your pull request:
 
 1. Visit the "Files changed" tab of your pull request.
-2. Click the edit (pencil) icon at the top-right of your style.
+2. Click the ellipsis button at the top-right of your style, and select "Edit file" in the ellipsis menu.
 3. Make your changes, and click the "Commit changes" button.
 
 Any changes made this way will automatically appear in the pull request, and each commit will trigger a new test report.
 
 Once we are satisfied, we will **merge** your pull request.
-This can take hours or days, depending on how busy we are, and on how much back and forth is needed to get your style in acceptable shape.
+This can take days or weeks, depending on how busy we are, and on how much back and forth is needed to get your style in acceptable shape.
 
 #### 5. Make additional changes after merging
 
 Once a pull request has been merged, it can no longer be used to submit further changes.
 So, if you wish to make additional changes, just create a new pull request.
 
-Please always start from the latest version of the style from our repository, because we often perform maintenance on the repository styles.
+Please always start from the latest version of the style from our repository, because we may have performed maintenance on your style or accepted corrections from other contributors.
 
 ## Asking for help