Skip to content

Commit

Permalink
Merge pull request #219 from compwron/readme_typofix
Browse files Browse the repository at this point in the history
Replacing typo extentions with extensions in readme
  • Loading branch information
Vitaly Puzrin committed Mar 25, 2016
2 parents 625f0ee + df81f9b commit 74085df
Showing 1 changed file with 2 additions and 2 deletions.
4 changes: 2 additions & 2 deletions README.md
Expand Up @@ -21,7 +21,7 @@ for more details.
Supported engines are described in [Wiki](https://github.com/nodeca/mincer/wiki).
If you wish to add new engine support - read
[tutorial](https://github.com/nodeca/mincer/wiki/How-to-create-addon). Also
you can [search existing extentions](https://www.npmjs.org/browse/keyword/mincer-contrib)
you can [search existing extensions](https://www.npmjs.org/browse/keyword/mincer-contrib)
in npm.


Expand Down Expand Up @@ -330,7 +330,7 @@ additional extention and does not break language syntax. When enabled, any
`'$$ expression $$'` or `"$$ expression $$"` pattern will be replaced with
evaluated expression value. In expression you can write JS code and use
registered helpers. Macros are off by default. You should enable those for
particular extentions:
particular extensions:

```javascript
Mincer.MacroProcessor.configure(['.js', '.css']);
Expand Down

0 comments on commit 74085df

Please sign in to comment.