some readme copy Ref #18

src/readme.md

@@ -13,7 +13,7 @@ We use [Yarn](https://yarnpkg.com) for package managment (instead of NPM) becaus
 We use Webpack to manage our asset pipeline. Arguably, Webpack is overkill for this use-case, but we're using it here because once it's set up (which we've done for you), it's really easy to use. If you want to use an external script, just add it via Yarn, and reference it in main.js. You'll find instructions in the js/main.js file.
 
 ### PostCSS
-PostCSS is just CSS. You'll find `postcss.config.js` in the css folder. There you'll find that we're using [`postcss-import`](https://github.com/postcss/postcss-import) which allows us import css files directly from the node_modules folder, [`postcss-cssnext`](http://cssnext.io/features/) which gives us the power to use upcoming CSS features today.
+PostCSS is just CSS. You'll find `postcss.config.js` in the css folder. There you'll find that we're using [`postcss-import`](https://github.com/postcss/postcss-import) which allows us import css files directly from the node_modules folder, [`postcss-cssnext`](http://cssnext.io/features/) which gives us the power to use upcoming CSS features today. If you miss Sass you can find PostCss modules for those capabilities, too.
 
 
 ### Tachyons
@@ -22,4 +22,4 @@ This theme uses the [Tachyons CSS Library](http://tachyons.io/). It's about 15kb
 
 ## How to Use
 
-You'll find the commands to run in `src/package.json`. For development, cd into `src` and run `npm start` which will run webpack, processing both the postcss and scripts. For production, run `npm run build:production`.
+You'll find the commands to run in `src/package.json`. For development, cd into `src` and run `npm start` which will run webpack, processing both the postcss and scripts. For production, run `npm run build:production,` which will output minified versions of your files.