paulononato/backstage
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

docs: Fix spelling issue

Browse Source 
Signed-off-by: Carlos Esteban Lopez <lcarlosesteb@vmware.com>
This commit is contained in:
Carlos Esteban Lopez
2022-10-21 13:33:04 -05:00
parent 1c8c0a2cc7
commit 56a74adc56
1 changed files with 1 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/dls/component-design-guidelines.md
+1 -1
View File
@@ -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