diff --git a/docs/modules/quickstarters/pages/release-manager.adoc b/docs/modules/quickstarters/pages/release-manager.adoc
index 2812d768d..3bb327c58 100644
--- a/docs/modules/quickstarters/pages/release-manager.adoc
+++ b/docs/modules/quickstarters/pages/release-manager.adoc
@@ -25,13 +25,12 @@ name: Project Phoenix
 
 repositories:
   - id: A
-    branch: master
   - id: B
     name: my-repo-B
-    branch: master
   - id: C
 ----
 
+For all repositories mentioned above (A, B, C) the library will resolve the default branch configured in each.
 If a named repository wants to announce a dependency on another repo, the dependency needs to be listed in that repository's `release-manager.yml`, simply by referring to its `repo.id` as defined in `metadata.yml`:
 
 ----
@@ -47,11 +46,9 @@ name: Project Phoenix
 
 repositories:
   - id: A
-    branch: master
     type: ods
   - id: B
     name: my-repo-B
-    branch: master
     type: ods
   - id: C
     type: ods
@@ -85,7 +82,6 @@ name: Project Phoenix
 repositories:
   - id: B
     name: my-repo-B
-    branch: master
 ----
 
 Assuming your release manager component's origin at `https://github.com/my-org/my-pipeline.git` in this example, the Git URL for repository `B` will resolve to `https://github.com/my-org/my-repo-B.git`, based on the value in `repositories[0].name`.
@@ -104,7 +100,7 @@ Assuming your release manager component's origin at `https://github.com/my-org/m
 
 === Automated Resolution of Repository Branch
 
-If no `branch` parameter is provided for a repository, `master` will be assumed.
+The default branch configured for the repository will be considered.
 
 === Automated Parallelization of Repositories