OK. Not the shortest story but here goes....
We offered a recruit whose name is Shitta but the bad word filter wouldn't let that go through. I have it set to find anything with s-h-i-t and replace it with s#!t. So I had to go into the settings, disable that filter, change Shitta's name and re-enable the filter. While I was in there, there were a bunch of other filters that had been set up at different times in the past and I worked on getting them cleaned up. So I did some work so the filter is catching the combinations better - instead of having to have every possible iteration of f-u-c-k (f-u-c-k-e-r, f-u-c-k-i-n-g, etc.) it will find any time those four letters appear together and edit it so the actual word doesn't show up.
Where that came into play here is because at some point someone had set up a filter for the word g-o-o-k because of its potential use as a racial slur. Instead of having the system mask that as we do with cuss words, I had it hide that post until it can be approved because that's probably not acceptable in any context when used as a slur.
However, The Dude used "gobbledygook" and his post got flagged because g-o-o-k is a filtered word in any setting. So I just approved the post and we shold be good to go.
That's a long way of saying he's not on Mod Preview, just that post got flagged.
For reference, I set up n-i-g-g-e-r to do the same thing because someone had already set up that word to be masked but I changed it for the post to be hidden. That shouldn't show up the way g-o-o-k did for The Dude (obviously).