misc: fix grammar and spelling

[jbampton]

General clean up

[volosied]

Looks like a majority of white space changes, and some spelling.

[volosied]

Before I merge, let me confirm there's no issue modifying the xsd files (whitespace). @bohmber would you see any potential issues?

[volosied]

@henningn

Do you see any potential problems regarding the whitespace changes in the xsd files? If not, I'd like to merge this. Thanks!

[henningn]

I have discussed this with @lofwyr14. Please do not change the released documentation. Especially not the XSD. The spelling issue must be fixed in the next version of the XSD.

[lofwyr14]

It is good to correct spelling mistakes. However, this must be done at the source. Subsequent changes to releases are to be discarded.

In general, this is my point of view:

Releases must be immutable
Under ASF policy, a published release artefact (including Javadoc and XSDs) must not be changed; any modification, even spelling fixes, effectively creates a new release that hasn’t gone through the formal process.

Reproducibility and trust
Users must be able to verify that what they have matches the signed release. If we silently edit generated docs, the content no longer matches the original source + build at release time.

Auditability and legal provenance
ASF emphasizes clear, traceable provenance of what was released and when. Post-hoc edits blur that boundary and can complicate legal or compliance questions later.

Version history clarity
The documentation associated with version X.Y should represent exactly what was shipped as X.Y. If we want corrected docs, they should be published as part of a new release or as separate, clearly marked, website content (e.g. “fixed docs” or errata), not by rewriting the original artefacts.

[lofwyr14]

No changes in releases