website: format docs with prettier (#2833)

* run prettier

Signed-off-by: Jens Langhammer <jens.langhammer@beryju.org>

* add scim to comparison

Signed-off-by: Jens Langhammer <jens.langhammer@beryju.org>

website/docs/events/index.md

@@ -4,29 +4,29 @@ title: Events
 
 Events are authentik's built-in logging system. Whenever any of the following actions occur, an event is created:
 
-- A user logs in/logs out (including the source, if available)
-- A user fails to login
-- A user sets their password
+-   A user logs in/logs out (including the source, if available)
+-   A user fails to login
+-   A user sets their password
 
-- A user views a token
+-   A user views a token
 
-- An invitation is used
+-   An invitation is used
 
-- A user object is written to during a flow
+-   A user object is written to during a flow
 
-- A user authorizes an application
-- A user links a source to their account
+-   A user authorizes an application
+-   A user links a source to their account
 
-- A user starts/ends impersonation, including the user that was impersonated
+-   A user starts/ends impersonation, including the user that was impersonated
 
-- A policy is executed (when a policy has "Execution Logging" enabled)
-- A policy or property mapping causes an exception
+-   A policy is executed (when a policy has "Execution Logging" enabled)
+-   A policy or property mapping causes an exception
 
-- A configuration error occurs, for example during the authorization of an application
+-   A configuration error occurs, for example during the authorization of an application
 
-- Any objects is created/updated/deleted
+-   Any objects is created/updated/deleted
 
-- An update is available
+-   An update is available
 
 Certain information is stripped from events, to ensure no passwords or other credentials are saved in the log.
 

website/docs/events/transports.md

@@ -13,7 +13,7 @@ This will send a POST request to the given URL with the following contents:
     "body": "body of the notification message",
     "severity": "severity level as configured in the trigger",
     "user_email": "user's email",
-    "user_username": "user's username",
+    "user_username": "user's username"
 }
 ```