few more updates

Author: Andy McCormick

docs/development/addon-development-overview.md

@@ -177,9 +177,9 @@ TIP: Reference the [Extensions](development/extensions.md) section of the docs f
 The `Module/Actions` folder stores all the business logic for any actions that we are adding to ExpressionEngine with our add-on. Each action will have a separate file and corresponding class created based on information provided in the `$actions` array in the `upd` file.   
 Reference [Adding Actions](development/actions.md) for more information on creating URL endpoints (actions) with your add-on.
 
-### Control Panel Pages - `/Mcp`
-The `Mcp` folder contains all the Control Panel pages and sidebar we create for our add-on.    
-Reference [Adding Control Panel Pages](development/modules.md) for more information on adding Control Panel pages with your add-on.
+### Control Panel Routes - `/Mcp`
+The `Mcp` folder contains all the Control Panel routes and we create for our add-on as well as our sidebar.    
+Reference [Adding Control Panel Pages](development/modules.md) for more information on adding Control Panel routes and pages with your add-on.
 
 ### `Module/Tags`
 The `Module/Tags` folder stores all the business logic for any template tags we create with our add-on.    

docs/development/extensions.md

@@ -19,19 +19,21 @@ lang: php
 
 Within ExpressionEngine are what is known as "hooks"; little snippets of code in over 100 strategic places that allow the calling of third-party scripts that can rewrite and modify the inner workings of the program. By hooking into the core, you can do things like modify an entire Control Panel page, add/remove functionality, and modify the appearance of certain page elements. Hooks enable third party developers to modify aspects of ExpressionEngine without hacking the core.
 
-## Generate Our Extension Files
+## Creating Our Extension Files
 
 We can give our add-on the ability to hook into the core of ExpressionEngine by using the CLI:
 
 ```
 $ php system/ee/eecli.php make:extension-hook
+
 ```
 
-Follow the prompts to add an extension file to your add-on. 
 
 TIP: Files that interact with ExpressionEngine core hooks are referred to as "extensions" because they extend the functionality of ExpressionEngine.
 
-This will create an `ext[addon_name].php` file in our add-on along with an `Extensions` folder where we will build out the code we want to run when we interact with a core hook. Inside our `Extensions` folder the CLI will create a file with the same name as the core hook we plan to use.
+This will create an `ext.[addon_name].php` file in our add-on along with an `Extensions` folder where we will build out the code we want to run when we interact with a core hook. 
+
+Inside our `Extensions` folder the CLI will create a file with the same name as the core hook we plan to use.
 
 ```
 amazing_add_on
@@ -43,10 +45,6 @@ amazing_add_on
 
 TIP: A single add-on can interact with as many hooks as you want.
 
-## `ext.[addon_name].php`
-
-Prior to ExpressionEngine 6.4.0 and 7.2.0, all code that was used to hook into the core was placed in our `ext.[addon_name].php` file. However, now that file mainly just extends the `Extension` service and routes ExpressionEngine to reference the `Extensions` folder in our add-on.
-
 ## `AddonName/Extensions`
 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.
 
@@ -102,10 +100,40 @@ We know that we should expect the following parameters for this hook:
 We also know that we should be returning a string from our `process()` function.
 
 
-## Do Something
+## Do Something - Create An Extension Hook
 
 Let's do something with our hook to demonstrate how this would work. We're going to continue working with the `typography_parse_type_end()` hook by replacing "e" with "EE" everywhere in our templates (because EE is amazing!)
 
+Using the CLI to generate the extension hook:
+
+```
+$ php system/ee/eecli.php make:extension-hook
+Let's implement an extension hook!
+What is the extension hook name? Amazing Hook
+What add-on is the extension hook being added to? [amazing_add_on]:  amazing_add_on
+Building Extension hook.
+Extension hook created successfully!
+```
+This creates our `Extensions/TypographyParseTypeEnd.php` file for us. This file will initially look like this:
+
+```
+
+<?php
+
+namespace ExpressionengineDeveloper\AmazingAddOn\Extensions;
+
+use ExpressionEngine\Service\Addon\Controllers\Extension\AbstractRoute;
+
+class TypographyParseTypeEnd extends AbstractRoute
+{
+    public function process()
+    {
+    }
+}
+```
+
+All the functionality we want to include when our hook is executed needs to go inside our `process()` method. Here we are going to take the string passed in by the `TypographyParseTypeEnd()` core hook, replace all instances of `e` with `EE`, and then return the updated string.
+
 ```
 <?php
 

docs/development/modules.md

@@ -13,7 +13,7 @@ lang: php
 
 # Add Control Panel Pages To Your Add-On
 
-[TOC]
+[TOC=2-3]
 
 If you have ever used some of the add-ons that ship with ExpressionEngine such as [Block and Allow](/add-ons/blocklist.md) or [Pro Search](/add-ons/pro-search/overview.md), you will notice those add-ons have settings and configuration pages associated with them in the Control Panel. You add this functionality to your add-on using Control Panel Routes, also known as `Mcp` files. Whenever you add a Control Panel Route to your add-on using the CLI, an `Mcp` and `views` folder is automatically created for you, opening the door to creating your own Control Panel settings and pages.