find and replace fixes, will introduce errors

docs/features/services/nameformats.md

@@ -6,7 +6,7 @@ Each service's username or nickname, depending on which the service supports, ca
 
 Currently the following services support custom name formats:
 
-```eval_rst
+```{eval-rst}
 +-------------+-----------+-------------------------------------+
 | Service     | Used with | Default Formatter                   |
 +=============+===========+=====================================+
@@ -30,8 +30,7 @@ Currently the following services support custom name formats:
 +-------------+-----------+-------------------------------------+
 ```
 
-```eval_rst
-.. note::
+:::{note}
     It's important to note here, before we get into what you can do with a name formatter, that before the generated name is passed off to the service to create an account it will be sanitized to remove characters (the letters and numbers etc.) that the service cannot support. This means that, despite what you configured, the service may display something different. It is up to you to test your formatter and understand how your format may be disrupted by a certain services sanitization function.
 ```
 
@@ -59,7 +58,7 @@ A more digestible documentation of string formatting in Python is available on t
 
 Some examples of strings you could use:
 
-```eval_rst
+```{eval-rst}
 +------------------------------------------+---------------------------+
 | Formatter                                | Result                    |
 +==========================================+===========================+
@@ -71,12 +70,12 @@ Some examples of strings you could use:
 +------------------------------------------+---------------------------+
 ```
 
-```eval_rst
+```{eval-rst}
 .. important::
     For most services, name formats only take effect when a user creates an account. This means if you create or update a name formatter it wont retroactively alter the format of users names. There are some exceptions to this where the service updates nicknames on a periodic basis. Check the service's documentation to see which of these apply.
 ```
 
-```eval_rst
+```{eval-rst}
 .. important::
     You must only create one formatter per service per state. E.g. don't create two formatters for Mumble for the Member state. In this case one of the formatters will be used and it may not be the formatter you are expecting.
 ```