In some cases, geo-spatial or text indexes may have extra index entries. For geo-spatial indexes this can occur due to slight differences in accuracy of the trigonometric functions on the target. Such cases are benign and do not result in incorrect query results. 

The advice given in the result document for the validation command is unnecessarily alarmist and has unhelpful advice for recovery:

            "validateOutput": {
                "advice": "A corrupt namespace has been detected. See http://dochub.mongodb.org/core/data-recovery for recovery steps.",
                "corruptRecords": [],
                "errors": [
                    "Index with name '$**_text' has inconsistencies."
                ],
               ... }

The dochub link suggests initial sync or running MongoDB --repair, which is not actually needed or recommended. Instead recreating the index, or running the validate command with repair : true should likely be preferred. Also, we likely should have a different dochub link, as "recover data following unexpected shutdown" is something that dates back to when journaling was optional.