I actually brain-dumped a bunch about the issue of showing placeholder values [in the contributing guide](https://github.com/rackerlabs/developer.rackspace.com/blob/master/src/docs/CONTRIBUTING.rst#placeholders), with some discussion about the particulars in #200. By the guidelines I wrote there, this should be something like `{domainName}`, since we can't know what domain will actually work for the user.

More generally, though: as I see it, the solution to "people are copying and pasting without reading" isn't going to be "add more text." If they aren't watching what they're copying in the first place, they're likely to miss whatever notice we could come up with, too, and it'd just clutter the text for everyone else. Hell, I'm guilty of this myself plenty of times, on pages with big bold notices saying "replace these values with your own." Sometimes you're just trying to get something to work quickly without really being in "learning mode" and you slip up.

This is a universal problem for this kind of documentation and I have to say I have never seen a good solution for it. We could intercept the browser's copy event and do... something... that wouldn't be incredibly annoying? Use an active login cookie to show tailored values for the actual user, like your real API key? Flag placeholders that need special handling with a special CSS class and style them to stand out from the rest of the syntax highlighting?