reorganize info

jonschlinkert · jonschlinkert · commit 4eb44a14ea54 · 2017-06-20T13:28:49.000-04:00
diff --git a/.verb.md b/.verb.md
@@ -26,49 +26,49 @@ Visit toolkit.io (coming soon) for more information.
 Tookit applications are organized into the following categories:
 
 1. [building blocks](#building-blocks)
-1. [lifecycle](#lifecycle)
 1. [configuration](#configuration) 
+1. [lifecycle](#lifecycle)
 1. [automation](#automation) 
 
 
 ### Building blocks
 
 Create an "instant API" for your node.js application. These "building blocks" are used as 
 
-* [base][]: Bare-bones starting point for creating a high quality node.js application. Build out your API by using plugins like building blocks. All of other the applications in the toolkit suite were created using Base.
-* [templates][]: System for creating and managing template collections, and rendering templates with any node.js template engine. Can be used as the basis for creating a static site generator, blog framework, documentaton system, and so on.
+- [base][]: Bare-bones starting point for creating a high quality node.js application. Build out your API by using plugins like building blocks. All of other the applications in the toolkit suite were created using Base.
+- [templates][]: System for creating and managing template collections, and rendering templates with any node.js template engine. Can be used as the basis for creating a static site generator, blog framework, documentaton system, and so on.
 
 
-### Lifecycle
+### Configuration
 
-Developer frameworks and command line tools that address common phases of the software development lifecycle. Each of these tools can be used standalone, but they work even better together.
+Tools and conventions for defining, using and publishing declarative configurations for projects, components and templates.
 
 **Tools**
 
-1. [generate][]: create projects
-1. [assemble][]: build projects
-1. [verb][]: document projects
-1. [update][]: maintain projects
+- [boilerplate][]: Describes all of the necessary files, templates and settings required to initialize a complete, new project.
+- [scaffold][]: Describes all of the necessary files, templates and settings required to initialize a complete, new project.
+- [snippet][]: Tools and conventions for creating, using and publishing invidual snippets of code or text.
 
+**Synopsis**
 
-### Configuration
+By keeping a separation of concerns between configuration and everything else (application logic, flow control, etc), we can use _plain, generic javascript, with prescriptive conventions to describe commonly needed objects, files, templates, and assets_. 
 
-Tools and conventions for defining, using and publishing declarative configurations for projects, components and templates.
+As a result, projects are lower complexity, easier to maintain, and the objects can be passed around to any rendering engine, build system, scaffolding tool or project generator when its time to create or build something.
 
-**Tools**
 
-1. [boilerplate][]: Describes all of the necessary files, templates and settings required to initialize a complete, new project.
-1. [scaffold][]: Describes all of the necessary files, templates and settings required to initialize a complete, new project.
-1. [snippet][]: Tools and conventions for creating, using and publishing invidual snippets of code or text.
+### Lifecycle
 
-**Advantages**
+Developer frameworks and command line tools that address common phases of the software development lifecycle. Each of these tools can be used standalone, but they work even better together.
 
-By keeping a separation of concerns between configuration and everything else (application logic, flow control, etc), we can use plain, generic javascript, with prescriptive conventions to describe commonly needed objects, files, templates, and assets. 
+**Tools**
 
-As a result, projects are lower complexity, easier to maintain, and the objects can be passed around to any rendering engine, build system or project generator when its time to create something.
+- [generate][]: scaffold out new projects
+- [assemble][]: build projects
+- [verb][]: document projects
 
 
 ### Automation
 
-1. [enquirer][]: Plugin-based prompt system, to automate interactions and conversations with your users throughout the developer lifecycle.
-1. [microbot][]: Empower your applications and users with automated responses, actions and notifications throughout the developer lifecycle.
+- [enquirer][]: Plugin-based prompt system, to automate interactions and conversations with users.
+- [microbot][]: Empower your applications and users with automated responses, actions and notifications.
+- [update][]: Automate updates for virtually any aspect of a project.
diff --git a/README.md b/README.md
@@ -25,8 +25,8 @@ Visit toolkit.io (coming soon) for more information.
 Tookit applications are organized into the following categories:
 
 1. [building blocks](#building-blocks)
-2. [lifecycle](#lifecycle)
-3. [configuration](#configuration)
+2. [configuration](#configuration)
+3. [lifecycle](#lifecycle)
 4. [automation](#automation)
 
 ### Building blocks
@@ -36,37 +36,37 @@ Create an "instant API" for your node.js application. These "building blocks" ar
 * [base](https://github.com/node-base/base): Bare-bones starting point for creating a high quality node.js application. Build out your API by using plugins like building blocks. All of other the applications in the toolkit suite were created using Base.
 * [templates](https://github.com/jonschlinkert/templates): System for creating and managing template collections, and rendering templates with any node.js template engine. Can be used as the basis for creating a static site generator, blog framework, documentaton system, and so on.
 
-### Lifecycle
+### Configuration
 
-Developer frameworks and command line tools that address common phases of the software development lifecycle. Each of these tools can be used standalone, but they work even better together.
+Tools and conventions for defining, using and publishing declarative configurations for projects, components and templates.
 
 **Tools**
 
-1. [generate](https://github.com/generate/generate): create projects
-2. [assemble](https://github.com/assemble/assemble): build projects
-3. [verb](https://github.com/verbose/verb): document projects
-4. [update](https://github.com/update/update): maintain projects
+* [boilerplate](https://github.com/jonschlinkert/boilerplate): Describes all of the necessary files, templates and settings required to initialize a complete, new project.
+* [scaffold](https://github.com/jonschlinkert/scaffold): Describes all of the necessary files, templates and settings required to initialize a complete, new project.
+* [snippet](https://github.com/jonschlinkert/snippet): Tools and conventions for creating, using and publishing invidual snippets of code or text.
 
-### Configuration
+**Synopsis**
 
-Tools and conventions for defining, using and publishing declarative configurations for projects, components and templates.
+By keeping a separation of concerns between configuration and everything else (application logic, flow control, etc), we can use _plain, generic javascript, with prescriptive conventions to describe commonly needed objects, files, templates, and assets_.
 
-**Tools**
+As a result, projects are lower complexity, easier to maintain, and the objects can be passed around to any rendering engine, build system, scaffolding tool or project generator when its time to create or build something.
 
-1. [boilerplate](https://github.com/jonschlinkert/boilerplate): Describes all of the necessary files, templates and settings required to initialize a complete, new project.
-2. [scaffold](https://github.com/jonschlinkert/scaffold): Describes all of the necessary files, templates and settings required to initialize a complete, new project.
-3. [snippet](https://github.com/jonschlinkert/snippet): Tools and conventions for creating, using and publishing invidual snippets of code or text.
+### Lifecycle
 
-**Advantages**
+Developer frameworks and command line tools that address common phases of the software development lifecycle. Each of these tools can be used standalone, but they work even better together.
 
-By keeping a separation of concerns between configuration and everything else (application logic, flow control, etc), we can use plain, generic javascript, with prescriptive conventions to describe commonly needed objects, files, templates, and assets.
+**Tools**
 
-As a result, projects are lower complexity, easier to maintain, and the objects can be passed around to any rendering engine, build system or project generator when its time to create something.
+* [generate](https://github.com/generate/generate): scaffold out new projects
+* [assemble](https://github.com/assemble/assemble): build projects
+* [verb](https://github.com/verbose/verb): document projects
 
 ### Automation
 
-1. [enquirer](http://enquirer.io): Plugin-based prompt system, to automate interactions and conversations with your users throughout the developer lifecycle.
-2. [microbot](https://github.com/microbot/microbot): Empower your applications and users with automated responses, actions and notifications throughout the developer lifecycle.
+* [enquirer](http://enquirer.io): Plugin-based prompt system, to automate interactions and conversations with users.
+* [microbot](https://github.com/microbot/microbot): Empower your applications and users with automated responses, actions and notifications.
+* [update](https://github.com/update/update): Automate updates for virtually any aspect of a project.
 
 ## Author
 
@@ -82,4 +82,4 @@ Released under the [MIT License](LICENSE).
 
 ***
 
-_This file was generated by [verb-generate-readme](https://github.com/verbose/verb-generate-readme), v0.6.0, on June 01, 2017._
+_This file was generated by [verb-generate-readme](https://github.com/verbose/verb-generate-readme), v0.6.0, on June 20, 2017._
