Thanks for your comment. We're resolving this issue, will update the post, and include full and clear attribution.