Update README

Author: chasegiunta

README.md

@@ -5,6 +5,7 @@ All the power of Vue CLI's scaffolding & single file components tailored for a C
 ## What's Included
 
 - `npm run dev` / `yarn dev`: first-in-class development experience.
+
   - Webpack + `vue-loader` for single file Vue components
   - State preserving hot-reload
   - Page reloading on file edits (twig, html, etc)
@@ -21,25 +22,23 @@ All the power of Vue CLI's scaffolding & single file components tailored for a C
 
 ### Fork It And Make Your Own
 
-You should fork this repo to create your own boilerplate. This scaffold makes no assumptions about pre-processor, babel, or linting configurations.
+You should fork this repo to create your own boilerplate. This scaffold makes no assumptions about pre-processors used or linting configurations.
 
 I've also created a [fork of this boilerplate](https://github.com/chasegiunta/craft-vue-tailwind) that integrates TailwindCSS & Purgecss.
 
 ## Setup
 
 This boilerplate requires Vue CLI 3 be [installed globally on your machine](https://cli.vuejs.org/guide/installation.html).
 
-
-
-``` bash
+```bash
 # create & install project
 composer create-project chasegiunta/craft-vue PATH
 
 # run Craft's setup & install
 ./craft setup
 
-# install the Asset Rev plugin
-./craft install/plugin assetrev
+# install the Twigpack plugin
+./craft install/plugin twigpack
 
 # install dependencies
 npm install # yarn
@@ -57,26 +56,31 @@ You can also run your `dev` & `build` tasks from the GUI to get valuable build s
 
 **NOTE:** During development, _only your assets_ will be served from `localhost:8080` and referenced in the base template. You'll still load your site locally under your normal development domain (mysite.test, etc.). This will also cause a brief unstyled flash on page loads due to JS/CSS assets loading from javascript for development. **This flash isn't present after build, on production**.
 
-After running `npm run build`, the easiest way to test your build files locally is to comment the environment variable in your `.env` file, and refresh the page. This will serve your assets from the build directory, rather than webpack's dev server.
+If webpack's dev server (`yarn dev`) is not running, Twigpack will serve your assets from the build directory.
 
 For a detailed explanation on how things work, check out the [Vue CLI docs](https://cli.vuejs.org/).
 
 ## Pre-Processors
 
 This boilerplate has pre-configured CSS extraction for most popular CSS pre-processors including LESS, SASS, Stylus, and PostCSS. To use a pre-processor, all you need to do is install the appropriate webpack loader for it. For example, to use SASS:
-``` bash
+
+```bash
 npm install sass-loader node-sass --save-dev
 # yarn add sass-loader node-sass --dev
 ```
+
 Note you also need to install node-sass because sass-loader depends on it as a peer dependency.
 
 Read more about this at https://cli.vuejs.org/guide/css.html#pre-processors
 
 ## Automatic Component Registration
-Any vue components placed within `src/components` will be registered with Vue automatically. **This requires their filenames to be in PascalCase**, eg. MyVueComponent.vue
+
+Any vue components placed within `src/components` will be registered with Vue automatically. You may nest these in subfolders if you wish.
 
 ## Babel Compiling
+
 This boilerplate uses babel-preset-env for configuring babel. [You can read more about it here.](https://cli.vuejs.org/config/#babel)
 
 ## Linting
+
 You can enable linting by adding the `@vue/cli-plugin-eslint` plugin through the GUI `vue ui`.