Update 2.1.0.md

Co-authored-by: Zoltán Lehóczky <[email protected]>

src/docs/releases/2.1.0.md

@@ -57,7 +57,7 @@ In the Roles feature, there were previously `AssignRoles` and `AssignRole_{RoleN
 To ensure a smooth transition, a migration step has been added. Any roles previously granted `AssignRoles` will now be automatically granted `AssignRoleToUsers`. Similarly, any roles with `AssignRole_{RoleName}` will now be granted the corresponding `AssignRoleToUsers_{RoleName}` permission.
 
 !!! warning
-    Please review all your recipes and replace occurrences of `AssignRoles` with `AssignRoleToUsers`, and `AssignRole_{RoleName}` with `AssignRoleToUsers_{RoleName}`.
+    Please review all your recipes and replace occurrences of `AssignRoles` with `AssignRoleToUsers`, and `AssignRole_{RoleName}` with `AssignRoleToUsers_{RoleName}`. Also note that since the `AssignRoles` permissions didn't actually work before, while this change fixes behavior and Orchard Core will now follow the intent of setting those permissions, it might be unexpected to see the restrictions governed by the be applied. Check if your administrators can still set what they should be able to.
 
 ### New **Azure Communication Services SMS** Feature