Getting started section is done

Finished the support

Author: remotesynth

src/content/docs/aws/capabilities/cloud-sandbox/ephemeral-instances.md

@@ -79,7 +79,7 @@ You can shut down the instance by navigating to the [Ephemeral Instances page](h
 
 <img src="shutdown-ephemeral-instance.png" alt="Shutdown the LocalStack Ephemeral Instance" title="Shutdown the LocalStack Ephemeral Instance" width="800" />
 
-:::warning
+:::danger
 Ephemeral Instances, by default, are created with the latest version of LocalStack.
 If you have created a Cloud Pod from an older version of LocalStack, you need to update the Cloud Pod to the latest version before loading it into an Ephemeral Instance.
 :::

src/content/docs/aws/getting-started/auth-token.mdx

@@ -23,7 +23,7 @@ Auth tokens come in two types: a **Developer Auth Token** and a **CI Auth Token*
 
 Both the **Developer Auth Token** and **CI Auth Token** can be managed on the [Auth Tokens page](https://app.localstack.cloud/workspace/auth-tokens).
 
-:::warning
+:::danger
 - It's crucial to keep your Auth Token confidential.
   Do not include it in source code management systems, such as Git repositories.
 - Be aware that if an Auth Token is committed to a public repository, it is at risk of exposure, and could remain in the repository's history, even if attempts are made to rewrite it.
@@ -66,7 +66,7 @@ LocalStack requires the `LOCALSTACK_AUTH_TOKEN` environment variable to contain
 You can configure your Auth Token in several ways, depending on your use case.
 The following sections describe the various methods of setting your Auth Token.
 
-:::warning
+:::danger
 - It's crucial to keep your Auth Token confidential.
   Do not include it in source code management systems, such as Git repositories.
 - Be aware that if an Auth Token is committed to a public repository, it's at risk of exposure, and could remain in the repository's history, even if attempts are made to rewrite it.

src/content/docs/aws/getting-started/help-support.md

@@ -22,7 +22,7 @@ For non-technical issues, such as billing or account inquiries, please contact s
 
 We welcome any feedback as we continue to improve LocalStack for all users.
 
-:::
+:::note
 At the moment, we only provide support in `English`, as we are an international team with members from various regions.
  This allows us to maintain clear and consistent internal communication across all our locations.
 :::
@@ -185,7 +185,7 @@ During these sessions, our support engineers can directly observe and diagnose t
 
 ### Enterprise support
 
-To learn more about the support available to **Enterprise** plan users, refer to the [Enterprise Support]({{<ref "enterprise-support" >}}) page.
+To learn more about the support available to **Enterprise** plan users, refer to the [Enterprise Support](/aws/pro/enterprise-support/) page.
 
 ## Support Business Hours
 
@@ -217,6 +217,8 @@ To use LocalStack's diagnostics endpoint:
 - Run the affected task(s)
 - Call the diagnostic endpoint `curl -s localhost:4566/_localstack/diagnose | gzip -cf > diagnose.json.gz` (Endpoint URL depends on your configuration)
 - Send the output file to our Slack chat
+:::
 
-<span style="color: darkred;">**Ensure that you avoid sending the diagnostic output to public channels or forums, as it may contain sensitive information.**</span>
+:::danger
+Ensure that you avoid sending the diagnostic output to public channels or forums, as it may contain sensitive information.
 :::

src/content/docs/aws/getting-started/installation.mdx

@@ -122,7 +122,7 @@ python3 -m pip install --user localstack
 ```
 :::
 
-:::warning
+:::danger
 Do not use `sudo` or the `root` user when starting LocalStack.
 It should be installed and started entirely under a local non-root user.
 :::