From ec5464a6dc44e5a5b4d085b5f206b593c907a9af Mon Sep 17 00:00:00 2001 From: Igor Date: Tue, 19 Apr 2016 22:21:26 +1200 Subject: [PATCH] minor docs broken link --- docs/en/05_Contributing/01_Code.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/en/05_Contributing/01_Code.md b/docs/en/05_Contributing/01_Code.md index f4e8b6776..d083d5cdc 100644 --- a/docs/en/05_Contributing/01_Code.md +++ b/docs/en/05_Contributing/01_Code.md @@ -127,7 +127,7 @@ If you're familiar with it, here's the short version of what you need to know. O * **Choose the correct branch**: Assume the current release is 3.0.3, and 3.1.0 is in beta state. Most pull requests should go against the `3.1` *pre-release branch*, only critical bugfixes against the `3.0` *release branch*. If you're changing an API or introducing a major feature, -the pull request should go against `master` (read more about our [release process](release_process)). Branches are periodically merged "upwards" (3.0 into 3.1, 3.1 into master). +the pull request should go against `master` (read more about our [release process](03_Release_Process.md)). Branches are periodically merged "upwards" (3.0 into 3.1, 3.1 into master). ### Editing files directly on GitHub.com