Agreed. "C/C++" as a term tends to be a crutch for cases where the author hasn't thought about the specifics of how their statement might apply differently to each language (much less the various versions and implementations of their specs) and would rather be vague than wrong (but is often both). "Both C and C++" (for exactly those two) or "C-family languages" (for C, C++, obj-C, at least, and as a more general term overall) are more often what people should be reaching for.
At the very least, the continued reinforcement of the myth that C++ is “just an extension” that sits on top of C really needs to stop. There is no real benefit from it and it can cause plenty of damage when developers incorrectly assume they have adequate knowledge from one of the two languages to be profficient in the other.