remove hugo semantics

Author: HarshCasper

src/content/docs/snowflake/features/accounts.md

@@ -47,7 +47,7 @@ You can also specify the account for Snowflake drivers that let you connect with
 
 Example establishing a JDBC connection:
 
-```
+```text
 jdbc:snowflake://snowflake.localhost.localstack.cloud:4566/?account=your_account
 ```
 
@@ -67,4 +67,4 @@ The query statement will return the name of the account you are currently connec
 |------------------------------------------|
 | YOUR_ACCOUNT                             |
 +------------------------------------------+
-```
+```

src/content/docs/snowflake/features/authentication.md

@@ -32,9 +32,9 @@ sf_conn_obj = sf.connect(
 
 The default username and password are set to `test` and can be changed using `SF_DEFAULT_USER` and `SF_DEFAULT_PASSWORD` when starting the Snowflake emulator.
 
-{{< alert title="Note" >}}
+:::note
 It is not recommended to use your production credentials in the Snowflake emulator.
-{{< /alert >}}
+:::
 
 ## RSA key pair authentication
 
@@ -66,6 +66,6 @@ conn = snowflake.connector.connect(
 )
 ```
 
-{{< alert title="Note" >}}
+:::note
 The Snowflake emulator does not validate key contents—RSA authentication is mocked for local testing only.
-{{< /alert >}}
+:::

src/content/docs/snowflake/features/clones.md

@@ -3,8 +3,6 @@ title: Clones
 description: Get started with Clones in LocalStack for Snowflake
 ---
 
-
-
 ## Introduction
 
 Cloning in Snowflake allows you to create a quick, zero-copy duplicate of an existing database, schema, or table. This feature enables users to replicate data structures and content for testing or development without duplicating the underlying storage.
@@ -110,4 +108,4 @@ The expected output is:
 |  1 | test |
 +----+------+
 1 Row(s) produced. Time Elapsed: 0.012s
-```
+```

src/content/docs/snowflake/features/cross-database-resource-sharing.md

@@ -3,8 +3,6 @@ title: Cross-Database Resource Sharing
 description: Get started with cross-database resource sharing in the Snowflake emulator
 ---
 
-
-
 ## Introduction
 
 Snowflake data providers can easily share data from various databases using secure views. These views can include schemas, tables, and other views from one or more databases, as long as they're part of the same account.
@@ -97,4 +95,4 @@ The expected output is:
 
 ```plaintext
 (1, 2, 3)
-```
+```

src/content/docs/snowflake/features/dynamic-tables.md

@@ -3,8 +3,6 @@ title: Dynamic Tables
 description: Get started with Dynamic Tables in LocalStack for Snowflake
 ---
 
-
-
 ## Introduction
 
 Snowflake Dynamic Tables enable a background process to continuously load new data from sources into the table, supporting both delta and full load operations. A dynamic table automatically updates to reflect query results, removing the need for a separate target table and custom code for data transformation. This table is kept current through regularly scheduled refreshes by an automated process.
@@ -91,4 +89,4 @@ The output should be:
 | 1  | foo  |
 | 2  | bar  |
 +----+------+
-```
+```

src/content/docs/snowflake/features/hybrid-tables.md

@@ -3,8 +3,6 @@ title: Hybrid Tables
 description: Get started with Hybrid Tables in LocalStack for Snowflake
 ---
 
-
-
 ## Introduction
 
 Snowflake Hybrid tables, also known as Unistore hybrid tables, support fast, single-row operations by enforcing unique constraints for required primary keys and including indexes to speed up data retrieval. These tables are designed to optimize support for both analytical and transactional workloads simultaneously, underpinning Snowflake's Unistore architecture.
@@ -73,4 +71,4 @@ The output should be:
 | -----------------------------------------+
 | TEST-TABLE successfully dropped.         |
 +------------------------------------------+
-```
+```

src/content/docs/snowflake/features/iceberg-tables.md

@@ -3,8 +3,6 @@ title: Iceberg Tables
 description: This is a dummy description.
 ---
 
-
-
 ## Introduction
 
 Iceberg tables uses [Apache Iceberg](https://iceberg.apache.org/) open table format specification to provide an abstraction layer on data files stored in open formats. Iceberg tables for Snowflake offer schema evolution, partitioning, and snapshot isolation to manage the table data efficiently.
@@ -81,6 +79,6 @@ The output should be:
 
 You can also list the content of the S3 bucket:
 
-{{< command >}}
-$ awslocal s3 ls --recursive s3://test-bucket/
-{{< / command >}}
+```bash
+awslocal s3 ls --recursive s3://test-bucket/
+```

src/content/docs/snowflake/features/native-apps.md

@@ -66,14 +66,14 @@ You can access the Native App by visiting your preferred browser and navigating
 https://snowflake.localhost.localstack.cloud:4566/apps/test/test/TASKS_STREAMS_APP_username/
 ```
 
-{{< alert title="Note" >}}
+:::note
 The URL above is an example. Change the outputted URL by:
 
 1.  Replacing `https://app.snowflake.com` with `https://snowflake.localhost.localstack.cloud:4566`.
 2.  Changing the path structure from `/#/apps/application/` to `/apps/test/test/`.
 
 You can make additional changes depending on your local setup.
