Skip to content

Commit adae6c4

Browse files
authored
Merge pull request #30148 from robotjellyzone/fixingSkew
Fixing Skew in localization doc
2 parents 4ecb2fd + 2fbb744 commit adae6c4

File tree

1 file changed

+2
-3
lines changed

1 file changed

+2
-3
lines changed

content/en/docs/contribute/localization.md

Lines changed: 2 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -346,7 +346,7 @@ Teams must merge localized content into the same branch from which the content w
346346

347347
For example:
348348
- a localization branch sourced from `main` must be merged into `main`.
349-
- a localization branch sourced from `release-{{ skew "prevMinorVersion" }}` must be merged into `release-{{ skew "prevMinorVersion" }}`.
349+
- a localization branch sourced from `release-{{% skew "prevMinorVersion" %}}` must be merged into `release-{{% skew "prevMinorVersion" %}}`.
350350

351351
{{< note >}}
352352
If your localization branch was created from `main` branch but it is not merged into `main` before new release branch `{{< release-branch >}}` created, merge it into both `main` and new release branch `{{< release-branch >}}`. To merge your localization branch into new release branch `{{< release-branch >}}`, you need to switch upstream branch of your localization branch to `{{< release-branch >}}`.
@@ -361,5 +361,4 @@ For more information about working from forks or directly from the repository, s
361361
## Upstream contributions
362362

363363
SIG Docs welcomes upstream contributions and corrections to the English source.
364-
365-
364+

0 commit comments

Comments
 (0)