Please be mindful that bonding is different from balancing.
Bonding is making one aggregate pipe out of multiple smaller pipes. For simplicity, I will refer to this as a “big pipe”. The deal with a big pipe is that it ONLY works if you have something on the other end of it. You can use a virtual machine in a cloud provided service. OR, you can place a Peplink device on an internet connection large enough to handle your big pipe.
Balancing is what you would most likely be doing in a home environment. That means things like - when this little pipe is at full load, start second traffic to pipe 2. Or, send all https traffic down this pipe and send all http down that one. OR, send all youtube stuff down WAN1, and send all Xbox connections down WAN2.
That being said, there are some scenarios where you can achieve a “big pipe” with just balancing. One example is to use a weighted balance on http traffic. Have even weights for each WAN set to 1, and then the http traffic will go one session per WAN. An Xbox makes 4 concurrent tcp sessions for large game downloads, so my end result is full capacity on both links for a single download. I have found that many large downloads use a similar strategy. Apple uses two for iOS downloads.
I hope this clears things up a bit. I don’t feel that there is any intentional misleading with the marketing. It is just dictionary terms that have similar meanings but are technically very different that can be difficult to decipher.