Formatting fix.
Integrate text describing copyright holders.

The enforcement section now has an integrated paragraph describing how
enforcement relates to copyright, and refers back to a related section
much earlier in the tutorial.
Rework two compliance guide sections in Background

Some of the text pasted in earlier commits was certainly useful, but
needed a complete rework.

Also, the text pasted was far too terse, and more detail was needed.

Therefore, I've moved text around and build a more comprehensive
Background section.  I've moved the burgeoning "Understanding Who's
Enforcing" section into the Background chapter and made it complete.

Probably the most bizarre (?) change I've made here is coining this
acronym COGEO.  This is non-optimal for sure, and I've added a FIXME to
seek a better term.
Properly quote & characters.
Some rewording of this section, mostly wordsmith.
Remove problematic text.

After rereading this text a few times, I realized that it doesn't
actually say anything of value.  It looks pretty but is devoid of
meaning (or, less glibly, it doesn't express any concept not already
covered by other text in the tutorial), so I'm cutting it entirely.
Incorporate new text fully into this section.
This should say GPLv3 here.
Correct formatting on footnote.
Integrate these texts and provide additional links
Integrate short sentence.
Integrate short sentence into main text.
Integrate this text and rewrite to make it work.

Also creates some label for references back.
Add use of CEGEO term here as well.

I still find my CEGEO acronym cumbersome, but I might as well commit to
using it until a better one comes along.
Rewrite section to incorporate text properly.

Much of the existing pasted text had subtle condescension toward
developers, which I've cleaned up here.  Admittedly, I may have over
compensated  and added subtle condescension toward lawyers.
This may better appear here.
Link LGPL compliance section to LGPL analysis.

Since so little material is currently given on LGPL compliance, it's
likely best to link back to the chapter on LGPL compliance.

Besides, I don't think there really is anything additional the
compliance guide can add regarding LGPL compliance, other than the
detail license analysis on LGPL already available in that part of the
text.

(Note labels had to be added for the chapters that didn't previously
exist.)
Integrate this LGPL text properly.

Upon a more detailed reading, it's clear this pasted text belongs in the
LGPL license analysis section, but that in fact some other text was
needed to improve the end of the section on LGPL in the compliance
guide.
Correct and integrate this pasted paragraph.

Upon closer inspection, this pasted paragraph contained a clear error:
as written.  Specifically, it stated that compliance was automatic if
you merely "pass along" the CCS received from upstream.  It's IOTTMCO
that this is wrong.  I've corrected it and integrated the text.
Full rewrite of the new M&A compliance section.

Again, upon careful reading of the pasted text, it was clearly not
as useful as it first appeared, and is in fact somewhat misleading.

This rewrite does a better job explaining the necessary focus required
for an M&A situation.  The section could use some work, but generally
speaking IMO this new does a better job than both the pasted text and
other texts on the issues I've read elsewhere.