Is this issue happening on phoneparks.com? I double checked that URL, however, I wasn't able to replicate the error you're referencing above. If this is the store, then it looks like you may have already gotten this fixed up!
That said, in most cases, this error is caused by funky HTML coding or an app, however, it's hard to say without looking at the store directly. In the case that this is for a different store, or it's on certain products, then I'd be happy to take another look if you could post further details on the store, and the steps taken to replicate the error.