Fix grammar issues

This commit is contained in:
Jonathan Reinink 2017-10-30 12:24:25 -04:00
parent be91596000
commit 7e860a8a6f

View File

@ -424,7 +424,7 @@ To get you started, we've provided a generous palette of great looking colors th
## Customizing
Tailwind makes it a breeze to modify to default color palette for you project. Remember, you own these colors and nothing will break if you change everything about them.
Tailwind makes it a breeze to modify the default color palette for you project. Remember, you own these colors and nothing will break if you change everything about them.
By default Tailwind defines the entire color palette in a `colors` object at the top of your Tailwind config file. These colors are then assigned to `textColors`, `backgroundColors` and `borderColors`. This approach works well since it provides a consistent naming system across all the utilities. However, you're welcome to modify them independently of one-another as well.
@ -465,6 +465,6 @@ You'll notice above that the color palette is also assigned to the `colors` key
In the default color palette we've used literal color names, like `red`, `green` and `blue`. Another common approach to naming colors is choosing functional names based on how the colors are used, such as `primary`, `secondary`, and `brand`.
You can also choose different approaches how handle your color variants. In the default color palette we've again used literal variants, like `light`, `dark`, and `darker`. Another common approach here is to use a numeric scale, like `100`, `200` and `300`.
You can also choose different approaches to how you name your color variants. In the default color palette we've again used literal variants, like `light`, `dark`, and `darker`. Another common approach here is to use a numeric scale, like `100`, `200` and `300`.
You should feel free to choose whatever color naming approach makes the most sense to your team.
You should feel free to choose whatever color naming approach makes the most sense to you.