Fix archors to mod_mam (was mod_mam_meta) in migrations

Author: arcusfelis

Diff for: doc/migrations/4.0.1_4.1.0.md

@@ -22,7 +22,7 @@ Since release 4.1.0, we are no longer supporting the `*.cfg` MongooseIM configur
 
 * [`mod_http_upload.max_file_size`](../modules/mod_http_upload.md#modulesmod_http_uploadmax_file_size): `undefined` is no longer allowed
 
-* [`mod_mam_meta.user_prefs_store`](../modules/mod_mam.md#modulesmod_mam_metauser_prefs_store): `false` is no longer allowed
+* [`mod_mam_meta.user_prefs_store`](../modules/mod_mam.md#modulesmod_mamuser_prefs_store): `false` is no longer allowed (note: the module is called `mod_mam` in the most recent versions)
 
 * [`mod_muc_light.config_schema`](../modules/mod_muc_light.md#modulesmod_muc_lightconfig_schema): the usage of `value` and `type` fields was replaced with one of the following fields: `string_value`, `integer_value` or `float_value`
 

Diff for: doc/migrations/4.1.0_4.2.0.md

@@ -23,7 +23,7 @@ ALTER TABLE inbox
 
 ### Archived groupchat messages in `mod_mam`
 
-The [`archive_groupchats`](../modules/mod_mam.md#modulesmod_mam_metapmarchive_groupchats) option is now set to `false` by default, as documented.
+The [`archive_groupchats`](../modules/mod_mam.md#modulesmod_mampmarchive_groupchats) option is now set to `false` by default, as documented.
 Before the change, the private message (PM) archive stored incoming groupchat messages as well, contrary to the documentation.
 After the upgrade you can manually remove those messages from the database.
 For example, when the MUC domain is `muc.localhost` and `rdbms_message_format` has the default value `internal`, one can remove such messages with the following query:

Diff for: doc/migrations/5.0.0_5.1.0.md

@@ -51,7 +51,7 @@ The rules for overriding global options in the `host_config` section have been s
 
 * `mod_auth_token` has a new configuration format - if you are using this module, amend the [`validity_period`](../modules/mod_auth_token.md#modulesmod_auth_tokenvalidity_period) option.
 * `mod_event_pusher` has an updated configuration format - the `backend` subsection is removed and the `http` backend has a new `handlers` option. Adjust your configuration according to [`mod_event_pusher`](../modules/mod_event_pusher.md) documentation.
-* `mod_mam_meta` does not have the `rdbms_message_format` and `simple` options anymore. Use [`db_jid_format`](../modules/mod_mam.md#modulesmod_mam_metadb_jid_format) and [`db_message_format`](../modules/mod_mam.md#modulesmod_mam_metadb_message_format) instead.
+* `mod_mam_meta` does not have the `rdbms_message_format` and `simple` options anymore. Use [`db_jid_format`](../modules/mod_mam.md#modulesmod_mamdb_jid_format) and [`db_message_format`](../modules/mod_mam.md#modulesmod_mamdb_message_format) instead. (note: the module is called `mod_mam` in the most recent versions).
 * `mod_shared_roster_ldap` all options have their `ldap_` prefix dropped.
 * `mod_vcard` LDAP options are moved into an LDAP subsection.