updated headings

Author: Andy McCormick

docs/cli/creating-a-command.md

@@ -9,7 +9,7 @@ You can also build your own commands that will enable users to interact with you
 
 NOTE:Before adding a custom CLI Command to your add-on, you need to already have an add-on in place. See [Building An Add-On: Getting Started](development/addon-development-overview.md#getting-started) for how to generate the starter files for your add-on.
 
-## Generate Our Add-on
+## Creating An Amazing Command
 We add custom commands to the CLI when our add-on is installed by using the CLI.
 
 ```
@@ -26,16 +26,6 @@ amazing_add_on
  ┃ ┣ Command[CommandName].php
 ```
 
-## `addon.setup.php`
-
-We see that the CLI has added our `Commands` folder and created our new class. However, the CLI has also modified our `addon.setup.php` file as well.
-
-```
-amazing_add_on
- ┣ Commands
- ┃ ┣ CommandAnAmazingCommand.php
-```
-
 CLI Commands are installed through an add-on's `addon.setup.php` file. The CLI takes care of this for us. We can see here that CLI creates the `$commands` array inside the array that gets returned from our `addon.setup.php` file.
 
 ```
@@ -61,7 +51,7 @@ return [
 
 Now when our add-on is installed, users will have access to our new command.
 
-## `\Commands\Command[CommandName]`
+## Anatomy of a Command - `/Commands/Command[CommandName]`
 Inside of our add-on we now have a file named with our command's name (in PascalCase).
 
 In this example we have created a new command named "An Amazing Command" to our Amazing Add-on:
@@ -124,11 +114,6 @@ class CommandAnAmazingCommand extends Cli
 }
 ```
 
-
-## Anatomy of a Command
-
-Creating commands is simple. Each commands is built in a similar way as part of a custom add-on:
-
 ### Class Structure
 
 Your class can have any name, and should be namespaced to your addon. When creating your class, make sure to include:

docs/development/actions.md

@@ -16,7 +16,7 @@ Actions in ExpressionEngine are URL endpoints that are reached with the `ACT` qu
 
 NOTE:Before adding an action to your add-on, you need to already have an add-on in place. See [Building An Add-On: Getting Started](development/addon-development-overview.md#getting-started) for how to generate the starter files for your add-on.
 
-## How To Build An Amazing Action?
+## Creating An Amazing Action
 To generate an action we use the CLI to add the action to our existing add-on named "Amazing Add-on".
 
 ```
@@ -90,7 +90,7 @@ On creation of an action, you can also specify to add it to the database after t
 
 
 
-## AddonName/Module/Actions
+## Anatomy of An Action
 
 Once we've added an action to our add-on, an `Actions` folder is created inside our add-on's `Module` folder. The CLI will generate a class and respective file for us based on the action name we passed to the CLI when creating our action. In this case we added an action named  "ExampleAction" to Amazing Add-on.
 
@@ -174,7 +174,7 @@ $ php system/ee/eecli.php make:action --csrf_exempt
 
 
 
-## Do Something
+## Do Something - Build An Action
 
 Let's do something with our action to demonstrate how this would work. 
 

docs/development/add-on-update-file.md

@@ -9,8 +9,12 @@
 
 # Add-on Update File
 
+## Overview
+
 The `upd.[addon_name].php` file (commonly just called the `upd` file) is critical to ExpressionEngine knowing what to do with your add-on. Here we tell ExpressionEngine what actions to register, core hooks we want to use, database tables to update, and much more. We need to tell ExpressionEngine what to do when we install an add-on, update an add-on, and uninstall and add-on. Thankfully the CLI takes care of most of this for us. 
 
+TIP:When using the CLI, your add-on update file will automatically be created for you. See [Building An Add-On: Getting Started](development/addon-development-overview.md#getting-started) for how to generate the starter files for your add-on.
+
 ## Initial Setup
 
 When you first create your add-on using the [`make:addon`](/cli/built-in-commands/make-addon.md) command from the CLI, a `upd` file is created for you in the root of your add-on.

docs/development/addon-setup-php-file.md

@@ -15,9 +15,14 @@ lang: php
 
 [TOC]
 
+## Overview
+
 Starting with version 3.0 each add-on in ExpressionEngine must have an `addon.setup.php` file in its package directory. This file provides descriptive data about a specific add-on, such as author, name, and version. Below we walk through the format and available keys. However, most of the time, the CLI will take care of generating and updating this file as needed for you.
 
-## Format
+
+TIP:When using the CLI, your add-on setup file will automatically be created for you. See [Building An Add-On: Getting Started](development/addon-development-overview.md#getting-started) for how to generate the starter files for your add-on.
+
+## Anatomy Of The Add-On Setup File
 
 The file must return an associative array. For example:
 

docs/development/custom-template-tags.md

@@ -23,7 +23,7 @@ Creating your own custom template tags allows you to display dynamic data from y
 
 NOTE:Before adding a template tag to your add-on, you need to already have an add-on in place. See [Building An Add-On: Getting Started](development/addon-development-overview.md#getting-started) for how to generate the starter files for your add-on.
 
-## Creating Template Tags
+## Creating An Amazing Template Tag
 Tags are created via the CLI by using the `make:template-tag` command. 
 
 ```
@@ -42,7 +42,10 @@ amazing_add_on
  ┗ ...
  ```
 
-## `class [TagName]`
+## Anatomy of A Template Tag
+
+**class** `class [TagName]`
+
 Inside `Modules/Tags/ExampleTag.php` we see the following code generated for us:
 
 ```
@@ -139,7 +142,7 @@ This would render in the browser as:
 Here is some amazing text: ExpressionEngine is the best CMS in the world!
 ```
 
-## Creating Tag Pair Template Tags
+## Do Something - Create A Tag Pair Template Tag
 
 Often you will want to process content contained between a pair of tags. Let's create a simple tag that makes text bold to illustrate how this is done. Our example plugin will have this syntax:
 
@@ -182,11 +185,13 @@ class Bold extends AbstractRoute
 
 ```
 
+Now We need to capture the content between our opening and closing tags, and return that context as bold text. In ExpressionEngine, this is called fetching tagdata.
+
 
 ### Fetching Tagdata
 In our class, we use `ee()->TMPL->tagdata;` to capture the template data that is between our opening and closing tag.
 
-In this example we will capture the text we want to make bold in our template and render it back to the browser.
+Let's update our example to capture the text we want to make bold in our template and render it back to the browser.
 
 Our tag's class:
 
@@ -215,7 +220,7 @@ We want to bold <b>this text</b>.
 
 As you can see, any template data between our opening and closing tags is captured using `ee()->TMPL->tagdata`.
 
-## Parameters
+## Do Something - Create A Template Tag With Parameters
 Both single tags and tag pairs can accept parameters. The template engine makes it easy to fetch them using the following variable:
 
     ee()->TMPL->fetch_param('param_name');
@@ -277,7 +282,7 @@ class format extends AbstractRoute
 
 ```
 
-## Variables
+## Using Variables In Your Template Tag
 With variables, we can take our tag a step further. Imagine that you have tag pair that you want to use to return data based on some parameters. We can do that using variables inside of our tag.
 
 We all know and love [`{exp:channel:entries}`](channels/entries.md). We use the Channel Entries tag by opening and closing the tag, passing some parameters, and then placing some template tags in our template that we know the tag will replace when rendered. 
@@ -294,7 +299,7 @@ This typically looks something like this:
 In the snippet above, we're passing in the `channel` and `limit` as parameters. We're then expecting the Channel Entries tag to replace the `{title}` and `{body}` **variables** when the tag is parsed. Now, let's do something similar to our add-on.
 
 
-## Create A Tag With Variables
+## Do Something - Create A Tag With Variables
 Let's add a tag to our add-on that will render the current date and time. The user can pass in their timezone and the tag will return the current Date and time.
 
 First, generate the tag (we're calling our tag "date and time" and adding it to our Amazing Add-On):

docs/development/extensions.md

@@ -21,7 +21,7 @@ Within ExpressionEngine are what is known as "hooks"; little snippets of code in
 
 NOTE:Before adding an extension hook to your add-on, you need to already have an add-on in place. See [Building An Add-On: Getting Started](development/addon-development-overview.md#getting-started) for how to generate the starter files for your add-on.
 
-## Creating Our Extension Files
+## Creating An Amazing Extension
 
 We can give our add-on the ability to hook into the core of ExpressionEngine by using the CLI:
 
@@ -47,7 +47,7 @@ amazing_add_on
 
 TIP: A single add-on can interact with as many hooks as you want.
 
-## `AddonName/Extensions`
+## Anatomy Of An Extension
 Once we've added the ability to hook into the core with our add-on, an `Extensions` folder is created. The CLI will generate a class and a respective file for each core hook we wish to use.
 
 Here we have added the ability to interact with the [`typography_parse_type_end()`](/development/extension-hooks/global/typography.html#typography_parse_type_endstr-this-prefs) hook.

docs/development/fieldtypes/fieldtypes.md

@@ -22,7 +22,7 @@ TIP: For an overview of what a Fieldtype is, read the [Fieldtype Overview docs](
 
 NOTE:Before adding a fieldtype to your add-on, you need to already have an add-on in place. See [Building An Add-On: Getting Started](development/addon-development-overview.md#getting-started) for how to generate the starter files for your add-on.
 
-## Creating A Custom Fieldtype
+## Creating An Amazing Fieldtype
 
 Adding a custom fieldtype to your add-on is easy with the `make:fieldtype` command. 
 
@@ -44,7 +44,9 @@ amazing_add_on
 ┗ ...
  ```
 
-## Basic Fieldtype File Structure
+## Anatomy of A Fieldtype
+
+[TOC=3]
 
 All fieldtypes must inherit from the `EE_Fieldtype` base class and they must provide an `$info` array with a name and version number.
 
@@ -78,9 +80,6 @@ NOTE: **Note:** Fieldtypes can declare their compatibility with other Fieldtypes
 NOTE: We also have [Example fieldtype with annotations](development/fieldtypes/example.md) for your reference.
 
 
-## Development Reference
-
-[TOC=3]
 
 ### Class Variables
 
@@ -573,6 +572,6 @@ A jQuery object of the field being affected by the current event is passed to th
 
 NOTE: **Note:** Please refer to [Enhanced Fieldtype Features](development/fieldtypes/enhanced.md) page for advanced topics, such ad working with Live Preview, Entry Manager, Entry Cloning, File Picker and Conditional Fields.
 
-## Do Something: Build A Fieldtype
+## Do Something - Build A Fieldtype
 
 For a complete fieldtype example see the [Google Maps Fieldtype example](/development/fieldtypes/example.md).

docs/development/modules.md

@@ -1,4 +1,4 @@
-0---
+---
 lang: php
 ---
 
@@ -22,7 +22,7 @@ NOTE:**NOTE:** Control Pages are what is rendered in the browser when visiting y
 
 NOTE:Before adding a Control Panel route to your add-on, you need to already have an add-on in place. See [Building An Add-On: Getting Started](development/addon-development-overview.md#getting-started) for how to generate the starter files for your add-on.
 
-## Generate Your Route
+## Creating An Amazing Control Panel Route
 
 If your add-on doesn't already have the required `Mcp` and `views` files, you can add a route to your add-on using the `make:mcp-route` command in the CLI.
 
@@ -37,7 +37,7 @@ This will create an `mcp.[addon_name].php` file in your add-on along with a `Mcp
 Inside of the `Mcp` folder, you will see that the CLI has created your first control route with `Mcp/Index.php` and a corresponding view in you `views` folder. This page is accessible via The Add-On Manager -> [Add-On Name] or via the `/admin.php?/cp/addons/settings/[add-on-name]` URL.
 
 
-## Your First Control Panel Page
+## Anatomy Of A Control Panel Route
 When you first add a route to your add-on an `Mcp` folder along with an `Mcp/Index.php` starter file is created. The starter file will look something like this:
 
 ```

docs/development/prolets.md

@@ -20,7 +20,7 @@ Here is an example of the add-on SEEO's prolet, which easily allows editors to e
 
 NOTE:Before adding a Prolet to your add-on, you need to already have an add-on in place. See [Building An Add-On: Getting Started](development/addon-development-overview.md#getting-started) for how to generate the starter files for your add-on.
 
-## Creating A Prolet
+## Creating An Amazing Prolet
 
 Creating a Prolet is straightforward using the `make:prolet` command in the CLI.
 
@@ -40,7 +40,7 @@ amazing_add_on
 ```
 
 
-## Prolet File Structure
+## Anatomy Of A Prolet
 
 Inside a prolet file, you are required to define the prolet class. The class name should consist of prolet name with the first letter capitalized followed by `_pro` postfix. So for the example above, the class name will be `Sample_prolet_pro`.
 
@@ -68,7 +68,6 @@ class Amazing_add_on_pro extends AbstractProlet implements ProletInterface
 }
 ```
 
-## Properties and Methods
 
 ### Icon
 On each page load, prolets appear on the front-end as Dock buttons. If not specified otherwise, `icon.svg` from the add-on package folder is used as the Dock button. If you want to specify a different icon to use from the add-on's folder, you can do that using `protected $icon` property or `public function getIcon()`.

docs/development/tab-files.md

@@ -14,6 +14,7 @@ lang: php
 
 # Adding Publish Layout Tabs
 
+[TOC]
 
 ## Overview
 Add-ons can also add tabs which are visible on in [Publish Layouts](control-panel/channels.md#publish-layouts). Respectivley these tabs would also be visible on the Entry Publish/Edit page if selected in the publish layout. Two things are required for your add-on to have this functionality:
@@ -25,7 +26,7 @@ Here is an example of the publish layout's tab for the Structure add-on:
 
 NOTE:Before adding a tab to your add-on, you need to already have an add-on in place. See [Building An Add-On: Getting Started](development/addon-development-overview.md#getting-started) for how to generate the starter files for your add-on.
 
-## Creating The Tab File
+## Creating An Amazing Tab File
 Tab files are not currently able to be generated through the CLI, thus you will need to manually create the file `tab.[addon_name].php` in the root of your add-on's folder.
 
 ```
@@ -35,7 +36,7 @@ amazing_add_on
 ┗...
 ```
 
-## The Tab File Structure
+## Anatomy Of A Tab File
 
 ```
 <?php