Link release guidance from branch docs

Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>

Author: MariusStorhaug

docs/content/get-started/module-bootstrap.md

@@ -60,6 +60,6 @@ A module bootstrapped this way:
 ## When to use this
 
 - The module has no usable release yet, and the load-bearing core hasn't landed.
-- Use this only for the initial bootstrap. Once `main` has a first release, ongoing feature work targets `main` directly with ordinary topic branches, or a [stacked pull request](https://msx.no/docs/Ways-of-Working/Branching-and-Merging/#stacked-pull-requests) when changes genuinely depend on each other.
+- Use this only for the initial bootstrap. Once `main` has a first release, ongoing feature work targets `main` directly with ordinary topic branches, uses the [release branch pattern](../guides/versioning-and-releases.md#release-branch-pattern) to batch independent features, or uses a [stacked pull request](https://msx.no/docs/Ways-of-Working/Branching-and-Merging/#stacked-pull-requests) when changes genuinely depend on each other.
 
 For the general branching and merge model, see [MSX Branching and Merging](https://msx.no/docs/Ways-of-Working/Branching-and-Merging/).

docs/content/reference/powershell-module-standard.md

@@ -115,7 +115,9 @@ The release process treats each merged PR as a release on a single linear ancest
 
 ### Release and feature branches
 
-For large work, open a release branch and target it from feature branches. Apply the `Prerelease` label on the release branch PR to publish preview versions before the final merge to `main`.
+For large work, follow the [release branch pattern](../guides/versioning-and-releases.md#release-branch-pattern):
+open a release branch and target it from feature branches. Apply the `Prerelease` label on
+the release branch PR to publish preview versions before the final merge to `main`.
 
 ## CI/CD pipeline
 

docs/content/specification/principles-and-practices.md

@@ -14,7 +14,8 @@ patch.
 
 ## Release and feature branches
 
-If you need to work forth a bigger release, create a branch representing the release (a release branch) and open a PR towards `main` for this branch.
+If you need to work toward a bigger release, follow the [release branch pattern](../guides/versioning-and-releases.md#release-branch-pattern):
+create a branch representing the release and open a PR toward `main` for this branch.
 For each topic or feature to add to the release, open a new branch representing the feature (a feature branch) and open a PR towards the release
 branch. Optionally add the `Prerelease` label on the PR for the release branch, to release preview versions before merging and releasing a published
 version of the PowerShell module.