Pages that have URLs beginning with http://code.google.com/chrome/extensions are served from files in the Chromium source repository. Four versions of the doc exist at all times—stable (default), beta, dev, and trunk—corresponding to the three Windows release channels of Google Chrome plus the tip-of-tree Chromium source code (which is closer to the Canary build).
The following figure shows how the extension doc server takes a request for a URL such as http://code.google.com/chrome/extensions/docs.html, gets the corresponding file from the Chromium source repository, and then delivers it to the browser.
By default, the doc server delivers files corresponding to the current Windows stable channel release. You can find the release branch by going to https://omahaproxy.appspot.com/viewer and looking at the tuple after "win stable". As I write this page, the tuple is 13.0.782.215, which means that the stable Windows branch (for Chrome 13) is 782. The upshot? The doc server currently gets the source for http://code.google.com/chrome/extensions/docs.html from http://src.chromium.org/viewvc/chrome/branches/782/src/chrome/common/extensions/docs/docs.html.
You can get different versions of the doc by adding "/beta", "/dev", or "/trunk" to the URL, after "/extensions". For example, specifying http://code.google.com/chrome/extensions/trunk/docs.html gives you the content of http://src.chromium.org/viewvc/chrome/trunk/src/chrome/common/extensions/docs/docs.html.
Here's an easy way to see where doc files are served from.
For Developers > Design Documents > Extensions > How the Extension System Works > Extension Documentation System >