Fixing callouts

Author: remotesynth

src/content/docs/aws/capabilities/chaos-engineering/chaos-engineering-dashboard.md

@@ -16,9 +16,9 @@ The dashboard uses [LocalStack Chaos API]({{< ref "chaos-api" >}}) under the hoo
 
 You can find this feature in the LocalStack Web Application by navigating to [**app.localstack.cloud/chaos-engineering**](https://app.localstack.cloud/chaos-engineering).
 
-{{< callout "note" >}}
+:::note
 Chaos Engineering Dashboard is offered as a **preview** feature and is under active development.
-{{< /callout >}}
+:::
 
 ## Features
 

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

@@ -11,9 +11,9 @@ sidebar:
 Ephemeral Instances allows you to run a LocalStack instance in the cloud.
 You can interact with these instances via the LocalStack Web Application, or by configuring your integrations and developer tools with the endpoint URL of the ephemeral instance.
 
-{{< callout "note" >}}
+:::note
 Ephemeral Instances is offered as a **preview** feature and is under active development.
-{{< /callout >}}
+:::
 
 ## Getting started
 
@@ -79,10 +79,10 @@ 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" />
 
-{{< callout "warning" >}}
+:::warning
 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.
-{{< /callout >}}
+:::
 
 ## Ephemeral Instances CLI
 

src/content/docs/aws/capabilities/security-testing/iam-policy-stream.md

@@ -14,9 +14,9 @@ This is typically a service resource for resource-based policies, or an IAM prin
 Subsequently, it displays the suggested policy.
 This feature aids in identifying the correct permissions for cloud applications and can help spot logical errors, such as unexpected actions in a policy.
 
-{{< callout "note" >}}
+:::note
 IAM Policy Stream is offered as a **preview** feature and is under active development.
-{{< /callout >}}
+:::
 
 ## Getting started
 
@@ -84,10 +84,10 @@ The Web Application provides the following features:
 3. Includes a feature to activate or deactivate this functionality on-the-fly for performance tuning.
 4. Presents an option to reset the stream, facilitating a clean slate to generate new policies.
 
-{{< callout "tip" >}}
+:::tip
 You don't need to set additional configuration variables, such as `DEBUG=1` or `IAM_SOFT_MODE=1`, when using the IAM Policy Stream with Web Application.
 However, it won't enforce policies or print IAM-related logs in the LocalStack container.
-{{< /callout >}}
+:::
 
 To use this feature, open the LocalStack Web Application in your browser, go to the IAM Policy Stream section, and click on **Enable** to view the **Summary Policy** and **Output**.
 

src/content/docs/aws/capabilities/web-app/stack-insights.md

@@ -13,12 +13,12 @@ Stack Insights let users report AWS API usage telemetry to their LocalStack acco
 
 Stack Insights show which APIs are used, which clients or integrations use specific services and API operations, and which services cause the most API errors.
 
-{{< callout "note" >}}
+:::note
 Your privacy matters to us!
 We only collect anonymized and sanitized data.
 No sensitive information about your application is ever collected or exposed.
 The data is only used to provide you with insights into the usage of LocalStack and to help us improve the product.
-{{< /callout >}}
+:::
 
 ## Getting started
 
@@ -57,7 +57,7 @@ View the list of events during the entire Stack lifetime, including:
 
 You can disable event reporting on your LocalStack client by setting the environment variable `DISABLE_EVENTS=1`.
 
-{{< callout "tip" >}}
+:::tip
 Brave blocks `localhost` requests due to security by default via shields.
 While some sites need access to `localhost` / `127.0.0.1` to work correctly, an easy option to allow a user to enable this is manually enabling via the site via `brave://settings/content/insecureContent`.
-{{< /callout >}}
+:::

src/content/docs/aws/capabilities/web-app/stack-overview.md

@@ -17,9 +17,9 @@ Alternatively, go to your LocalStack Instance and click on **Overview** to see a
 <br>
 <br>
 
-{{< callout "note" >}}
+:::note
 Stack Overview is offered as a **preview** feature and is under active development.
-{{< /callout >}}
+:::
 
 ## Supported Resources
 

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

@@ -21,12 +21,12 @@ 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).
 
