[setq]

Most of the documentation is boilerplate. There's very little real content now and most of it is filler.

[wfunction]

Here's an example of a new API they added recently (the first one I thought of): https://msdn.microsoft.com/en-us/library/windows/desktop/mt5...

It says things like this:

> Indicates that the data for the file should be obtained from a WIM file. On access, data is transparently extracted from the WIM file and provided to applications. If the file contents are modified, data is transparently decompressed and the file is restored to the same physical form it had if this API were not used.

This is "boilerplate" and "very little content" to you? What are you thinking of?

[setq]

To be fair Win32 isn't terrible. Have you looked at the .Net docs?

http://imgur.com/a/iK4uG

[wfunction]

I haven't to be honest, but at the same time I'm not sure what you expect to see as the summary here. Is there anything profound to say about two overloads that differ by an extra "millisecond" parameter?

[krallja]

You need to click on the overload of this method that you are interested in. This is just the top level "where do you want to go?" document.

[setq]

It's not. There's a content about 11 screens down, not that you'd find it easily.

[darklajid]

Again, GP just stated that these are local links, links to anchors on that very same page, explaining the overloads.

Are there too many? For this class, maybe. It's at least potentially worth discussing it. But the way the navigation works isn't "just scroll until something seems to fit".