starting grammar cleanup

Author: Andy McCormick

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

@@ -7,15 +7,15 @@
     @license   https://expressionengine.com/license Licensed under Apache License, Version 2.0
 -->
 
-# Add-on Update File `upd.[addon_name].php`
+# Add-on Update File
 
-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 and add-on, update an add-on, and uninstall and add-on. Thankfully the CLI takes care of most of this for us. 
+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. 
 
 ## 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.
 
-Here I have created an Amazing Add-on which currently has a module and has some extensions that interact with the core hooks.
+Here I have created an add-on called Amazing Add-on using the CLI.
 
 ```
 <?php
@@ -64,7 +64,7 @@ The first thing you will notice in our `Amazing_add_on_upd` class is a list of p
 ```
 
 ## Install Your Add-On (`install()`)
-The CLI automatically generates our install method. This method will ensure that all extensions and actions declared above will be properly installed. If you just need to install actions and/or extensions, then you can leave this method as is. Otherwise use this section to add tabs to saved [publish layouts](), update the database, or do something else when the add-on is installed.
+The CLI automatically generates our install method. This method will ensure that all extensions and actions declared above will be properly installed. If you only need to install actions and/or extensions, then you can leave this method as is. Otherwise, use this section to add tabs to saved [publish layouts](), update the database, or do something else when the add-on is installed.
 
 
 | Parameter | Type      | Description                                             |
@@ -98,7 +98,7 @@ Optionally add the publish page tab fields to any saved publish layouts. This is
 | --------- | ------- | ------------------------------------------------ |
 | Returns   | `Array` | Associative array of the tab name and tab fields |
 
