Fix typos

docs/development-strategy.md

@@ -1,4 +1,4 @@
-# JabRef's development strategy
+# JabRef's Development Strategy
 
 We aim to keep up to high-quality code standards and use code quality tools wherever possible.
 
@@ -10,9 +10,9 @@ To ensure high code-quality,
 * 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).
+Read on about our automated quality checks at [Code Quality](code-quality.md).
 
-## Continuos integration
+## Continuous 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).