All that said, it might help to include a pretty graph of two branches and how a bug fix gets merged to both. It might not be simple to generate a good looking graph like that, but a visual image that demonstrates our merge strategy might get at what you are asking about.

Perhaps this is part of what @jdob was suggesting, but an example of what to do when there is a bug fix that needs to go to more than one branch might be handy, especially if presented graphically. My previous post was more about how, in my opinion, we don't need to educate the developers about git terminology.