[docs] Fix migrated links

general/development/process/integration-review.md

@@ -104,7 +104,7 @@ During the continuous integration period (last 6 weeks before release) the integ
 
 Throughout:
 
-- Issues are picked on a one by one basis, prioritising [QA blockers](https://docs.moodle.org/dev/QA_testing#Resetting_tests) and master regressions (MUST FIX) issues.
+- Issues are picked on a one by one basis, prioritising [QA blockers](/general/development/process/testing/qa#resetting-tests) and master regressions (MUST FIX) issues.
 - After freeze (usually 5 weeks before release) any non bug fix issues are given the `integration_held` label and are explicitly not picked for integration. Still, anybody is able to add a reasoned `unhold_requested` label to those issues in order to get them unblocked by the development managers. Note this does not guarantee the issue to land before release, but just gives it a chance to be integrated like any other issue.
 - Also, coming together with freeze, all the flow of issues to current integration is automatically controlled by the [Manage queues on continuous](https://ci.moodle.org/view/Tracker/job/TR%20-%20Manage%20queues%20on%20continuous/) job that keeps the current queue fed with issues, moves important ones, holds new features and other niceties. Issues are picked in strict integration order.
 - Our goal is to achieve 'release-ability' throughout, so we stop integrating to ensure a release happens

general/development/process/peer-review.md

@@ -129,7 +129,7 @@ Ensure that:
 - `Sesskey` values are checked before all write actions where appropriate (some read actions as well);
 - Capabilities are checked where roles differ;
 - User inputs are properly escaped (eg the correct param type is used and risky types such as raw are only used where necessary and safe to do so); and
-- If the issue itself is a [security](https://docs.moodle.org/dev/security) issue, the [security process](https://docs.moodle.org/dev/Process#Security_issues) is being followed.
+- If the issue itself is a [security](https://docs.moodle.org/dev/security) issue, the [security process](/general/development/process#security-issues) is being followed.
   - Ensure that the fix is **not** available in a public repository (ie. a personal Github account); stand-alone patches should be provided instead.
   - The issue will not be integrated until just before the next minor version release.
 

general/development/process/testing/integrated-issues.md

@@ -86,7 +86,7 @@ as the very first command.
 
 :::tip
 
-Alternatively, you can also use [Moodle Development Kit (MDK)](https://docs.moodle.org/dev/Moodle_Development_kit), and add the option `--integration` to install a Moodle instance based on integration.git.
+Alternatively, you can also use [Moodle Development Kit (MDK)](/general/development/tools/mdk), and add the option `--integration` to install a Moodle instance based on integration.git.
 
 :::
 

general/development/process/testing/qa.md

@@ -254,5 +254,5 @@ Comments on tests from previous QA cycles:
 ## See also
 
 - [QA testing dashboard](https://tracker.moodle.org/secure/Dashboard.jspa?selectPageId=11454)
-- [Testing credits](https://docs.moodle.org/dev/Testing_credits)
+- [Testing credits](/general/community/credits/testing)
 - [Useful tips for QA testing](https://moodle.org/mod/forum/discuss.php?d=351302)