-{{< /alert >}}
+:::
 
 The following app should be displayed:
 

src/content/docs/snowflake/features/snowpipe.md

@@ -9,10 +9,10 @@ Snowpipe allows you to load data into Snowflake tables from files stored in an e
 
 The Snowflake emulator supports Snowpipe, allowing you to create and manage Snowpipe objects in the emulator. You can use Snowpipe to load data into Snowflake tables from files stored in a local directory or a local/remote S3 bucket. The following operations are supported:
 
-* `CREATE PIPE`
-* `DESCRIBE PIPE`
-* `DROP PIPE`
-* `SHOW PIPES`
+* [`CREATE PIPE`](https://docs.snowflake.com/en/sql-reference/sql/create-pipe)
+* [`DESCRIBE PIPE`](https://docs.snowflake.com/en/sql-reference/sql/describe-pipe)
+* [`DROP PIPE`](https://docs.snowflake.com/en/sql-reference/sql/drop-pipe)
+* [`SHOW PIPES`](https://docs.snowflake.com/en/sql-reference/sql/show-pipes)
 
 ## Getting started
 
@@ -24,9 +24,9 @@ In this guide, you will create a stage, and a pipe to load data from a local S3
 
 You can create a local S3 bucket using the `mb` command with the `awslocal` CLI.
 
-{{< command >}}
-$ awslocal s3 mb s3://test-bucket
-{{< / command >}}
+```bash
+awslocal s3 mb s3://test-bucket
+```
 
 ### Create a stage
 
@@ -73,11 +73,11 @@ Retrieve the `notification_channel` value from the output of the `DESC PIPE` que
 
 You can use the [`PutBucketNotificationConfiguration`](https://docs.aws.amazon.com/AmazonS3/latest/API/API_PutBucketNotificationConfiguration.html) API to create a bucket notification configuration that sends notifications to Snowflake when new files are uploaded to the S3 bucket.
 
-{{< command >}}
-$ awslocal s3api put-bucket-notification-configuration \
+```bash
+awslocal s3api put-bucket-notification-configuration \
     --bucket test-bucket \
     --notification-configuration file://notification.json
-{{< / command >}}
+```
 
 The `notification.json` file should contain the following configuration:
 
@@ -107,14 +107,14 @@ Copy a JSON file to the S3 bucket to trigger the pipe to load the data into the
 
 Upload the file to the S3 bucket:
 
-{{< command >}}
-$ awslocal s3 cp test.json s3://test-bucket/
-{{< / command >}}
+```bash
+awslocal s3 cp test.json s3://test-bucket/
+```
 
 ### Check the data
 
 After uploading the file to the S3 bucket in the previous step, the contents of the JSON file should get inserted into the table automatically by the `test_pipe` pipe. You can check the data in the table using the following query:
 
 ```sql
 SELECT * FROM my_test_table
-```
+```

…ontent/docs/snowflake/features/stages.md …ntent/docs/snowflake/features/stages.mdxsrc/content/docs/snowflake/features/stages.md renamed to src/content/docs/snowflake/features/stages.mdx src/content/docs/snowflake/features/stages.md renamed to src/content/docs/snowflake/features/stages.mdx

@@ -2,8 +2,7 @@
 title: Stages
 description: Get started with Stages in LocalStack for Snowflake
 ---
-
-
+import { Tabs, TabItem } from '@astrojs/starlight/components';
 
 ## Introduction
 
@@ -60,14 +59,22 @@ FILE_FORMAT = csv;
 
 In this example, you can upload the CSV files to the table stage provided for `employees` table.
 
-{{< tabpane >}}
-{{< tab header="Linux/macOS" lang="sql" >}}
+
+<Tabs>
+   <TabItem label="Linux/macOS">
+   ```sql
 PUT file://./employees0*.csv @@employees_stage AUTO_COMPRESS=TRUE;
-{{< /tab >}}
-{{< tab header="Windows" lang="sql" >}}
+```
+</TabItem>
+   <TabItem label="Windows">
+   ```sql
 PUT file://C:\temp\employees0*.csv @@employees_stage AUTO_COMPRESS=TRUE;
-{{< /tab >}}
-{{< /tabpane >}}
+```
+</TabItem>
+</Tabs>
+
+
+
 
 The expected output is:
 
@@ -87,10 +94,10 @@ The expected output is:
 
 You can also load data from an S3 bucket using the `CREATE STAGE` command. Create a new S3 bucket named `testbucket` and upload the [employees CSV files](./getting-started.zip) to the bucket. You can use LocalStack's `awslocal` CLI to create the S3 bucket and upload the files.
 
-{{< command >}}
+```bash
 awslocal s3 mb s3://testbucket
 awslocal s3 cp employees0*.csv s3://testbucket
-{{< /command >}}
+```
 
 In this example, you can create a stage called `my_s3_stage` to load data from an S3 bucket:
 
@@ -107,4 +114,4 @@ You can further copy data from the S3 stage to the table using the `COPY INTO` c
 COPY INTO mytable
 FROM @my_s3_stage
 PATTERN='.*employees.*.csv';
-```
+```