[autofix.ci] apply automated fixes

autofix-ci[bot] · web-flow · commit b6497be1a973 · 2025-03-12T00:09:23.000Z
diff --git a/docs/boilerplate.md b/docs/boilerplate.md
@@ -4,7 +4,7 @@ All these files will be generated at your `src/_standalone/<component>` folder w
 
 ## **index.svelte**
 
-The component written here will be transformed into a embedabble - you can treat it as **any** Svelte component and Svelte Standalone will bundle it for you. 
+The component written here will be transformed into a embedabble - you can treat it as **any** Svelte component and Svelte Standalone will bundle it for you.
 
 :::warning
 This is the `entry` for your vite build. You **MUST** explicitly import the global CSS files here.
@@ -17,9 +17,9 @@ Embedding logic that controls how and where the component is inserted. It follow
 This is a example of a `embed file` using the [embed on body method](/embed.html#auto-embed-on-body)
 
 ```ts
-import { autoEmbedWithTarget } from 'svelte-standalone'
-import Example from './index.svelte' // your embedabble
-autoEmbedWithTarget(Example, 'example')
+import { autoEmbedWithTarget } from 'svelte-standalone';
+import Example from './index.svelte'; // your embedabble
+autoEmbedWithTarget(Example, 'example');
 ```
 
 :::tip
@@ -33,13 +33,13 @@ Default configuration for your component, including settings like styles or init
 ```ts
 // example
 import type { ComponentProps } from 'svelte';
-import type { MultipleEmbedWindow } from 'svelte-standalone'; 
+import type { MultipleEmbedWindow } from 'svelte-standalone';
 import Example from './index.svelte'; // your embedabble
 
 export type ExampleProps = ComponentProps<Example>; // props from your components
 export const defaultConfig: ExampleProps = {}; // this will be used - when aplicable - as a config to start your embedabble (it'll also be used at your story when using storybook)
 
 declare global {
-	interface Window extends MultipleEmbedWindow<typeof Example, 'example'> {} // typesafe wrapper for window.example 
+	interface Window extends MultipleEmbedWindow<typeof Example, 'example'> {} // typesafe wrapper for window.example
 }
-```
+```
diff --git a/docs/cli.md b/docs/cli.md
@@ -16,13 +16,12 @@ npx standalone create
 
 1. **Name your component**: Enter a name for your component (e.g., `payments`).
 2. **Choose an embedding strategy**:
-  - **Explicit Call (Single Instance)**: Mounts the component **once** using `window.payments.start()`.
-  - **Explicit Call (Multiple Instances)**: Allows mounting **multiple** instances with `window.payments.start()`.
-  - **Auto-Embed with Target ID**: **Automatically** appends to an element with a specified `id`.
-  - **Auto-Embed with Target Class**: **Automatically** appends to elements with a specified `class`.
-  - **Auto-Embed on Body**: **Automatically** appends to the `<body>` when downloaded.
-
 
+- **Explicit Call (Single Instance)**: Mounts the component **once** using `window.payments.start()`.
+- **Explicit Call (Multiple Instances)**: Allows mounting **multiple** instances with `window.payments.start()`.
+- **Auto-Embed with Target ID**: **Automatically** appends to an element with a specified `id`.
+- **Auto-Embed with Target Class**: **Automatically** appends to elements with a specified `class`.
+- **Auto-Embed on Body**: **Automatically** appends to the `<body>` when downloaded.
 
 ## `build`
 
@@ -37,13 +36,17 @@ npx standalone build
 ### Options:
 
 - **Production Build**: Minifies and optimizes for production.
+
 ```bash
 npx standalone build --production
 ```
+
 - **Build All Components**: Builds all standalone components at once.
+
 ```bash
 npx standalone build --all
-  ```
+```
+
 - **Strip Runtime**: Bundles shared styles directly into components (excludes the runtime).
   ```bash
   npx standalone build --strip-runtime
diff --git a/docs/install.md b/docs/install.md
@@ -1,10 +1,10 @@
-# Installation Guide  
+# Installation Guide
 
-Set up **Svelte Standalone** as you would set up any Svelte project:  
+Set up **Svelte Standalone** as you would set up any Svelte project:
 
-1. **Create a Svelte App** – Use the [Svelte CLI](https://svelte.dev/docs/kit/creating-a-project) and select your preferred tools.  
-2. **Clean Up** – Remove svelte boilerplate code (e.g., routes, components).  
-3. **Install Svelte Standalone**  
+1. **Create a Svelte App** – Use the [Svelte CLI](https://svelte.dev/docs/kit/creating-a-project) and select your preferred tools.
+2. **Clean Up** – Remove svelte boilerplate code (e.g., routes, components).
+3. **Install Svelte Standalone**
 
 ```bash
    npm install -D svelte-standalone@latest
diff --git a/docs/introduction.md b/docs/introduction.md
@@ -6,39 +6,39 @@ Featuring _opt-in_ support for **Tailwind**, **TypeScript** or **Storybook**, it
 
 [Just want to try it out? Let's install it.](/install)
 
-## What Are Embedabbles?  
+## What Are Embedabbles?
 
-Simply put, *embedabbles* are Svelte components designed to work in **any JavaScript environment**. Unlike regular Svelte components, an embedabble **must** be fully self-contained since it should be able to **mount itself** and function independently without relying on a specific framework or setup.  
+Simply put, _embedabbles_ are Svelte components designed to work in **any JavaScript environment**. Unlike regular Svelte components, an embedabble **must** be fully self-contained since it should be able to **mount itself** and function independently without relying on a specific framework or setup.
 
-## When to Use Embedabbles?  
+## When to Use Embedabbles?
 
-Embedabbles are great when you need to **embed a Svelte component anywhere**, regardless of the tech stack i.e. **third-party integrations**, **no-framework environments** or even as **microfrontends**.  
+Embedabbles are great when you need to **embed a Svelte component anywhere**, regardless of the tech stack i.e. **third-party integrations**, **no-framework environments** or even as **microfrontends**.
 
-## Why Use Svelte Standalone?  
+## Why Use Svelte Standalone?
 
-- **Reactive & Lightweight** – Build fast, self-contained embeddables with Svelte’s reactivity.  
-- **Flexible** – Opt-in support for Tailwind, TypeScript, and Storybook.  
-- **Zero Setup** – Handles minification, CSS purging, and boilerplate generation for you.  
-- **Universal Compatibility** – Works across all OS and node package managers.  
+- **Reactive & Lightweight** – Build fast, self-contained embeddables with Svelte’s reactivity.
+- **Flexible** – Opt-in support for Tailwind, TypeScript, and Storybook.
+- **Zero Setup** – Handles minification, CSS purging, and boilerplate generation for you.
+- **Universal Compatibility** – Works across all OS and node package managers.
 
-## Can I Use It With?  
+## Can I Use It With?
 
-Yes you can! **Svelte Standalone** is made to integrate with any Svelte workflow. It offers **_opt-in_** support for:  
+Yes you can! **Svelte Standalone** is made to integrate with any Svelte workflow. It offers **_opt-in_** support for:
 
-- **Tailwind**  
-- **TypeScript**  
-- **Storybook**  
-- **SvelteKit**  
+- **Tailwind**
+- **TypeScript**
+- **Storybook**
+- **SvelteKit**
 
 ## Boilerplate Generation
 
-**Svelte Standalone** automatically scans your `package.json` and generates boilerplate code based on your setup:  
+**Svelte Standalone** automatically scans your `package.json` and generates boilerplate code based on your setup:
 
-- **Storybook detected?** → Generates story files.  
-- **SvelteKit detected?** → Generates route files.  
-- **TypeScript/Tailwind detected?** → Applies them to the boilerplate.  
-- **SvelteKit** → Generate routes for bundled embedabbles.  
-- **Storybook** → Create component stories.  
+- **Storybook detected?** → Generates story files.
+- **SvelteKit detected?** → Generates route files.
+- **TypeScript/Tailwind detected?** → Applies them to the boilerplate.
+- **SvelteKit** → Generate routes for bundled embedabbles.
+- **Storybook** → Create component stories.
 
 ## Is It Type-Safe?
 
