Merge pull request #78939 from rolyon/rolyon-rbac-assignablescopes

[Azure RBAC] Update of AssignableScopes

Author: PRMerger14

articles/role-based-access-control/role-definitions.md

@@ -12,7 +12,7 @@ ms.devlang: na
 ms.topic: conceptual
 ms.tgt_pltfrm: na
 ms.workload: identity
-ms.date: 02/09/2019
+ms.date: 06/06/2019
 ms.author: rolyon
 ms.reviewer: bagovind
 ms.custom: 
@@ -211,7 +211,7 @@ The `NotDataActions` permission specifies the data operations that are excluded
 
 ## AssignableScopes
 
-The `AssignableScopes` property specifies the scopes (subscriptions, resource groups, or resources) that the role is available for assignment. You can make the role available for assignment in only the subscriptions or resource groups that require it, and not the clutter user experience for the rest of the subscriptions or resource groups. You must use at least one subscription, resource group, or resource ID.
+The `AssignableScopes` property specifies the scopes (subscriptions, resource groups, or resources) that have this role definition available. You can make the role available for assignment in only the subscriptions or resource groups that require it, and not clutter the user experience for the rest of the subscriptions or resource groups. You must use at least one subscription, resource group, or resource ID.
 
 Built-in roles have `AssignableScopes` set to the root scope (`"/"`). The root scope indicates that the role is available for assignment in all scopes. Examples of valid assignable scopes include: