[docs]: update comments for github_branch_protection in case of push_restrictions

Author: nickfloyd

website/docs/r/branch_protection.html.markdown

@@ -11,6 +11,8 @@ Protects a GitHub branch.
 
 This resource allows you to configure branch protection for repositories in your organization. When applied, the branch will be protected from forced pushes and deletion. Additional constraints, such as required status checks or restrictions on users, teams, and apps, can also be configured.
 
+Note: for the `push_restrictions` a given user or team must have specific write access to the repository. If specific write access not provided, github will reject the given actor, which will be the cause of terraform drift.
+
 ## Example Usage
 
 ```hcl
@@ -47,16 +49,19 @@ resource "github_branch_protection" "example" {
     data.github_user.example.node_id,
     "/exampleuser",
     "exampleorganization/exampleteam",
-    # limited to a list of one type of restriction (user, team, app)
+    # you can have more than one type of restriction (teams + users). If you use
+    # more than one type, you must use node_ids of each user and each team.
     # github_team.example.node_id
+    # github_user.example-2.node_id
   ]
 
   force_push_bypassers = [
     data.github_user.example.node_id,
     "/exampleuser",
     "exampleorganization/exampleteam",
-    # limited to a list of one type of restriction (user, team, app)
+    # you can have more than one type of restriction (teams + users)
     # github_team.example.node_id
+    # github_team.example-2.node_id
   ]
 
 }