fix UI bug

src/OrchardCore.Modules/OrchardCore.Roles/Views/Admin/Edit.cshtml

@@ -28,7 +28,7 @@
     {
         <div class="mb-3">
             <div class="form-check">
-                <input type="checkbox" class="form-check-input" asp-for="IsOwnerType" checked="@Model.IsOwnerType" role="button" />
+                <input type="checkbox" class="form-check-input" asp-for="IsOwnerType" checked="@Model.IsOwnerType" role="button" data-bs-toggle="collapse" data-bs-target="#Role_Permissions_Container" aria-expanded="@(Model.IsOwnerType ? "false" : "true")" aria-controls="Role_Permissions_Container" />
                 <label class="form-check-label" asp-for="IsOwnerType">@T["Site Owner?"]</label>
                 <span class="badge text-bg-danger">@T["Security Critical"]</span>
                 <span class="hint dashed">@T["Roles with the Owner type will automatically grant the user full access to all permissions."]</span>

src/docs/releases/2.1.0.md

@@ -74,6 +74,7 @@ A new `Type` property has been added to the `IRole` interface, and partially sur
 Furthermore, the `SiteOwner` permission has been deprecated and will be removed in future releases. To prevent any breaking changes, we've introduced a fast-track migration that automatically assigns the `Owner` role type to any role with the `SiteOwner` permission.
 
 Instead of authorizing against the `SiteOwner` permission, the Recipes feature now uses its own  Manage Recipes permission (which is automatically available for the Administrator role).
+
 !!! warning
     Please set the `Owner` type on roles instead of using the `SiteOwner` permission. The latter will be removed in a future version. Don't authorize against the `SiteOwner` permission in code.