From: Jakub Wilk <jwilk@jwilk.net>
Date: Fri, 31 Mar 2017 23:07:49 +0000 (+0200)
Subject: Fix typo
X-Git-Url: http://git.ipfire.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=refs%2Fpull%2F10875%2Fhead;p=thirdparty%2FFont-Awesome.git

Fix typo
---

diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md
index f281d304ff..094cef8e62 100644
--- a/CONTRIBUTING.md
+++ b/CONTRIBUTING.md
@@ -87,7 +87,7 @@ As of v3.2.0, Font Awesome's CSS, LESS, SCSS, and documentation are all powered
 
 - Adhere to the [Recess CSS property order](http://markdotto.com/2011/11/29/css-property-order/)
 - Multiple-line approach (one property and value per line)
-- Always a space after a property's colon (.e.g, `display: block;` and not `display:block;`)
+- Always a space after a property's colon (e.g., `display: block;` and not `display:block;`)
 - End all lines with a semi-colon
 - For multiple, comma-separated selectors, place each selector on its own line
 - Attribute selectors, like `input[type="text"]` should always wrap the attribute's value in double quotes, for consistency and safety (see this [blog post on unquoted attribute values](http://mathiasbynens.be/notes/unquoted-attribute-values) that can lead to XSS attacks)