Portions of the tor.1 man page and html doc formatted incorrectly

Some portions of the tor.1 doc don't join paragraphs correctly, leading to strange output styles, especially in html view, which appears to default to

 blocks when asciidoc is confused by the syntax.
Trac:

Username: jryans

changed milestone to %Tor: 0.3.0.x-final in legacy/trac

added component::core tor/tor in Legacy / Trac doc in Legacy / Trac man in Legacy / Trac milestone::Tor: 0.3.0.x-final in Legacy / Trac owner::jryans in Legacy / Trac priority::medium in Legacy / Trac reporter::jryans in Legacy / Trac resolution::fixed in Legacy / Trac review-group-14 in Legacy / Trac severity::normal in Legacy / Trac status::closed in Legacy / Trac type::defect in Legacy / Trac labels

Trac:
Username: jryans
Status: new to assigned
Owner: N/A to jryans

Patch available at https://github.com/jryans/tor/commits/doc-formatting.

Trac:
Username: jryans
Status: assigned to needs_review

Thanks jryans! Question:

Why SocksPortFlagsMisc and ExitPolicyDefault and ORPortFlagsExclusive don't show in the generated man page or HTML? So what are they for?

I'm asking because those could be confused with torrc option so I would be careful not to introduce section title that looks like such :S.

Trac:
Keywords: N/A deleted, man doc added
Status: needs_review to needs_information
Milestone: Tor: 0.3.??? to Tor: 0.3.0.x-final

Sorry, I should have explained that up front!

These "fake" sections were the only way I could see to have a paragraph be indented in the style of a first-level list item when it comes after a second-level / nested list item. All the other approaches I attempted led to the paragraph glued onto the content of the last second-level list item or formatted as a code sample, both of which are not what's intended. (There seems to be no explicit way to "end" the second-level list, so you have to find some way to trigger that implicitly. asciidoc is strange.)

I noticed there is a pre-existing usage of this technique with OtherSocksPortFlags. So anyway, these sections could really be named anything, since they don't appear in the output. Any suggestions for less confusing names, or do they seem okay?

Trac:
Username: jryans
Status: needs_information to needs_review

Maybe <X>Footer is a good name for these "hidden" sections?

Trac:
Username: jryans

Trac:
Keywords: man doc deleted, man, doc, review-group-14 added

This looks good to me. Merging; thanks!

Trac:
Resolution: N/A to fixed
Status: needs_review to closed

closed

mentioned in issue legacy/trac#25582 (moved)

moved from legacy/trac#20885 (moved)

added Bug label and removed 1 deleted label

added 1 deleted label and removed 1 deleted label

added Documentation label and removed 1 deleted label