From 0b65b6110b303022be805e6f7eebd01c35f29ea1 Mon Sep 17 00:00:00 2001 From: Qa'id Jacobs Date: Mon, 27 Jul 2015 11:40:34 +0200 Subject: [PATCH] Fix small grammar issues Just a couple of minor things to make your project even more awesome than it already is. --- src/views/docs/getting-started/working-with-fabricator.html | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/src/views/docs/getting-started/working-with-fabricator.html b/src/views/docs/getting-started/working-with-fabricator.html index 3023448..9994f5b 100644 --- a/src/views/docs/getting-started/working-with-fabricator.html +++ b/src/views/docs/getting-started/working-with-fabricator.html @@ -30,7 +30,7 @@ ## Directories -All work is done in`src` directory. Inside you'll find a the following directories: +All work is done in`src` directory. Inside you'll find the following directories: ``` └── src @@ -53,7 +53,7 @@ ### Materials -By default, Fabricator defines a simple UI taxonomy of "components" and "structures" - components are the smallest unit of UI, and structures are two or components combined. This is a simple, reasonable taxonomy will work in many cases, however, you are free to define your own taxonomy. To do so, rename/create new directories in the `materials` directory as needed. For example, toolkit that follows [Atomic Design](http://bradfrost.com/blog/post/atomic-web-design/) might look like: +By default, Fabricator defines a simple UI taxonomy of "components" and "structures" - components are the smallest unit of UI, and structures are two or more components combined. This is a simple, reasonable taxonomy will work in many cases, however, you are free to define your own taxonomy. To do so, rename/create new directories in the `materials` directory as needed. For example, toolkit that follows [Atomic Design](http://bradfrost.com/blog/post/atomic-web-design/) might look like: ``` └── materials @@ -78,7 +78,7 @@ ### toolkit -By default, Fabricator defines almost no architecture. Those decision are best made by you, the developer. Inside of `src/assets/toolkit` you'll find a single `.scss` and `.js` file. Both are entry points for Sass and Browserify, respectively. It is recommended that you compile your toolkit to a single `.js` and `.css` file to increase portability. The Gulp tasks for both stylesheets and scripts is setup to give you all the power of Sass and Browserify to help achieve this. +By default, Fabricator defines almost no architecture. Those decisions are best made by you, the developer. Inside of `src/assets/toolkit` you'll find a single `.scss` and `.js` file. Both are entry points for Sass and Browserify, respectively. It is recommended that you compile your toolkit to a single `.js` and `.css` file to increase portability. The Gulp tasks for both stylesheets and scripts is setup to give you all the power of Sass and Browserify to help achieve this. ### f.js and f.css