Add link to code quality.

Author: koppor

docs/development-strategy.md

@@ -5,11 +5,13 @@ We aim to keep up to high-quality code standards and use code quality tools wher
 To ensure high code-quality,
 
 * we follow the principles of [Java by Comparison](https://java.by-comparison.com/).
-* we follow the principles of [Effetcive Java](https://www.oreilly.com/library/view/effective-java-3rd/9780134686097/).
+* we follow the principles of [Effective Java](https://www.oreilly.com/library/view/effective-java-3rd/9780134686097/).
 * we use [Design Pattners](https://java-design-patterns.com/patterns/) when applicable.
 * we document our design decisions using the lightweight architectural decision records [MADR](https://adr.github.io/madr/).
 * we review each external pull request by at least two [JabRef Core Developers](https://github.com/JabRef/jabref/blob/master/DEVELOPERS).
 
+Read on on our automated quality checks at [Code Quality](code-quality.md).
+
 ## Continuos integration
 
 Since end of 2019, we just use GitHub actions to execute our tests and to creates binaries. The binaries are create using [gradle](https://gradle.org/) and are uploaded to to [https://builds.jabref.org](https://builds.jabref.org). These binaries are created without any checks to have them available as quickly as possible, even if the localization or some fetchers are broken. Deep link: [https://github.com/JabRef/jabref/actions?workflow=Deployment](https://github.com/JabRef/jabref/actions?workflow=Deployment).