Apply suggestions from code review

Thanks @mattkasa

Co-authored-by: Matt Kasa <[email protected]>

Author: willianpaixao

docs/data-sources/user.md

@@ -29,7 +29,7 @@ The following arguments are supported:
 
 * `user_id` - (Optional) The ID of the user.
 
-> **Note**: only one of email, user_id or username must be provided.
+-> **Note** Only one of email, user_id, or username must be provided.
 
 ## Attributes Reference
 
@@ -85,5 +85,4 @@ The following arguments are supported:
 
 * `current_sign_in_at` - Current user's sign-in date.
 
-> **Note**: some attributes might not be returned depending on if you're an admin or not. Please refer to [Gitlab documentation](https://docs.gitlab.com/ce/api/users.html#single-user) for more details.
-
+-> **Note** Some attributes might not be returned depending on if you're an admin or not. Please refer to [Gitlab documentation](https://docs.gitlab.com/ce/api/users.html#single-user) for more details.

docs/resources/branch_protection.md

@@ -2,7 +2,7 @@
 
 This resource allows you to protect a specific branch by an access level so that the user with less access level cannot Merge/Push to the branch.
 
--> **NOTE**: The `allowed_to_push`, `allowed_to_merge` and `code_owner_approval_required` arguments require a GitLab Premium account or above.  Please refer to [Gitlab API documentation](https://docs.gitlab.com/ee/api/protected_branches.html) for further information.
+-> **Note** The `allowed_to_push`, `allowed_to_merge` and `code_owner_approval_required` arguments require a GitLab Premium account or above.  Please refer to [Gitlab API documentation](https://docs.gitlab.com/ee/api/protected_branches.html) for further information.
 
 ## Example Usage