I just want to add one thing. In the 'family' parameter, you should always include all styles and weights (i.e. italics and bold) that you will use in your CSS - just as you, Jake, did with including weights 400 and 600.
Otherwise the font rendering in browsers will lead to ugly looking 'faux bolds'. On A List Apart http://www.alistapart.com/articles/say-no-to-faux-bold/ you can read: "If text is styled as bold or italic and the typeface family does not include a bold or italic font, browsers will compensate by trying to create bold and italic styles themselves."
I just want to add one thing. In the 'family' parameter, you should always include all styles and weights (i.e. italics and bold) that you will use in your CSS - just as you, Jake, did with including weights 400 and 600.
Otherwise the font rendering in browsers will lead to ugly looking 'faux bolds'. On A List Apart http://www.alistapart.com/articles/say-no-to-faux-bold/ you can read: "If text is styled as bold or italic and the typeface family does not include a bold or italic font, browsers will compensate by trying to create bold and italic styles themselves."
I think this can more often be seen on IOS devices. Some people even thought it was an iPhone rendering bug http://stackoverflow.com/questions/.. ..2/ios-4-2-webfont-ttf-s-bold-font-weight-rendering-bug/.
And another article from Smashing Magazine http://www.smashingmagazine.com/2012/07/11/avoiding-faux-weights-styles-google-web-fonts/.