I’m going to post this here and trust someone to move it if need be.

Comment Time Interval
This setting defines the amount of time that must lapse between comment postings. A malicious user will have to wait until the time has lapsed before being able to post again.
The setting is located at: Admin > Weblog Management > Edit Preferences > Comment Time Interval

Under my Admin there is no “Weblog Management”, so I clicked “Weblog Administration”, which is the closest there is. And under this there is indeed a “Weblog Management”, and under this, an “edit preferences” but no “Comment Time Interval.” There is a “Comment Posting Preferences,” and yes, this has the settings I was looking for, but not at all where I would look if I was trying to get there following the documentation.

Downloading ExpressionEngine.com Lists
EllisLab, Inc. maintains its own Blacklist and Whitelist, which are available for licensed purchasers of ExpressionEngine. These lists are maintained with the help of our users. If you have an item that you believe should be added to the Blacklist or Whitelist, please email blacklist@pmachine.com.

To download the ExpressionEngine Lists, you must have your License Number entered into the Admin > General Configuration area of the Control Panel. To download the Lists, go into the Modules > Blacklist. In the main menu for the module are links that you can click to automatically download and add the pMachine.com Lists to your own.

Again, not where the docs say it’s supposed to be. Is Admin > System Preferences > General Configuration

And the header calls it an ExpressionEngine.com Lists, while the paragraph below the header a pMachine.com Lists.

Writing Blacklist to .htaccess File
...
In order to include this “override” you need to ensure that your “Cookie Domain” preference is set under Admin > Cookie Settings.

Again, Admin > System Preferences > General Configuration. Oh, if only there were such a thing as find and replace.

I would also like to suggest that someone make a documentation section in the forums. I’ve sen typos reported in the “bugs” section. And with the forthcoming 2.0 having quickly corrected docs would be pretty handy.

For the record, I can usually figure it out, but I really could also hammer on the docs all day.

[Mod edit: moved to Bug forum]

Greetings Christopher,

Thank you for the report, I will be taking a look and correcting these issues.

Well, honestly, these were just the first ones I bothered to report, and these were found pretty quickly. I was going to make a post offering to trade 100 typo corrections for a free EE 2.0 license (but this would have required another 97 more and probably a weekend’s worth of time).

Part of me feels that since EE 2.0 is coming out anyway, it doesn’t matter that much, but since A. 2.0 is not out, and B. the 1.6 branch isn’t going away right away, then it’s still worth correcting.

Besides, some of the errors seem pretty consistent. Like the whole lack of System Preferences in some of the paths.

I was having a bad spam morning when I posted this, so was already frustrated by the time I got around to consulting the docs.

Does seem weird to me to put what amount to typos into a bug report. Documentation and corrections should have their own thread (in my opinion, but then I am opinionated). I realize stuff gets moved, added, etc., so staying on top of the docs probably takes a lot.

Thanks for clearing them up.

I’ve seen issues with the breadcrumb cut and paste items aren’t always showing a real breadcrumb when you look via the CP.

When I post instructions, I try to copy and paste from the CP’s breadcrumb.

Hopefully we can make sure that the breadcrumbs reflect the real steps to take.

No problems with you posting typos—I’m usually the person finding them.

The breadcrumb links aren’t always 1:1 with the path you’d take to click to a link though, which is just the nature of some of 1.x’s control panel since some of the mouseclicks are on the same page.

If the docs were in a wiki, then experienced users could add links and rewrite or flag problematic places. Administrators would be
notified of changes and could roll them back if necessary. (Comments at bottom of page are maybe overlooked by many…) 
This is a feature request rather than a bug

Our documentation fairies get notifications on every user guide comment, and if there’s an error or something to clarify, we do so.  And besides, have you seen the quality of community managed documentation via a wiki?  ::shudder::

The existing wiki and the documentation are separate entities.
I was suggesting that maybe the documentation could be more easily maintained and enhanced
if it were a wiki—this would make it less of a hassle for experienced users to cross-link stuff.
Explanatory links on a wiki (in a location where they belong) are less easy to overlook
than comments at the bottom of the page in the present docs.
For example “formatting button toolbar” is mentioned on the Stand-Alone Entry Form page,
but a beginner has to do a search to find what this is.
If the documentation were a wiki, all such terms/references could be easily linked/cross referenced
to relevant pages.

Also it’s easier to add links to relevant forum posts from the wiki than from the present docs,
and to cross-reference related stuff.

I didn’t suggest “community managed”—the present wiki is not “community managed”.
(Inexperienced users can’t post on the wiki or comment on the document pages).

Just a point of clarification, all registered users can post to the wiki.

I have seen one example where wiki documentation worked well.

They had two sets of docs, the open wiki ones, and a closed off set. Changes that made sense were reflected into the main docs, the ones that the owners disagreed with were either reverted, or if people clamored enough, or revised them enough, they were eventually adopted.

This said, I almost always referenced the mains docs.

Housecleaning coming through.  I’m going to go ahead and close this one out as conversation has tapered off.  (Good discussion, though.)