I ran `codespell` on the `src/java.desktop` directory, and accepted those changes where it indeed discovered real typos.
I ignored typos in public methods and variables. Maybe they can be fixed later on without much fanfare, if they are in internal classes. Typos in exposed APIs are likely here to stay. I will update copyright years using a script before pushing (otherwise like every second change would be a copyright update, making reviewing much harder). The long term goal here is to make tooling support for running `codespell`. The trouble with automating this is of course all false positives. But before even trying to solve that issue, all true positives must be fixed. Hence this PR. ------------- Commit messages: - Pass #2 - Pass #1 Changes: https://git.openjdk.java.net/jdk/pull/8328/files Webrev: https://webrevs.openjdk.java.net/?repo=jdk&pr=8328&range=00 Issue: https://bugs.openjdk.java.net/browse/JDK-8285306 Stats: 1015 lines in 493 files changed: 0 ins; 0 del; 1015 mod Patch: https://git.openjdk.java.net/jdk/pull/8328.diff Fetch: git fetch https://git.openjdk.java.net/jdk pull/8328/head:pull/8328 PR: https://git.openjdk.java.net/jdk/pull/8328
