Nothing. This will go away when Google retests the page.
I went through some of this by the thousands. It has been since at least early May that all of the errors have been fixed, and still there is about 125 remaining as of this morning. It takes time of course, however, Google does say it is a priority to retest mobile pages. However, it may be that as you get to the end of your list, Google may slow down. At least that is the way is seems to be for me. I assume this is because of the pages relative importance. You may see that Googles regular spider has visited some of these pages before the mobility test. I experienced this. However, it does appear that the mobility test will occur one or more days after.
Since you have only a few, try submitting them using the Fetch as Google. That spider may not fix the problem, however, it may trigger the mobility test to follow soon after. Who knows for sure?
Incidentally, for what it is worth, while there are different spiders from Google, G admits that they are all the same spider with different intents. The advantage is this. If one of the media or mobility spiders visits your page, it is also the same as the regular spider visiting your page. The converse is also at least somewhat true if not entirely true. While the fetch comes from different places and processed specifically for the portion of the index that requested the fetch, the systems are designed to save bandwidth (both yours and theirs) and conserve requests by advantaging the other processes and indexes as well.
It will all work out okay.
Remember that search engines are notoriously slow.