From c87524561d2d190b2480b0c6c1b514f552926888 Mon Sep 17 00:00:00 2001 From: Grant Starkman Date: Wed, 8 May 2024 13:11:05 -0600 Subject: [PATCH] update readme --- packages/ui/README.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/packages/ui/README.md b/packages/ui/README.md index 9bb9eabc685..21bfd7d46e8 100644 --- a/packages/ui/README.md +++ b/packages/ui/README.md @@ -67,7 +67,7 @@ To account for screen size references, components take in props to adapt custom ``` -When components cannot take in these props or a value needs to be resued multiple times, the `useMedia` hook allows these same breakpoint values to be defined programmatically. +When components cannot take in these props or a value needs to be reused multiple times, the `useMedia` hook allows these same breakpoint values to be defined programmatically. ### Other notable usage @@ -119,7 +119,7 @@ When possible, usage of `styled` should be limited to use within the `ui` packag The `ui` package should be where we put all low level interface components that are shared between apps (or will likely be shared). It should *not* contain components that are specific to any one app, or which touch app-level data in any way. -A good rule of thumb is: if it deals with app-specific state (eg anything thats stored in redux) or has a very complex interface, then: +A good rule of thumb is: if it deals with app-specific state (eg anything that's stored in redux) or has a very complex interface, then: - If it's specific to just one app, put it in that app. - Else if it's shared between multiple apps, put it in a shared package above the UI package, e.g `packages/{package}`.