Ah, I see. What could be happening is when the profile is created in Ancestry.com (or another program) there is an "auto" add or correct (or suggest) function for the place names. I know in the software I use, it wants to geographically identify the place name, and it uses only modern ones. So every entry that I have for St. John Horsleydown, for instance, shows up as an error. If I want to geo-correct it, I have to change the name to St. Olave. But if I didn't know that was the new name of that area, I might choose something completely different, like, for example, Long Island City - which to someone thousands of miles away, may well seem like a reasonable modern day name for Long Island. That's my guess, anyway.
If you have evidence for the location that contradicts the original, by all means correct the place name and document your source.
And have fun!