From 278b3c71e1925eee7e8936622217324f934453f2 Mon Sep 17 00:00:00 2001 From: Cody Coljee-Gray Date: Wed, 11 Jun 2025 18:03:37 -0700 Subject: [PATCH] Grammar fixes en-US.mdx (#494) --- .../user-interface-components-api-design-principles/en-US.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/packages/front-end-interview-guidebook/contents/user-interface-components-api-design-principles/en-US.mdx b/packages/front-end-interview-guidebook/contents/user-interface-components-api-design-principles/en-US.mdx index a5d9cf227..3506d9342 100644 --- a/packages/front-end-interview-guidebook/contents/user-interface-components-api-design-principles/en-US.mdx +++ b/packages/front-end-interview-guidebook/contents/user-interface-components-api-design-principles/en-US.mdx @@ -219,7 +219,7 @@ Despite its flaws, class injection is still a very popular option. ### CSS selector hooks -Technically speaking, developers can achieve customization if they read the source code of the component and define their custom styling by using the same classes. However, doing this is dangerous as relying on a component's internals and there's no guarantee that the class names won't change in future. +Technically speaking, developers can achieve customization if they read the source code of the component and define their custom styling by using the same classes. However, doing this is dangerous as relying on a component's internals and there's no guarantee that the class names won't change in the future. If UI library authors can make these classes/attributes part of their API, which comes with these guarantees: