From daa2c4718d82cbf0ed9bd4c28f1de3f7cefc8537 Mon Sep 17 00:00:00 2001 From: Tim Bannister Date: Wed, 11 Nov 2020 23:34:37 +0000 Subject: [PATCH] Fix branch name advice Fixup for commit 28c8c2e9b2059612d87b623b06415b041bbf31af --- content/en/docs/contribute/new-content/overview.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/en/docs/contribute/new-content/overview.md b/content/en/docs/contribute/new-content/overview.md index 3cba9e434e..a7c6ab083e 100644 --- a/content/en/docs/contribute/new-content/overview.md +++ b/content/en/docs/contribute/new-content/overview.md @@ -43,7 +43,7 @@ When opening a pull request, you need to know in advance which branch to base yo Scenario | Branch :---------|:------------ Existing or new English language content for the current release | `master` -Content for a feature change release | The branch which corresponds to the major and minor version the feature change is in, using the pattern `dev-`. For example, if a feature changes in the `{{< latest-version >}}` release, then add documentation changes to the ``dev-{{< latest-version >}}`` branch. +Content for a feature change release | The branch which corresponds to the major and minor version the feature change is in, using the pattern `dev-`. For example, if a feature changes in the `v{{< skew nextMinorVersion >}}` release, then add documentation changes to the ``dev-{{< skew nextMinorVersion >}}`` branch. Content in other languages (localizations) | Use the localization's convention. See the [Localization branching strategy](/docs/contribute/localization/#branching-strategy) for more information.