"Asynchronous Programming With Twisted" says that reactor.run and reactor.stop are "not usual" but don't explain what is

[radix]

First of all, they *are* usual - they're the usual ways to manage the reactor if you're using the reactor API to do it. I *assume* the document is talking about 'twistd', but it doesn't mention the tool once in the entire document.

Either these assertions need to be qualified with an explanation of twistd, or they should be removed entirely.

[cary]

I rephrased these comments. Attempting to explain twistd in this context would probably confuse folks.

[glyph]

Please wrap the comments to 80 columns; in examples, it's even more important than usual, since preformatted text tends to run off the margin of a browser pretty easily.

I think it would also be helpful to add a reference to the Twisted plugins system to the 'see also' at the bottom of the document, explaining that larger programs typically do not call reactor.run themselves.

You might also want to have a look at the work that has gone into #1490, which might help to obviate the need for reactor.run all over the place in example code.