Since no-one commented, I took the liberty of adding the following files
to <https://files.scheme.org>:

errata-corrected-r6rs.pdf (from Göran)
errata-corrected-r6rs-app.pdf (from Göran)
errata-corrected-r6rs-lib.pdf (from Göran)
errata-corrected-r6rs-rationale.pdf (from Göran)
errata-corrected-r7rs.pdf (from John)

r5rs.pdf (official)
r6rs.pdf (official)
r6rs-app.pdf (official)
r6rs-lib.pdf (official)
r6rs-rationale.pdf (official)
r7rs.pdf (official)

Let me know if the naming and/or the act of publishing the
errata-corrected versions on files.scheme.org is not all right.

The errata-corrected versions can be expected to change as more errata
are discovered. files.scheme.org should have some way to distinguish
between set-in-stone files (like a git tag) and moving targets (like a
git branch).

Set-in-stone files can still in theory be revoked for security or
copyright reasons, as can git tags, but are not intended to change.