This table is not relevant for several install methods (Vagrant/Docker/Generic).

For Ubuntu/Debian, I think it's useful information, but it's a bit
overwhelming, and what we're basically doing is elaborating on a couple
words (*it needs to be a __recent__, supported version of Ubuntu/Debian -
which is specifically yadda yadda...*).

If one is oblivious to this content and runs the install script on an
unsupported version of Ubuntu/Debian, that should be safe -- since the first
thing it does is to verify compatibility.

Note: not trying to bury - the next commit will call this out a bit more.

This makes the new section match the other sections.

corrected extension name

The extension name is just `myextension`, not `com.example.myextension`.

See https://chat.civicrm.org/civicrm/channels/dev-newcomers

Add documentation about how to  migrate off transact api

I think this is more accurate on what Payment api does - note I can't…

Co-Authored-By: Mikey O'Toole <mikey@mjco.uk>

Co-Authored-By: Mikey O'Toole <mikey@mjco.uk>

Co-Authored-By: Mikey O'Toole <mikey@mjco.uk>

Add information about api4 changes

Co-Authored-By: Mikey O'Toole <mikey@mjco.uk>

Copy editing on Order api

Update custom data for apiv4 mentioning the class used for OOP coding…

API - Add redirects for relocated APIv3 pages

These pages were moved (e.g.  03b42ee6).
Add corresponding redirects.

Co-Authored-By: Mikey O'Toole <mikey@mjco.uk>

I just read the first part & believe this edit makes it more succinct & clearer

Update Order docs to reflect https://github.com/civicrm/civicrm-core/…

Update custom data for apiv4 mentioning the class used for OOP coding format for Multi Record Custom data sets

Add in documentation on APIv4 and Custom Data