[docs] moodleapp/release-process: Improve texts on page

docs/moodleapp/development/release-process.md

@@ -7,7 +7,7 @@ tags:
   - Release notes
 ---
 
-## Two weeks before (Code freeze)
+## Six weeks before (Code freeze)
 
 | **#** | **Task** | **Responsibility** |
 |---|---|---|
@@ -18,15 +18,15 @@ tags:
 | 5. | Add the release notes in the release issue created (search for the [release_notes tag](https://tracker.moodle.org/issues/?jql=project%20%3D%20MOBILE%20AND%20labels%20%3D%20release_notes)). Ask someone from the documentation team or Martin to review the release notes. | Integration Lead |
 | 6. | Contact the marketing team announcing the new release and highlights. | Integration Lead |
 | 7. | Add new QA tests to the "Testing cases" document. New QA tests should be labeled with [qa_test_required](https://tracker.moodle.org/issues/?jql=project%20%3D%20MOBILE%20AND%20resolution%20in%20(Unresolved%2C%20Fixed)%20AND%20labels%20%3D%20qa_test_required%20ORDER%20BY%20priority%20DESC%2C%20updated%20DESC). Remove that label once are added to the document. | Tester |
-| 8. | Run npm audit to ensure all the dependencies are OK. | Developer |
+| 8. | Run `npm audit` to ensure all the dependencies are OK and check github vulnerabilities report. | Developer |
 | 9. | Freeze Cordova plugins and Javascript libraries versions (node modules) in the integration branch. | Developer |
 | 10. | **Start testing** | Tester |
 
 ## The release day
 
 | **#** | **Task** | **Responsibility** |
 |---|---|---|
-| 1. | Fix the version name in integration:config.xml, integration:package.json and integration:src/config.json (remove the -dev). | Integration Lead |
+| 1. | Fix the version name in `integration:config.xml`, `integration:package.json` and `integration:moodle.config.json` (remove the `-dev`). | Integration Lead |
 | 2. | Integrate the [integration branch onto the master one](https://github.com/moodlehq/moodleapp/compare/master...integration). | Integration Lead |
 | 3. | Do some testing with the production builds before sending the application to the stores (overall testing to see that nothing is broken because of the branch merge done in step 2): <ul><li>Correct definitive version name displayed (and commit)</li><li>AOT compiling worked</li><li>Language strings synchronised from lang.moodle.net</li><li>New language packs added</li></ul> | All the team |
 | 4. | Send the applications to the stores for review. | Integration Lead |
@@ -42,7 +42,7 @@ tags:
 | 2. | Post in moodle.org/news. | Team Lead |
 | 3. | Review the users and developers documentation (check that everything is in order). Review the [docs_required and dev_docs_required_tags](https://tracker.moodle.org/issues/?jql=project%20%3D%20MOBILE%20AND%20labels%20in%20%28docs_required%2C%20dev_docs_required%29). Review the [Mobile features wiki documentation](https://docs.moodle.org/en/Moodle_Mobile_features). | All the team |
 | 4. | Delete the integration and desktop branches and create it again based on master. | Team Lead |
-| 5. | Bump version numbers in the following files in the integration branch: config.xml, src/config.json (appending a -dev to the versionname field to indicate that is a development version), package.json. | Integration Lead |
+| 5. | Bump version numbers in the following files in the integration branch: `config.xml` (version), `package.json` (version), `moodle.config.json` (versionname) appending a `-dev` to indicate that is a development version). | Integration Lead |
 | 6. | Unfreeze Cordova plugins and Javascript libraries versions (node modules). | Developer |
 | 7. | Check that the [Docker image](https://cloud.docker.com/u/moodlehq/repository/docker/moodlehq/moodleapp/general) for the new version was successfully built. | Integration Lead |
 | 8. | Update of the [local_moodlemobileapp](https://moodle.org/plugins/view.php?id=997) plugin (as final release) in moodle.org/plugins. | Developer |