Couple of thoughts on how a user would install content locally and how they could refresh content...

• For offline use, (or if your internet connection isn't as fast as you'd like), a user could choose to install an “SDK”... For example, the user could choose to install the Longhorn SDK, and they'd get all the related content locally.
• By default the SDK would always go to the local content (if it's available locally of course), and a background process would update the content so most of the time the local content is as upto date at the online content. If the content has not been downloaded by the user, the SDK would retrieve it from the MSDN website.
• The user could be viewing a specific page, and if they think it may be out of date (the background process hasn't got around to updating that page yet), but they want it updated NOW, they could click on the “Force a refresh” of this page button.
• The user could also choose to subscribe to a single piece of content instead of a whole SDK... for example I want to read the “parsing regular expressions” from the MSDN website and I could choose to take that piece of content offline (and also choose to mark it for synchronization each time the background process runs)

Thoughts? Do let me know by clicking the feedback button below!