Seriously though, if learning the meaning of two (three if you throw in grey hat) terms is too difficult, never mind the rest of the requisite knowledge to meaningfully participate, you may want to consider an alternate area of study.
Yeah, anything that boils down to "you don't need to know about X, you just need to know that white X is good and black X is bad" is not a great look for technical terminology in the current context.
There are countless words and idioms that will make no sense when you're not familiar with them. You could consider these annoying, or you could consider these the interesting parts of a language.
I for one very much like words with interesting history.
I'm aware that I'm moving the goalposts a little bit, or at least making them more explicit. Sorry? Just trying to voice explicitly why my (admittedly subjective) stylistic sense is going "Eh, this one is better off replaced by explicit terms".
If you can't figure out how to google white hat, how are you going to figure out what the FHBTYU (made up acronym) is in your tech stack?