diff --git a/.github/actions/graformer/action.yaml b/.github/actions/graformer/action.yaml
index a9fb025..d4c63bc 100644
--- a/.github/actions/graformer/action.yaml
+++ b/.github/actions/graformer/action.yaml
@@ -112,6 +112,8 @@ runs:
               return `${resourceChange.type} :: ${actualChange.repository}/${actualChange.name}`
             }else if(resourceChange.type === 'github_repository_collaborator'){
               return `${resourceChange.type} :: ${actualChange.repository}/${actualChange.username}`
+            }else if(resourceChange.type === 'github_branch'){
+              return `${resourceChange.type} :: ${actualChange.repository}/${actualChange.branch}`
             }else if(resourceChange.type === 'github_branch_default'){
               return `${resourceChange.type} :: ${actualChange.repository}/${actualChange.branch}`
             }else if(resourceChange.type === 'github_team_repository'){
diff --git a/docs/renaming-teams-and-members.md b/docs/renaming-teams-and-members.md
index c4edb18..fff5003 100644
--- a/docs/renaming-teams-and-members.md
+++ b/docs/renaming-teams-and-members.md
@@ -103,7 +103,7 @@ Terraform plan: 0 to import, 0 to add, 1 to change, 0 to destroy.
 with a `Resources to update:` section and **no** `Resources to recreate:` section. The plan job counts recreates into both the add and the destroy totals, so `0 to destroy` is the check that matters.
 
 > [!NOTE]
-> Organisation resources have no display-name mapping in the plan summary, so they render as `unknown type github_team. resource address: github_team.team["New Name"]`. That is expected, not a failure.
+> Organisation resources render in the plan summary with a display name, e.g. `github_team :: New Name` and `github_team_membership :: alice/New Name (maintainer)`.
 
 Merge PR 1. The apply renames the team on GitHub and its slug becomes `new-slug`.