This week's book giveaway is in the OCAJP 8 forum. We're giving away four copies of OCA Java SE 8 Programmer I Study Guide and have Edward Finegan & Robert Liguori on-line! See this thread for details.
"Gotcha" isn't a formal term. It's a slang term for an easy-to-make mistake.
In a computer language, a gotcha is often an indication of a weakness in the design of the language. After all, one of the main design goals of most languages is clarity and a gotcha is an example of lack of clarity.
Java has far fewer gotchas than other languages. For instance, C++ has so many that there's a whole book (by Stephen C. Dewhurst) devoted to them.
A common gotcha for Java beginners is using == to compare Strings. You should use equals() method, of course. It's made even more of a gotcha by the interning of literal Strings, which means that == can sometimes seem to work for string comparisons.
Betty Rubble? Well, I would go with Betty... but I'd be thinking of Wilma.
If you want to learn about tricky constructs in Java and how to write good programs in Java, then I will highly recommend you the book Effective Java. Another interesting book with regard to this is Java Puzzlers.