Hi, @camerondurham, and thanks for the PR! :) I've taken your suggestions, with the exception of commenting out the ellipses. Across my docs, I have a number of cases where I show a small piece of source code and then successively build that up over the course of a number of listings. In so doing, in each listing I show only the deltas, and I include enough context to make it clear where the reader should add the delta to their own project. I don't, of course, repeat the entire previous listing + delta. That would take up too much space, and would make it harder to identify the delta. Any "delta" listing isn't meant to compile on its own, so it's not meant to be copy-pasted in its entirety into an entire source code file. The reader can of course use the Copy affordance, if that's convenient. But in many cases it's easier just to select-copy the delta and paste that in to the right place.

Anyway, consequently, to remain consistent with the practice described above (which I use in several places in the C++/WinRT docs), I've set the ellipses back to their sans comment syntax form. Remember that those ellipses are not meant to be source code (which the comment might imply) any more than an ellipsis in a passage of English is meant to be English. In both cases (source code or human language), rather, they're meant to indicate that something has been intentionally elided (with enough context to be clear exactly what has been elided).

Thanks!
Steve