Your cut points between summaries and full articles often fall at awkward points. Most notably, don't put them right after a sentence that ends in a ':'; instead, write the summary to stand alone. For instance, your declspec summary ought to end with something like "Read on for examples of when you might want to use declspec instead of auto.", and your summary of the new random bits should end with something like "C++11 adds a new object-oriented random number generator with many enhancements over the C library version."
Your article tags seem rather redundant to be as prominent as they are; every article has the "C++", "C++11", and "Programming" tags.
In your shared_ptr example, you should talk about when you might need to actually take away the reference from the shared_ptr, so that it outlives the shared_ptr.
Some feedback:
Your cut points between summaries and full articles often fall at awkward points. Most notably, don't put them right after a sentence that ends in a ':'; instead, write the summary to stand alone. For instance, your declspec summary ought to end with something like "Read on for examples of when you might want to use declspec instead of auto.", and your summary of the new random bits should end with something like "C++11 adds a new object-oriented random number generator with many enhancements over the C library version."
Your article tags seem rather redundant to be as prominent as they are; every article has the "C++", "C++11", and "Programming" tags.
In your shared_ptr example, you should talk about when you might need to actually take away the reference from the shared_ptr, so that it outlives the shared_ptr.