-An optional function, included only if your add-on adds a tab to the publish page. This function should return an multidimensional associative array, the top array key consisting of the tab name, followed by any field names, with each field having a variety of default settings. Note that when the fields are added to the publish page, they are namespaced to prevent variable collisions:
+An optional function included only if your add-on adds a tab to the publish page. This function should return a multidimensional associative array: the top array key consisting of the tab name, followed by any field names, with each field having a variety of default settings. Note that when the fields are added to the publish page, they are namespaced to prevent variable collisions:
 
     function tabs()
     {
@@ -127,7 +127,7 @@ Be sure that you also update your [`install()` function](#adding-publish-tabs) t
 
 
 ## Update Your Add-on (`update()`)
-The `update` method is will run code when a user installs an update to our add-on. 
+The `update` method will run code when a user installs an update to our add-on. 
 
 | Parameter | Type      | Description                                                        |
 | --------- | --------- | ------------------------------------------------------------------ |

docs/development/addon-development-overview.md

@@ -9,9 +9,9 @@
 
 # Add-on Development Overview
 
-With custom add-ons you can add new fieldtypes, features, template tags, and much more to ExpressionEngine. Here we are going to look at the different parts of an add-on and how to define just what our add-on is going to do.
+With custom add-ons you can add new fieldtypes, features, template tags, and much more to ExpressionEngine. Here we are going to look at different parts of an add-on, and how to define just what our add-on is going to do.
 
-TIP: In this section we're explaining the parts of an add-on. No need to memorize everything though, the [CLI](/cli/intro.html) will generate all the pieces we need based on what functions we want our add-on to have.
+TIP: In this section, we're explaining the parts of an add-on. No need to memorize everything though, the [CLI](/cli/intro.html) will generate all the pieces we need based on what functions we want our add-on to have.
 
 [TOC]
 
@@ -21,18 +21,18 @@ While ExpressionEngine offers a lot of functionality right out of the box, somet
 Here are some ideas of what you can accomplish with a custom add-on:
 
 - Add custom [template tags](development/custom-template-tags.md) like `{exp:amazing_add_on:member_info}`.
-- Run functions or return data when someone reaches a certain URL using [URL endpoints (called Actions)](development/actions.md).
+- Run functions or return data when someone reaches a specific URL using [URL endpoints (called Actions)](development/actions.md).
 - Add custom [fieldtypes](development/fieldtypes/fieldtypes.md) for content editors when creating channel entries.
 - Add custom [CLI commands](cli/creating-a-command.md) like `$ eecli.php amazing_add_on:do_something_amazing`
 - Add custom [Publish Form tabs](development/tab-files.md) to help organize entry fields for content editors.
 - Hook into ExpressionEngine and run [custom functions (called Extensions)](development/extensions.md) when ExpressionEngine does certain actions, like emailing your team whenever a post is created or manipulating text when a template is rendered. 
-- Display information from from your add-on to content editors on the front-end by adding a [Prolet](/development/prolets.md) to the [ExpressionEngine Dock](/advanced-usage/front-end/dock.md).
+- Display information from your add-on to content editors on the front-end by adding a [Prolet](/development/prolets.md) to the [ExpressionEngine Dock](/advanced-usage/front-end/dock.md).
 - Display information in the [Control Panel Dashboard](/control-panel/dashboard_management.md) using a [custom Dashboard Widget](/development/widgets.md).
 
 These are just a few ideas of what you can do with custom add-ons. The possibilities are almost endless. 
 
 ## Getting Started
-Getting started making your own add-on is incredibly easy with the CLI. To begin making an add-on simply use the `make:addon` command from the [CLI](/cli/intro.html). 
+Getting started making an add-on is incredibly easy with the CLI. To begin making an add-on simply, use the `make:addon` command from the [CLI](/cli/intro.html). 
 
 ```
 $ php system/ee/eecli.php make:addon
@@ -64,26 +64,26 @@ amazing_add_on/
 ┗ upd.amazing_add_on.php
 ```
 
-This is the starting point of an add-on and is enough to begin creating template tags, extension hooks, and much more! From here you can add more functionality to your add-on depending on your needs. 
+This is the starting point of an add-on and is enough to begin creating template tags, extension hooks, and much more! From here, you can add more functionality to your add-on depending on your needs. 
 
-Here's a list of functionality that can be added to your add-on:
+Here's a list of functionality that can be added to your add-on and the corresponding CLI command if applicable:
 
-- [Extension hooks](development/extensions.md)
-- [Control Panel Pages](development/modules.md)
-- [Actions](development/actions.md)
-- [Fieldtypes](development/fieldtypes/fieldtypes.md)
-- [CLI Commands](cli/creating-a-command.md)
-- [Template Tags](development/custom-template-tags.md)
+- [Extension hooks (`make:extension-hook`)](development/extensions.md)
+- [Control Panel Pages (`make:mcp-route`)](development/modules.md)
+- [Actions (`make:action`)](development/actions.md)
+- [Fieldtypes (`make:fieldtype`)](development/fieldtypes/fieldtypes.md)
+- [CLI Commands (`make:command`)](cli/creating-a-command.md)
+- [Template Tags (`make:template-tag`)](development/custom-template-tags.md)
 - [Language Files](development/add-on-language-files.md)
 - [Publish Form Tabs](development/tab-files.md)
-- [Prolets](development/prolets.md)
-- [Dashboard Widgets](development/widgets.md)
+- [Prolets (`make:prolet`)](development/prolets.md)
+- [Dashboard Widgets (`make:widget`)](development/widgets.md)
 
 Continue reading below to understand all the files and folders found in the structure of an add-on.
 
 ## Add-On Structure
 
-Below is the complete structure of an add-on that we'll call "Amazing Add-on". There's a lot in this structure, because this add-on can do a lot of things (it's amazing 😀)! Don't worry though, your add-on can be as simple or complex as you want to make it. This example just shows all the possibilities. Continue reading as we break down the parts of this add-on.
+Below is the complete structure of an add-on that we'll call "Amazing Add-on". There's a lot in this structure because this add-on can do many things (it's amazing 😀)! Don't worry though; your add-on can be as simple or complex as you want to make it. This example just shows all the possibilities. Continue reading as we break down the parts of this add-on.
 
 ```
 amazing_add_on
@@ -126,17 +126,17 @@ amazing_add_on
  ┗ upd.amazing_add_on.php
  ```
 
-NOTE: **Note:** Pay attention to how these filenames are structured. For filenames, hyphens and special characters are removed and spaces are replaced with underscores.
+NOTE: **Note:** Pay attention to how these filenames are structured. For filenames, hyphens and special characters are removed, and spaces are replaced with underscores.
 
 
 ### The Add-on Setup File (`addon.setup.php`)
-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.   
-Reference the [The Add-on Setup File](development/addon-setup-php-file.md) for more information on the contents of this file.
+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.   
+Reference [The Add-on Setup File](development/addon-setup-php-file.md) for more information on the contents of this file.
 
 ### The Update File (`upd.[addon_name].php`)
 **class `Add_on_name_upd extends Installer`**        
 The Update file for an add-on includes a class with a name that is a combination of the add-on's name with a `_upd` suffix. Here you define functionality that should be executed on installation, update, and uninstallation of your add-on.     
-Reference the [The Add-on Update File](development/add-on-update-file.md) for more information on this file.
+Reference [The Add-on Update File](development/add-on-update-file.md) for more information on this file.
 
 
 ### The Extension File (`ext.[addon_name].php`)
@@ -151,54 +151,54 @@ Reference [Adding Fieldtypes](development/fieldtypes/fieldtypes.md) for more inf
 
 ### The Mcp File (`mcp.[addon_name].php`)
 **class `Add_on_name_upd extends Mcp`**    
-The Mcp file is used to route ExpressionEngine to our `Mcp` Folder which contains logic for your Control Panel pages (settings or other pages you might want to add to the Control Panel for your users to interact with).    
+The Mcp file is used to route ExpressionEngine to our `Mcp` Folder, which contains logic for your Control Panel pages (settings or other pages you might want to add to the Control Panel for your users to interact with).    
 Reference [Adding Control Panel Pages](development/modules.md) for more information on adding Control Panel pages with your add-on.
 
 ### The Module File `mod.[addon_name].php`
 **class `Add_on_name_upd extends Module`**    
-The module file is used to route ExpressionEngine to our `Modules` Folder which contains any actions or template tags you are adding with your add-on.    
+The module file is used to route ExpressionEngine to our `Modules` Folder, which contains any actions or template tags you are adding with your add-on.    
 Reference [Adding Template Tags](development/custom-template-tags.md) for more information on adding template tags with your add-on or [Adding Actions](development/actions.md) for more information on creating URL endpoints (actions) with your add-on.
 
 ### The Tab File (`tab.[addon_name].php`)
 **class `Module_name_tab`**    
-The tab file is used to create 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.    
+The tab file is used to create tabs that are visible in [Publish Layouts](control-panel/channels.md#publish-layouts). Respectively, these tabs would also be visible on the Entry Publish/Edit page if selected in the publish layout.    
 Reference [Adding Publish Form Tabs](development/tab-files.md) for more information on adding Publish Form Tabs with your add-on.
 
 ### The Prolet File `pro.[addon_name].php`
 **class `Add_on_name_upd extends AbstractProlet implements ProletInterface`**    
-The prolet file is used to create new [Prolets](/development/prolets.md) with our add-on.    
+The Prolet file is used to create new [Prolets](/development/prolets.md) with our add-on.    
 Reference [Adding Prolets](development/prolets.md) for more information on adding prolets to your add-on.
 
 ### The Add-on Icon File `icon.svg`
 The add-on icon folder is used both in the Add-on Manager and in the Dock on the front-end to distinguish your add-on from others.
 
 ### `/Extensions`
-When we tell the CLI that we want to create an extension, classes are automatically created in the `Extensions` folder along with the above mentioned `ext.[addon_name].php` file. Interacting with hooks allow us to extend ExpressionEngine's functionality, thus we refer to these as "extensions". 
+When we tell the CLI that we want to create an extension, classes are automatically created in the `Extensions` folder along with the above mentioned `ext.[addon_name].php` file. Interacting with hooks allows us to extend ExpressionEngine's functionality, thus we refer to these as "extensions". 
 
 TIP: Reference the [Extensions](development/extensions.md) section of the docs for more information on using extensions in your add-on.
 
 ### `Module/Actions`
-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 information provided in the `$actions` array in the `upd` file.
+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.
 
 ### `Module/Tags`
-The `Module/Tags` folder stores all the business logic for any template tags we are creating with our add-on. 
+The `Module/Tags` folder stores all the business logic for any template tags we create with our add-on. 
 
 ### `/views`
-The `views` folder contains all of our control panel views which will be used to actuall render our add-on's control panel pages.
+The `views` folder contains all of our Control Panel views which will be used to render our add-on's control panel pages.
 
 ### `/language`
-The `language` folder contains all of our lang files that will be used to display text on a page in whatever language is selected in the user’s account settings. 
+The `language` folder contains all of our language files that will be used to display text on a page in whatever language is selected in the user’s account settings. 
 
 ### `/database/migrations`
-The `/database/migrations` folder holds all migrations that will be ran on installation or updating of our add-on. Using the CLI, migrations can also be ran indepentantly.
+The `/database/migrations` folder holds all migrations that will be ran on installation or updating of our add-on. Using the CLI, migrations can also be ran independently.
 
 ### `Model`
 The `Model` folder holds all models that we are creating with our add-on.
 
 ### `widgets`
-The `widgets` folder holds all dashboard widgets that we are creating with our add-on.
+The `widgets` folder holds all dashboard widgets we create with our add-on.
 
 ## A Word About Legacy Add-On Development
-In the past, add-ons were often categorized based on their functionality. We identified our add-on to ExpressionEngine as a fieldtype, extension, module, or plug-in. Thus there was never a clear process to of how to structure one add-on that was all these categories in one. With the release of 6.4.x and 7.2.x this has been updated. The CLI has been updated to make creating add-ons and adding functionality incredibly easy, while the docs have also been updated to reflect the ideal workflow of creating an add-on. 
+In the past, add-ons were often categorized based on their functionality. We identified our add-on to ExpressionEngine as a fieldtype, extension, module, or plug-in. Thus there was never a straightforward process on structuring one add-on that contained all these categories in one. With the release of 6.4.x and 7.2.x this has been updated. The CLI has been updated to make creating add-ons and adding functionality incredibly easy. At the same time, the docs have also been updated to reflect the ideal workflow of creating an add-on. 
 
-While the latest changes shift our view of add-ons and how developers will create add-ons, you may still come across add-ons using the old methodology. We have left much of the old methods and structure in place so that older add-ons will continue to work. However, we are choosing not actively update the documentation for the old methods because we feel it's no longer in the best interest of the community to develop add-ons in this way. If you need to access how the docs once were regarding add-ons add-ons, you can reference the [legacy docs in GitHub](https://github.com/ExpressionEngine/ExpressionEngine-User-Guide/releases/tag/legacy-add-on-structure). 
+While the latest changes shift our view of add-ons and how developers will create add-ons, you may still come across add-ons using the old methodology. We have left much of the old methods and structure in place so that older add-ons will continue to work. However, we are choosing to not actively update the documentation for the old methods because we feel it's no longer in the best interest of the community to develop add-ons in this way. If you need to access how the docs once were regarding add-ons, you can reference the [legacy docs in GitHub](https://github.com/ExpressionEngine/ExpressionEngine-User-Guide/releases/tag/legacy-add-on-structure) (note that v7 and v6 were the same in these regards).