It's not possible, or necessary, to know everything about everything
While we all try to keep up on the latest trends, cool technologies, hip terminology, it just isn't possible to cover all the bases and stay up-to-date across all of them, while also being effective at your job.
Some technologies really don't hang around long enough to be worth knowing about and others are still so nebulous that its' not clear what benefit they'll actually be.
I'll take a guess that this has come up because of one of three reasons:
1) The technical manager is trying to keep up with a clique of people who are playing some power games by using bleeding edge technology to make him (and maybe others) look out-of-touch. The best way to win this game is not to play - you can't possibly be 'cooler' than them, so don't even try. I actually caught a group of guys making up terminology to run rings around their team leader who was desperately trying to gel with them.
One way to nip this in the bud is to ask the people involved to explain what the technology is to the rest of the team and why it is useful/advantageous. It is not necessary for the TM to admit they don't know, just ask for the guys to include everyone else in their tech-speak discussions. If their use of the terminology is genuine, he'll get an explanation. If they were playing power games, this won't happen again.
2) The technical manager is actually out of his depth, treading water and desperately asking for help. A simple Google search would yield either a handful of blogs/forums or the programmers.stackexchange.com question asking for recommended list of blogs, like this question is. You can type the example terms into Wikipedia, for example, and follow some of the topic links to read around and pick up others.
That they've asked you to come up with this (and they couldn't) is a bit worrying.