If updates were made but you still cannot see them, caching is often the reason.
This is one of the most common website frustrations: a change has been made, but the website still looks old.
Most of the time, the cause is cache. Caching helps websites load faster by storing saved versions of files, but it can also make old content appear even after an update has gone live.
There are several layers where this can happen. Your browser may still be loading a saved version. The website server may be caching old content. A CDN or performance tool may also be serving an older version to visitors.
That is why the site may look updated to one person but unchanged to another.
A hard refresh can sometimes solve it quickly. Testing in another browser or private window is also useful. If the change appears there, the site is probably updated correctly and the issue is local cache.
If the issue continues across multiple devices and browsers, then it may be more than cache. The update may not have deployed properly, or the wrong page or file may have been edited.
If you contact us, say exactly what change you expected to see, where you expected to see it, and whether you checked from another device or browser. That helps distinguish between a display delay and a real deployment problem.