remaining folders done

Author: remotesynth

src/content/docs/aws/integrations/app-frameworks/quarkus.md

@@ -140,7 +140,7 @@ All the other configuration properties can be overridden at runtime.
 | `quarkus.aws.devservices.localstack.additional-services."additional-services".service-name` | string                 | `localstack`                         |
 | `quarkus.aws.devservices.localstack.additional-services."additional-services".container-properties` | `Map<String,String>`  |                                      |
 
-{{< callout >}}
+:::note
 - If `quarkus.aws.devservices.localstack.additional-services."additional-services".enabled` is set to `true` and the endpoint-override is not configured, LocalStack will be started and utilized instead of the provided configuration.
   For all services excluding Cognito, LocalStack will function as the core cloud emulator.
    In the case of Cognito, the emulation/mocking will be done by Moto.
@@ -155,7 +155,7 @@ All the other configuration properties can be overridden at runtime.
   Otherwise, it creates a new container with the `quarkus-dev-service-localstack` label set to the specified value.
   In test mode, Dev Services groups services with the same service-name value into a single container instance.
   This property is useful when there's a requirement for multiple shared LocalStack instances.
-{{< /callout >}}
+:::
 
 ### Specific configuration
 

…/messaging/selfmanaged-kafka-cluster.mdx …s/messaging/selfmanaged-kafka-cluster.mdsrc/content/docs/aws/integrations/messaging/selfmanaged-kafka-cluster.mdx renamed to src/content/docs/aws/integrations/messaging/selfmanaged-kafka-cluster.md src/content/docs/aws/integrations/messaging/selfmanaged-kafka-cluster.mdx renamed to src/content/docs/aws/integrations/messaging/selfmanaged-kafka-cluster.md

@@ -11,7 +11,6 @@ It supports a wide range of testing frameworks and integrates seamlessly with CI
 You can use HyperExecute to run your LocalStack tests on your local machine or in the CI pipeline using a single configuration file.
 
 :::note
-
 LambdaTest provides specialized runners for LocalStack.
 The default runners don't provide a Docker socket, which is required for LocalStack to work properly.
 If you want to use LocalStack with HyperExecute, you need to get in touch with the LambdaTest team to get access to the specialized runners.
@@ -51,7 +50,6 @@ pre:
 The above minimal configuration file starts LocalStack and creates an S3 bucket, SQS queue, and SNS topic.
 
 :::note
-
 To use the LocalStack Pro image, configure a LocalStack Auth Token by appending `LOCALSTACK_AUTH_TOKEN=${{ .secrets.LOCALSTACK_AUTH_TOKEN }}` to the `localstack start` command.
 Subsequently, you need to add your LocalStack Auth Token to your HyperExecute Portal as a secret.
 :::

src/content/docs/aws/integrations/testing/hyperexecute.mdx

@@ -99,7 +99,7 @@ using var client = new AmazonS3Client(config);
 ```
 </TabItem>
 <TabItem label="Go">
-```go
+```go showLineNumbers
 func s3Client(ctx context.Context, l *localstack.LocalStackContainer) (*s3.Client, error) {
     // the Testcontainers Docker provider is used to get the host of the Docker daemon
     provider, err := testcontainers.NewDockerProvider()
@@ -150,8 +150,10 @@ S3Client s3 = S3Client.builder()
     .credentialsProvider(StaticCredentialsProvider.create(AwsBasicCredentials.create(localstack.getAccessKey(), localstack.getSecretKey())))
     .region(Region.of(localstack.getRegion()))
     .build();
+```
 </TabItem>
-{{< tab header="NodeJS (typescript)" lang="typescript">}}
+<TabItem label="NodeJS (typescript)">
+```typescript
 const awsConfig = {
       endpoint: localstack.getConnectionUri(),
       credentials: {
@@ -183,7 +185,6 @@ The Testcontainer can be created like this:
 public LocalStackContainer localstack = new LocalStackContainer(DockerImageName("localstack/localstack:2.0.0"))
                                                     .withExposedPorts(4510, 4511, 4512, 4513, 4514) // the port can have any value between 4510-4559, but LS starts from 4510
                                                     .withEnv("LOCALSTACK_AUTH_TOKEN", auth_token); // add your Auth Token here
-
 ```
 
 To find the exposed port which you can use to connect to the instance: