I ran `codespell` on modules owned by core-libs, and accepted those changes 
where it indeed discovered real typos.

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 core
 - Pass #1 core
 - Pass #2 misc
 - Pass #1 misc

Changes: https://git.openjdk.java.net/jdk/pull/8364/files
 Webrev: https://webrevs.openjdk.java.net/?repo=jdk&pr=8364&range=00
  Issue: https://bugs.openjdk.java.net/browse/JDK-8285485
  Stats: 215 lines in 103 files changed: 0 ins; 0 del; 215 mod
  Patch: https://git.openjdk.java.net/jdk/pull/8364.diff
  Fetch: git fetch https://git.openjdk.java.net/jdk pull/8364/head:pull/8364

PR: https://git.openjdk.java.net/jdk/pull/8364

Reply via email to