Using the term "Base" instead of "Simple" (vuejs#1520)

* simple -> base

* clarify template

* undo prettier formatting

Author: sdras

src/v2/cookbook/adding-instance-properties.md

@@ -4,7 +4,7 @@ type: cookbook
 order: 2
 ---
 
-## Simple Example
+## Base Example
 
 There may be data/utilities you'd like to use in many components, but you don't want to [pollute the global scope](https://github.com/getify/You-Dont-Know-JS/blob/master/scope%20%26%20closures/ch3.md). In these cases, you can make them available to each Vue instance by defining them on the prototype:
 

src/v2/cookbook/creating-custom-scroll-directives.md

@@ -4,7 +4,7 @@ type: cookbook
 order: 7
 ---
 
-## Simple Example
+## Base Example
 
 There are many times that we might want to add a bit of behavior, especially animation, to a scroll event on a site. There are many ways to do so, but the path with the least amount of code and dependencies is perhaps to use a [custom directive](https://vuejs.org/v2/guide/custom-directive.html) to create a hook for anything that fires off a particular scroll event.
 

src/v2/cookbook/form-validation.md

@@ -4,7 +4,7 @@ type: cookbook
 order: 3
 ---
 
-## Simple Example
+## Base Example
 
 Form validation is natively supported by the browser, but sometimes different browsers will handle things in a manner which makes relying on it a bit tricky. Even when validation is supported perfectly, there may be times when custom validations are needed and a more manual, Vue-based solution may be more appropriate. Let's begin with a simple example.
 

src/v2/cookbook/index.md

@@ -35,32 +35,34 @@ Recipes should generally:
 > * Explain the pros and cons of your strategy, including when it is and isn't appropriate
 > * Mention alternative solutions, if relevant, but leave in-depth explorations to a separate recipe
 
-### Simple Example
+We request that you follow the template below. We understand, however, that there are times when you may necessarily need to deviate for clarity or flow. Either way, all recipes should at some point discuss the nuance of the choice made using this pattern, preferably in the form of the alternative patterns section.
+
+### Base Example
 
 _required_
 
-1. Articulate the problem in a sentence or two.
-2. Explain the simplest possible solution in a sentence or two.
-3. Show a small code sample.
-4. Explain what this accomplishes in a sentence.
+1.  Articulate the problem in a sentence or two.
+2.  Explain the simplest possible solution in a sentence or two.
+3.  Show a small code sample.
+4.  Explain what this accomplishes in a sentence.
 
 ### Details about the Value
 
 _required_
 
-1. Address common questions that one might have while looking at the example. (Blockquotes are great for this)
-2. Show examples of common missteps and how they can be avoided.
-3. Show very simple code samples of good and bad patterns.
-4. Discuss why this may be a compelling pattern. Links for reference are not required but encouraged.
+1.  Address common questions that one might have while looking at the example. (Blockquotes are great for this)
+2.  Show examples of common missteps and how they can be avoided.
+3.  Show very simple code samples of good and bad patterns.
+4.  Discuss why this may be a compelling pattern. Links for reference are not required but encouraged.
 
 ### Real-World Example
 
 _required_
 
 Demonstrate the code that would power a common or interesting use case, either by:
 
-1. Walking through a few terse examples of setup, or
-2. Embedding a codepen/jsfiddle example
+1.  Walking through a few terse examples of setup, or
+2.  Embedding a codepen/jsfiddle example
 
 If you choose to do the latter, you should still talk through what it is and does.
 

src/v2/cookbook/unit-testing-vue-components.md

@@ -4,7 +4,7 @@ type: cookbook
 order: 6
 ---
 
-## Simple Example
+## Base Example
 
 Unit testing is a fundamental part of software development. Unit tests execute the smallest units of code in isolation, in order to increase ease of adding new features and track down bugs. Vue's [single-file components](../guide/single-file-components.html) make it straight forward to write unit tests for components in isolation. This lets you develop new features with confidence you are not breaking existing ones, and helps other developers understand what your component does.
 

src/v2/cookbook/using-axios-to-consume-apis.md

@@ -4,7 +4,7 @@ type: cookbook
 order: 9
 ---
 
-## Simple Example
+## Base Example
 
 There are many times when building application for the web that you may want to consume and display data from an API. There are several ways to do so, but a very popular approach is to use [axios](https://github.com/axios/axios), a promise-based HTTP client.