No, your rephrasing is completely orthogonal to what they're saying. Both are true. Seems like dishonest nitpicking to me to say that they obscure the difference between a gateway and a node.
Now if everyone accessed the content via a gateway, then sure - that undermines the point of IPFS. But a gateway isn't inherently bad, nor is it worse in most respects than a local node - at least, to my understanding.
ipfs companion is worthy of mention:
https://addons.mozilla.org/en-US/firefox/addon/ipfs-companio...
It converts ipfs.io to use your local resolver (amongst other cool things).
The content is being served by many peers on the network. You find the peers through a gateway - ipfs.io is one such gateway but any peer can also act as a gateway.
You lose most of the benefits of IPFS if you browse via a gateway controlled by somebody else.
You don't find peers through a gateway. A gateway is literally just an IPFS<->HTTP gateway. The gateway does all the IPFS stuff and just serves content to you over normal HTTP.
This is a strange way of saying "you're looking at this site through one centralised server hosted at ipfs.io".
Don't get me wrong, IPFS is great. I have released an application that works over IPFS. But I don't think obscuring the difference between a gateway and a node is beneficial. I think the difference needs to be highlighted front and centre, at least until we reach a point where every user is running an IPFS node without realising it.