From 795323fffd5e5877ec9d1f905734332d630363e4 Mon Sep 17 00:00:00 2001 From: Naman Goel Date: Fri, 10 Jan 2025 19:10:38 -0800 Subject: [PATCH] Update apps/docs/blog/2024-10-10-designing-for-composition.mdx Co-authored-by: Matt Styles --- apps/docs/blog/2024-10-10-designing-for-composition.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/apps/docs/blog/2024-10-10-designing-for-composition.mdx b/apps/docs/blog/2024-10-10-designing-for-composition.mdx index 8c1bc5a93..eff85d585 100644 --- a/apps/docs/blog/2024-10-10-designing-for-composition.mdx +++ b/apps/docs/blog/2024-10-10-designing-for-composition.mdx @@ -66,7 +66,7 @@ However, component-based frameworks, such as React, largely sidestep any architectural issues with inline styles. Components are a layer of abstraction that enables code reuse without needing to write the same styles over and over again. This change was noticed early and was described in the original -[`CSS-in-JS` talk by _Christopher Cheadeu_](https://vimeo.com/116209150). +[`CSS-in-JS` talk by _Christopher Chedeau_](https://vimeo.com/116209150). So, when it came to designing StyleX, we decided to model our styles after inline styles. To form a mental model, it can be helpful to think of StyleX