-{{< callout "warning">}}
+:::warning
 - 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.
 - In case your Auth Token is accidentally published, immediately rotate it on the [Auth Token page](https://app.localstack.cloud/workspace/auth-tokens).
-{{< /callout >}}
+:::
 
 ## Managing your License
 
@@ -52,9 +52,9 @@ After initiating your trial or acquiring a license, proceed to assign it to a us
 If you have joined a workspace, you need to be assigned a license by the workspace administrator.
 In case of switching workspaces or licenses, you need to make sure that you are assigned to the correct license.
 
-{{< callout "note" >}}
+:::note
 If you do not assign a license, you will not be able to use LocalStack even if you have a valid Auth token.
-{{< /callout >}}
+:::
 
 To view your own assigned license, visit the [My License page](https://app.localstack.cloud/workspace/my-license).
 You can further navigate to the [Auth Token page](https://app.localstack.cloud/workspace/auth-tokens) to view your **Developer Auth Token** and **CI Auth Token**.
@@ -65,12 +65,12 @@ 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.
 
-{{< callout "warning">}}
+:::warning
 - 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.
 - In case your Auth Token is accidentally published, immediately rotate it on the [Auth Token page](https://app.localstack.cloud/workspace/auth-tokens).
-{{< /callout >}}
+:::
 
 ### LocalStack CLI
 
@@ -87,19 +87,19 @@ localstack start
 {{< /tab >}}
 {{< /tabpane >}}
 
-{{< callout "note" >}}
+:::note
 1. You can alternatively set the `LOCALSTACK_AUTH_TOKEN` environment variable in your shell session.
   This ensures the Auth Token is transmitted to your LocalStack container, enabling key activation.
 2. The `localstack auth set-token` command is only available for `localstack` CLI and cannot be used with a Docker/Docker Compose setup.
-{{< /callout >}}
+:::
 
 You have the option to run your LocalStack container in the background by appending the `-d` flag to the `localstack start` command.
 
 The `localstack` CLI automatically detects the Auth Token and appropriately conveys it to the LocalStack container.
 
-{{< callout "note" >}}
+:::note
 If you are using LocalStack with an Auth Token, it's necessary to download the [LocalStack Pro image](https://docs.localstack.cloud/references/docker-images/#localstack-pro-image), which includes Pro services and several advanced features.
-{{< /callout >}}
+:::
 
 ### Docker
 

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

@@ -22,10 +22,10 @@ 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.
 
-{{< callout >}}
+:::
 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.
-{{< /callout >}}
+:::
 
 ## Support Coverage
 
@@ -207,7 +207,7 @@ In case you encounter any issues with LocalStack, follow these troubleshooting g
 - Consult the error logs for any relevant error messages or warnings.
 - Seek guidance from the community through the user forum.
 
-{{< callout "note" >}}
+:::note
 In many scenarios, we ask our customers to use the diagnostics endpoint to provide additional information.
 
 To use LocalStack's diagnostics endpoint:
@@ -219,4 +219,4 @@ To use LocalStack's diagnostics endpoint:
 - 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>
-{{< /callout >}}
+:::

src/content/docs/aws/tooling/aws-replicator.md

@@ -17,19 +17,19 @@ Some resources may be referred to by ARN, for example Secrets Manager secrets, b
 LocalStack AWS Replicator creates identical copies of AWS resources in a running LocalStack instance.
 This means that external resources can easily be replicated before deploying the main application, and removes the need to change existing stacks or create custom infrastructure, making LocalStack setup easier.
 
-{{< callout "note">}}
+:::note
 The AWS Replicator is in a preview state, supporting only [selected resources](#supported-resources).
 It is only available as part of the **LocalStack Teams** plan and higher.
-{{< /callout >}}
+:::
 
 ## Getting started
 
 A valid `LOCALSTACK_AUTH_TOKEN` must be configured to start the LocalStack Pro image.
 
-{{< callout "note" >}}
+:::note
 The Replicator is in limited preview and is available from LocalStack CLI version 4.2.0.
 If you encounter issues, update your [LocalStack CLI](https://docs.localstack.cloud/getting-started/installation/#updating).
-{{< /callout >}}
+:::
 
 ### Retrieve credentials to access AWS
 
@@ -97,13 +97,13 @@ localstack replicator start \
  [--target-region-name <region-name>]
 {{< /command >}}
 
-{{< callout "note" >}}
+:::note
 Resources that supports replicating with arn can be replicated by providing `--resource-arn` instead of `--resource-type` and `--resource-identifier`.
 
 {{< command >}}
 <disable-copy>$ </disable-copy>localstack replicator start --resource-arn <resource-arn>
 {{< /command >}}
-{{< /callout >}}
+:::
 
 This triggers the replication job.
 The output will look similar to:
@@ -121,12 +121,12 @@ The output will look similar to:
 }
 ```
 
-{{< callout "note" >}}
+:::note
 - `--target-account-id` specifies the destination AWS account for replication.
   If not set, the resource is replicated into account `000000000000`.
 - `--target-region-name` specifies the destination AWS region.
   If not set, the resource is replicated into the default region from the provided credentials.
-{{< /callout >}}
+:::
 
 #### Using the HTTP API
 
@@ -187,9 +187,9 @@ To wait for the job to finish, use the `--follow` flag.
 
 To check the status of a replication job via the HTTP API, send a `GET` request to `http://localhost.localstack.cloud:4566/_localstack/replicator/jobs/<job-id>`.
 
-{{< callout "tip" >}}
+:::tip
 If the replication state is `SUCCEEDED` but the resource is missing, check in account `000000000000`.
-{{< /callout >}}
+:::
 
 ## Quickstart
 
@@ -320,8 +320,8 @@ The project is still in preview state and we welcome feedback and bug reports.
 We have opened a [github issue where you can request and upvote](https://github.com/localstack/localstack/issues/12439) to help us prioritize our efforts and support the resources with the most impact.
 For any other requests or reports, please open a [new github issue](https://github.com/localstack/localstack/issues/new/choose).
 
-{{< callout "tip" >}}
+:::tip
 To ensure support for all resources, use the latest LocalStack Docker image.
-{{< /callout >}}
+:::
 
 {{< localstack_replicator_table >}}