diff --git a/Readme.md b/Readme.md
index 91d70e3..dae3fde 100644
--- a/Readme.md
+++ b/Readme.md
@@ -50,7 +50,7 @@ Add your base font and color styles to the `body` element in your stylesheet, al
body {
color: #333;
- font: 16px/1.4 'Helvetica Neue', sans-serif;
+ font: 16px/1.4 "Helvetica Neue", sans-serif;
}
```
@@ -111,9 +111,11 @@ Creating two different styles for `h1` is made easy, only the properties for the
### Buttons
-`button` tags have a lot of default styles that can make them cumbersome to use from a styling perspective, especially if they should look like plain things or need to wrap some other content, but `button` tags are the recommended elements to use as click targets for user interactions. Falling back to using `` even with `role="button"` is [not recomended](https://developer.mozilla.org/en-US/docs/Web/Accessibility/ARIA/Roles/button_role) from an accessibility standpoint as Screenreaders will recognize `button`s as interactive elements by default and treat them accordingly. `a` should be used when there is the need to link to a page via `href`.
+`button` tags have a lot of default styles that can make them cumbersome to use from a styling perspective, especially if they should look like plain things or need to wrap some other content, but `button` tags are the recommended elements to use as click targets for user interactions. Falling back to using `` even with `role="button"` is [not recomended](https://developer.mozilla.org/en-US/docs/Web/Accessibility/ARIA/Roles/button_role) from an accessibility standpoint as screen readers will recognize `button`s as interactive elements by default and treat them accordingly. `a` should be used when there is the need to link to a page via `href`.
+
destyle.css resets buttons completely to make them usable as any other element * see note [below](#caveats).
+
```css
/* Make anything look like a link, even a