The city in question: Relation: Mação, Penhascoso e Aboboreira (6458560) | OpenStreetMap
The city is called Mação, but for a long time it showed up on maps as Maçã, which is the Portuguese word for apple 
. I noticed it first in August, when it was appearing in both OSM and Strava as Maçã. I went to fix it in OSM but the name was correct there, nothing to fix in the feature marker, border, etc. Eventually at some point it has corrected in Strava and elsewhere, but in CS it persists with the missing ‘o’ for 4+ months now.
I am trying to update the city which would maybe fix it? But I thought that only has to do with streets…can’t do update anyways due to current processing load. Any ideas?
Mapbox handles the entire mapping display. I have no control over that whatsoever.
There’s an “Improve this map” link in the bottom right corner. They have an interactive contribution map that doesn’t seem to include city-level updates. 
That made me double-check, on Strava on mobile it’s Mação but on Strava on desktop it’s still Maçã, like CityStrides (missing the ‘o’ on desktop or mobile). I wonder why the map data source would differ for Strava…Well, I submitted a Mapbox ticket for it we’ll see if anything comes of it, thanks for pointing me in that direction.
I got an automated reply that my “feedback was resolved” but still appears without the ‘o’ on the map. They did mention it could take up to 14 days (seriously?) to see the change resolved on the map, so now we wait…
FWIW, the map (or rather, different parts thereof) is likely only regenerated every x timeframe, that’s pretty common practice. It’s generally not vital to keep track of minutely or daily changes. Generating the map is quite intensive compared to serving it (aka expensive) and generating one invalidates existing caches (also more expensive). It sounds likely to me they made a fix in whatever datastore they have and that data will eventually get used when the map is regenerated. Short of some serious vandalism sneaking in, I don’t see them intervening in the automated schedule for a typo.
I figured it might have something to do with cached versions. Still have no idea why no one bothered to fix it for 3+ months other than the fact it’s pretty rural, or how the error happened in the first place - may have something to do with the typo version being a common word in Portuguese as I mentioned. Damn you autocorrect.
4 days to go, still “Maçã” 
