more automated upgrades

docs/features/core/admin_site.md

@@ -10,11 +10,9 @@ You can open the admin site by clicking on "Admin" in the drop down menu for a u
 
 For small to medium size alliances it is often sufficient to have no more then two superuser admins (admins that also are superusers). Having two admins usually makes sense, so you can have one primary and one backup.
 
-```{eval-rst}
-.. warning::
+:::{warning}
     Superusers have read & write access to everything on your AA installation. Superusers also automatically have all permissions and therefore access to all features of your apps. Therefore we recommend to be very careful to whom you give superuser privileges.
-```
-
+:::
 ## Setup for large installations
 
 For large alliances and coalitions you may want to have a couple of administrators to be able to distribute and handle the work load. However, having a larger number of superusers may be a security concern.
@@ -41,10 +39,9 @@ To create a staff admin you need to do two things:
 Access to the admin site is restricted. Users needs to have the `is_staff` property to be able to open the site at all. The superuser that is created during the installation
 process will automatically have access to the admin site.
 
-```{eval-rst}
-.. hint::
+:::{hint}
     Without any permissions a "staff user" can open the admin site, but can neither view nor edit anything except for viewing the list of permissions.
-```
+:::
 
 ### Permissions for common admin tasks
 

docs/features/core/index.md

@@ -2,7 +2,7 @@
 
 Managing access to applications and services is one of the core functions of **Alliance Auth**. The related key concepts and functionalities are describes in this section.
 
-```{toctree}
+:::{toctree}
 :maxdepth: 1
 
 dashboard
@@ -11,4 +11,4 @@ groups
 analytics
 notifications
 admin_site
-```
+:::