From de00002e745872c4ce06f3cc7b387c03494bd4fa Mon Sep 17 00:00:00 2001 From: Fredrik Nicol Date: Thu, 12 Apr 2018 23:55:34 +0200 Subject: [PATCH] Fix typo --- README.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/README.md b/README.md index e6c295f..e8481f0 100644 --- a/README.md +++ b/README.md @@ -33,7 +33,7 @@ $ yarn add csstype * [`@viewport`](#viewport) * [Pseudo types](#pseudo-types) * [Usage](#usage) -* [What should I to do when I get type errors?](#what-should-i-to-do-when-i-get-type-errors) +* [What should I do when I get type errors?](#what-should-i-do-when-i-get-type-errors) * [Version 2.0](#version-20) ## Style types @@ -206,7 +206,7 @@ const style: Style = { }; ``` -## What should I to do when I get type errors? +## What should I do when I get type errors? The goal is to have as perfect types as possible and we're trying to do our best. But with CSS Custom Properties, the CSS specification changing frequently and vendors implementing their own specifications with new releases sometimes causes type errors even if it should work. Here's some steps you could take to get it fixed: