find and replace fixes, will introduce errors

docs/features/core/admin_site.md

@@ -10,7 +10,7 @@ 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
+```{eval-rst}
 .. 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.
 ```
@@ -26,8 +26,7 @@ To create a staff admin you need to do two things:
 1. Enable the `is_staff` property for a user
 1. Give the user permissions for admin tasks
 
-```eval_rst
-.. note::
+:::{note}
     Note that staff admins have the following limitations:
 
     - Can not promote users to staff
@@ -42,7 +41,7 @@ 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
+```{eval-rst}
 .. 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.
 ```

docs/features/core/analytics.md

@@ -64,7 +64,7 @@ This data is stored in a Team Google Analytics Dashboard. The Maintainers all ha
 
 ### Analytics Event
 
-```eval_rst
+```{eval-rst}
 .. automodule:: allianceauth.analytics.tasks
     :members: analytics_event
     :undoc-members:

docs/features/core/dashboard.md

@@ -13,7 +13,7 @@ For admin users the dashboard shows additional technical information about the
 Here is a list of available settings for the dashboard. They can be configured by adding them to your AA settings file (``local.py``).
 Note that all settings are optional and the app will use the documented default settings if they are not used.
 
-```eval_rst
+```{eval-rst}
 +-----------------------------------------------------+-------------------------------------------------------------------------+-----------+
 | Name                                                | Description                                                             | Default   |
 +=====================================================+=========================================================================+===========+

docs/features/core/groups.md

@@ -42,7 +42,7 @@ Most people won't have a use for public groups, though it can be useful if you w
 
 When a group is restricted only superuser admins can directly add or remove them to/from users. The purpose of this property is prevent staff admins from assigning themselves to groups that are security sensitive. The "restricted" property can be combined with all the other properties.
 
-```eval_rst
+```{eval-rst}
 .. _ref-reserved-group-names:
 ```
 
@@ -50,8 +50,7 @@ When a group is restricted only superuser admins can directly add or remove them
 
 When using Alliance Auth to manage external services like Discord, Auth will automatically duplicate groups on those services. E.g. on Discord Auth will create roles of the same name as groups. However, there may be cases where you want to manage groups on external services by yourself or by another bot. For those cases you can define a list of reserved group names. Auth will ensure that you can not create groups with a reserved name. You will find this list on the admin site under groupmanagement.
 
-```eval_rst
-.. note::
+:::{note}
     While this feature can help to avoid naming conflicts with groups on external services, the respective service component in Alliance Auth also needs to be build in such a way that it knows how to prevent these conflicts. Currently only the Discord and Teamspeak3 services have this ability.
 ```
 
@@ -101,8 +100,7 @@ By default, in AA both requests and leaves for non-open groups must be approved
 GROUPMANAGEMENT_AUTO_LEAVE = True
 ```
 
-```eval_rst
-.. note::
+:::{note}
     Before you set `GROUPMANAGEMENT_AUTO_LEAVE = True`, make sure there are no pending leave requests, as this option will hide the "Leave Requests" tab.
 ```
 
@@ -111,7 +109,7 @@ GROUPMANAGEMENT_AUTO_LEAVE = True
 Here is a list of available settings for Group Management. They can be configured by adding them to your AA settings file (``local.py``).
 Note that all settings are optional and the app will use the documented default settings if they are not used.
 
-```eval_rst
+```{eval-rst}
 +---------------------------------------------+---------------------------------------------------------------------------+------------+
 | Name                                        | Description                                                               | Default    |
 +=============================================+===========================================================================+============+
@@ -127,14 +125,13 @@ In order to join a group other than a public group, the permission `groupmanagem
 
 When a user loses this permission, they will be removed from all groups _except_ Public groups.
 
-```eval_rst
-.. note::
+:::{note}
     By default, the ``groupmanagement.request_groups`` permission is applied to the ``Member`` group. In most instances this, and perhaps adding it to the ``Blue`` group, should be all that is ever needed. It is unsupported and NOT advisable to apply this permission to a public group. See #697 for more information.
 ```
 
 Group Management should be mostly done using group leaders, a series of permissions are included below for thoroughness:
 
-```eval_rst
+```{eval-rst}
 +--------------------------------+-------------------+------------------------------------------------------------------------------------+
 | Permission                     | Admin Site        | Auth Site                                                                          |
 +================================+===================+====================================================================================+

docs/features/core/index.md

@@ -2,14 +2,13 @@
 
 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.
 
-```eval_rst
-.. toctree::
-    :maxdepth: 1
+```{toctree}
+:maxdepth: 1
 
-    dashboard
-    states
-    groups
-    analytics
-    notifications
-    admin_site
+dashboard
+states
+groups
+analytics
+notifications
+admin_site
 ```