The ToC needs to have links to the *files* and that determines the
location of the article in the overall document structure.

Do not confuse this with internal reference *links* that are based on
the names. Although links get made if the ToC isn't hidden, that isn't
the way to create the references in the ToC.

Refer to docs/docs.beagleboard.io!105

The "expansion" section is meant to be about how to *build* expansion
hardware. This is where we provide information about what we expect
people to do when building add-on hardware, not about telling people how
to use it. They can infer how to use it, but that should really be
broken down into the "quick start", "design" and "demos" sections.

docs/docs.beagleboard.io!105

docs/docs.beagleboard.io!105

docs/docs.beagleboard.io!105

Helping out a little bit with docs/docs.beagleboard.io!105

Still need to move to sub-sections

Small Spelling and Flow Changes

See merge request docs/docs.beagleboard.io!103

Docs updates - chapter restructuring, images, and more

See merge request docs/docs.beagleboard.io!89