[2] no money involved.
The point seems to be, that for this case, the GPL should allow
the "distributing" to take place, since it is not doing any harm;
Due to [1], the ["un-modified"] source code, "has" to be available
from someone else (whoever created the current version, by
making the last change); so, no problem there.
...although, the recipient of the software, might have some
confusion (well, some ignorance) regarding how to get the
source code. But actually, come to think of it, that's where
software revision "version identifiers" (being annunciated
when the binary program is getting executed) could come
in handy. They are intended for (well, at least one of their
purposes, is:) achieving just such a goal -- avoiding
confusion about which version of software, is being run.
In the example that they gave near the end of "page 4",
it was clear that the person to whom the software was being distributed, was not technically adept enough to compile
things on his own; but if they have the version number,
and the URL from which the source code can be downloaded,
then maybe they *are* being provided, (effectively), the ability
to obtain the source code. Hmmm...
and as for [2], I forgot why [2] makes any difference; but it
was present in the example they gave near the end of page 4,
(at least I thought it was; or was I just reading something "in"
to the story, that was not actually written there?)
...so I just assumed that it [2] was relevant, and was not just
thrown in there to confuse things.
(hmm... does [2] matter? and if so, why?)