Fix typo

docs/development-strategy.md

@@ -6,7 +6,7 @@ To ensure high code-quality,
 
 * we follow the principles of [Java by Comparison](https://java.by-comparison.com/).
 * 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 use [Design Patterns](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).
 
@@ -22,7 +22,7 @@ The branch [master](https://builds.jabref.org/master/) is the main development l
 
 Other branches are used for discussing improvements with the help of [pull requests](https://github.com/JabRef/jabref/pulls). One can see the binaries of each branch at [https://builds.jabref.org/](https://builds.jabref.org/). Releases mark milestones and are based on the master at a point in time.
 
-## How JabRef aquires contributors
+## How JabRef acquires contributors
 
 * We participate in [Hacktoberfest](https://hacktoberfest.digitalocean.com/). See [https://www.jabref.org/hacktoberfest/](https://www.jabref.org/hacktoberfest/) for details.
 * We participate in [Google Summer of Code](https://developers.google.com/open-source/gsoc/).