diff --git a/apps/docs/pages/docs/buttonkit.mdx b/apps/docs/pages/docs/buttonkit.mdx index 1b23995..7e967b8 100644 --- a/apps/docs/pages/docs/buttonkit.mdx +++ b/apps/docs/pages/docs/buttonkit.mdx @@ -112,7 +112,7 @@ const myButton = new ButtonKit() myButton.onClick(); ``` -The first argument required by this function, is your handler function which will acknowledge button clicks (interactions) handled by ButtonKit. You can handle them like so: +The first argument required by this function is your handler function which will acknowledge button clicks (interactions) handled by ButtonKit. You can handle them like so: ```js myButton.onClick((buttonInteraction) => { diff --git a/apps/docs/pages/docs/using-signals.mdx b/apps/docs/pages/docs/using-signals.mdx index 54cb40e..9ca30b9 100644 --- a/apps/docs/pages/docs/using-signals.mdx +++ b/apps/docs/pages/docs/using-signals.mdx @@ -1,12 +1,12 @@ import { Tabs, Callout } from 'nextra/components'; +# Using Signals + This is currently only available in the [development version](/docs/installation#development-version) of CommandKit. -# Using Signals - Signals are a way to add states and basic reactivity to your commands. It is similar to SolidJS signals. ## Creating a signal