This bug has been taken care of the the correct information should be showing as of patch 1.22a. Thanks for the post!