# Terminology & Menu Items did not change with update?

**URL:** <https://forum.mautic.org/t/terminology-menu-items-did-not-change-with-update/6097>\
**Category:** Product Support\
**Created:** [October 5, 2016, 1:49pm UTC](https://forum.mautic.org/t/terminology-menu-items-did-not-change-with-update/6097 "2016-10-05T13:49:35Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![hughmacdonald](https://avatars.discourse-cdn.com/v4/letter/h/85f322/32.png) [@hughmacdonald](https://forum.mautic.org/u/hughmacdonald)\
**Post date:** [October 5, 2016, 1:49pm UTC](https://forum.mautic.org/t/terminology-menu-items-did-not-change-with-update/6097/1 "2016-10-05T13:49:35Z")

</div>

I updated our installation of Mautic from 1.3 to 1.4 earlier in the summer and just upgraded it again to 2.1.  
  
  
  
The terminology and menu item changes mentioned at the top of the 1.4 release notes do not seem to have occurred:  
  
  
  
[https://github.com/mautic/mautic/releases/tag/1.4.0](https://github.com/mautic/mautic/releases/tag/1.4.0)  
  
  
  
Each upgrade seemed to proceed normally and didn’t report any errors. Is this the expected behaviour, and if not, is there a database migration or something else that has not been processed that I can trigger?

---

<div class="post-metadata">

**Author:** ![hughmacdonald](https://avatars.discourse-cdn.com/v4/letter/h/85f322/32.png) [@hughmacdonald](https://forum.mautic.org/u/hughmacdonald)\
**Post date:** [October 5, 2016, 1:49pm UTC](https://forum.mautic.org/t/terminology-menu-items-did-not-change-with-update/6097/2 "2016-10-05T13:49:35Z")

</div>

I updated our installation of Mautic from 1.3 to 1.4 earlier in the summer and just upgraded it again to 2.1.

The terminology and menu item changes mentioned at the top of the 1.4 release notes do not seem to have occurred:

[https://github.com/mautic/mautic/releases/tag/1.4.0](https://github.com/mautic/mautic/releases/tag/1.4.0)

Each upgrade seemed to proceed normally and didn’t report any errors. Is this the expected behaviour, and if not, is there a database migration or something else that has not been processed that I can trigger?