From 56a74adc56338e198aa3e298b14383ddaa18d54d Mon Sep 17 00:00:00 2001 From: Carlos Esteban Lopez Date: Fri, 21 Oct 2022 13:33:04 -0500 Subject: [PATCH] docs: Fix spelling issue Signed-off-by: Carlos Esteban Lopez --- docs/dls/component-design-guidelines.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/dls/component-design-guidelines.md b/docs/dls/component-design-guidelines.md index 6b96e82ca0..3622d8f2ba 100644 --- a/docs/dls/component-design-guidelines.md +++ b/docs/dls/component-design-guidelines.md @@ -41,7 +41,7 @@ Any component that needs a color to put in the styles should be using the theme's color palette, most Backstage components and all MUI components should use the theme's color palette by default, so unless you need explicit control on the color of a component (say when the component was designed to use the -primay color but you want to use the secondary), then the easiest way to access +primary color but you want to use the secondary), then the easiest way to access the color palette is with [`useTheme` hook](https://mui.com/material-ui/customization/theming/#accessing-the-theme-in-a-component). It's not a very common use case to override a theme color in a MUI component