`;
-}
+};
const testOptions = [
["funky", "Option One: The Funky One"],
@@ -55,13 +55,13 @@ export const ToggleGroup = () => {
// eslint-disable-next-line @typescript-eslint/no-explicit-any
const displayChange = (ev: any) => {
document.getElementById(
- "toggle-message-pad"
+ "toggle-message-pad",
)!.innerText = `Value selected: ${ev.detail.value}`;
};
return container(
html`
${testOptions.map(([key, label]) => html``)}
- `
+ `,
);
};
diff --git a/website/developer-docs/docs/templates/index.md b/website/developer-docs/docs/templates/index.md
index 7ae832890..9645e706d 100644
--- a/website/developer-docs/docs/templates/index.md
+++ b/website/developer-docs/docs/templates/index.md
@@ -8,7 +8,7 @@ The most common types are:
- [**Procedural**](./procedural.md): these are How To docs, the HOW information, with step-by-step instructions for accomplishing a task. This is what most people are looking for when they open the docs... and best practice is to separate the procedural docs from long, lengthy conceptual or reference docs.
-- **Conceptual**: these docs provide the WHY information, and explain when to use a feature (or when not to!), and general concepts behind the fature or functioanlity.
+- **Conceptual**: these docs provide the WHY information, and explain when to use a feature (or when not to!), and general concepts behind the feature or functioanlity.
- **Reference**: this is typically tables or lists of reference information, such as configuration values, or most commmonly APIs.