I see @jdg26 has submitted the correction already:
Thanks!
For the benefit of anyone else with a similar question who finds this forum topic through their research, I will say that I think the best approach for getting changes made to the diagrams or images in the Arduino documentation is to just submit an issue to the arduino/docs-content repository and leave it for the Arduino documentation developers to implement the fix. They will have access to the source files for the diagrams and so will be able to easily make adjustments.
It is unfortunate that the source files are not available in the arduino/docs-content repository to make it easy for anyone to contribute directly.
The above advice is specific to diagrams and images. If you would like to make a correction or enhancement to the text content of the documentation, you are welcome to submit a pull request to make the change directly.
I also believe that KiCad is the best option for creating schematics in general. However, Arduino has a specific style for schematic diagrams included in the documentation and won't accept diagrams that don't conform to that style, so I don't think KiCad is an appropriate tool for this specific application (unless you are able to make the schematic produced by KiCad match the Arduino style).
That said, if you are proficient with schematic capture, you might find it useful to create a schematic to illustrate issues reporting an error or proposing an enhancement to a schematic in the documentation, even though that image won't actually be used in the published documentation.
Unfortunately I don't know. I don't have any involvement in that area. I would guess it is the responsibility of the design team.
If I was doing this for my own project I would traditionally use the open source Inkscape vector graphics editor. That said, lately I have moved toward just writing clean SVG code by hand for simple graphics.