From 285d5c085fbb8660d630d5e48e61598f54f9decd Mon Sep 17 00:00:00 2001 From: Ola Hungerford Date: Wed, 11 Mar 2026 08:29:10 -0700 Subject: [PATCH] Apply suggestion from @olaservo --- specification/v2_ux_components.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/specification/v2_ux_components.md b/specification/v2_ux_components.md index 83590304..85a5525b 100644 --- a/specification/v2_ux_components.md +++ b/specification/v2_ux_components.md @@ -9,7 +9,7 @@ We are developing React components with Mantine, Zustand, and Storybook using a The idea is that a component receives everything it needs through props — the data it renders *and* the callbacks it fires when the user interacts. The component itself has no idea where the data came from or what happens when a button is clicked. It just calls `onSave(formData)` and trusts that someone upstream is handling it. -This creaes clean layering: Zustand stores own the state and logic, container components (or hooks) wire stores to presentational components, and the presentational components themselves are pure rendering machines. Storybook targets that bottom layer exclusively. +This creates clean layering: Zustand stores own the state and logic, container components (or hooks) wire stores to presentational components, and the presentational components themselves are pure rendering machines. Storybook targets that bottom layer exclusively. ## What Storybook Does