diff --git a/docs/docs/guides/integrate/export-and-import.md b/docs/docs/guides/integrate/export-and-import.md
index d47df6d174..05f9cabd18 100644
--- a/docs/docs/guides/integrate/export-and-import.md
+++ b/docs/docs/guides/integrate/export-and-import.md
@@ -12,20 +12,18 @@ Currently, this doesn't include the following points:
 * Global IDPs
 * Global second/multi factors
 * Machine keys
-* PAT's
+* Personal Access Tokens
 * Application keys
+* Passwordless authentication
 
 Which results in that if you want to import, and you have no defined organization-specific custom policies, the experience for your users will not be exactly like in your old instance.
-```suggestion
 
-::note Note that the ressources will be migrated without the event stream. This means that you will not have the audit trail for the imported objects.
-
-*** With this export and import the current audit trail is not included, the resources will be newly created ***
+:::note 
+Note that the resources will be migrated without the event stream. This means that you will not have the audit trail for the imported objects.
+:::
 
 ### Export from V1 to import into V2 directly 
 
-***To use this requests you have to have an access token with enough permissions to export and import.***
-
 To export all necessary data you only have to use one request, as an example:
 
 ```bash
@@ -50,7 +48,9 @@ curl  --request POST \
 * "timeout": timeout of the call to export the data
 * "response_output": to output the export as response to the call
 
-***To import the exported data into you new instance, you have to have an already existing instance on a ZITADEL V2, with all desired configuration and global resources.***
+:::note 
+To import the exported data into you new instance, you have to have an already existing instance on a ZITADEL V2, with all desired configuration and global resources.
+:::
 
 Then as an example you can use one request for the import:
 
@@ -66,9 +66,10 @@ curl --request POST \
 
 ## Export from V1 to Import into V2 thorugh GCS
 
-***To use this requests you have to have an access token with enough permissions to export and import.***
-
-***The used serviceaccount has to have at least the role "Storage Object Creator" to create objects on GCS***
+:::note 
+To use this requests you have to have an access token with enough permissions to export and import.
+The used serviceaccount has to have at least the role "Storage Object Creator" to create objects on GCS
+:::
 
 To export all necessary data you only have to use one request which results in a file in your GCS, as an example:
 
@@ -100,9 +101,10 @@ curl  --request POST \
   * "bucket": used bucket for output on GCS
   * "serviceaccount_json": base64-encoded serviceaccount.json used to output the file on GCS
 
-***To import the exported data into you new instance, you have to have an already existing instance on a ZITADEL V2, with all desired configuration and global resources.***
-
-***The used serviceaccount has to have at least the role "Storage Object Viewer" to create objects on GCS***
+:::note
+To import the exported data into you new instance, you have to have an already existing instance on a ZITADEL V2, with all desired configuration and global resources.
+The used serviceaccount has to have at least the role "Storage Object Viewer" to read objects from GCS
+:::
 
 Then as an example you can use one request for the import: