@Scott-Hanselman Thanks for the heads up, we've fixed the link now. Sorry about the confusion!