Best effort internal review using readily available accessible language guides

[scottrigby]

What we've done so far and plans

• @todaywasawesome, @murillodigital and I all tried to bear this in mind before publishing RC 2
• The longer-term effort, Ensure documents language is accessible and inclusive #73 – originally planned for v1.0.0 release milestone – has now been moved to a post-KubeCon NA 2021 milestone. There is now an internal CNCF support ticket for this, which has already been noticed by and CNCF techdocs team and soon will be added to the techdocs queue! It will for sure not happen until after KubeCon NA 2021.

How you can help now

We can at least do a best effort internal review before KubeCon. Can we please get more eyes on this from WG members and maintainers before the planned v1.0.0 release at the end of this week?

1. Please re-read PRINCIPLES.md, GLOSSARY.md, and README.md from a language accessibility point of view. You can comment here or give an emoji reaction if that is more efficient.

2. We are now asking YOU – WG members & maintainers – to 👍 or 👎 this issue by Friday Oct 8th. (ideally, also comment a short reason).

   Note this does not require language accessibility expertise – that is scheduled with CNCF already. This is an ask for one more best effort pass by WG members available to do so before 1.0.0 goes out.

Thanks! 😄

[kingdonb]

Desired State
The aggregate of all configuration data for a system form its desired state

Is this correct? I think it should say "from" or "forms", not sure which. This is in GLOSSARY.md (probably should read "forms," right?)

I didn't find any other errors. I will PR this so you can merge it straight away if the correction is OK, and get on with 1.0.0 👍

(thumbs up from me, with that change!)

edit: "aggregate .. forms"

[dj1k]

Great job everyone, these look good to me! 👍

[scottrigby]

Thank you everyone! Will follow up with CNCF after 1.0.0 via #73