Minor updates to template editing docs

Author: bryannielsen

docs/templates/overview.md

@@ -41,21 +41,21 @@ Templates can be created and edited in the `Developer -> Templates` area of your
 
 ![Templates List](_images/templates-list.png)
 
-You start off by creating template group. When creating, you will have options to duplicate existing group with all templates in it. You are also able to select the roles that will have editing permissions for templates in this group.
+You start off by creating a template group. During creation you will have the option to duplicate an existing group with all of its templates. You can also select the roles that will have editing permissions for templates in this group.
 
-Then, create individual templates. You can duplicate existing template, or create blank one. If necessary, change the template type from "Webpage" to the type that you need (RSS Page, CSS, JavaScript, Static, XML)
+Then, create individual templates. You can duplicate an existing template, or create a blank one. If necessary, change the template type from "Webpage" to the type that you need (RSS Page, CSS, JavaScript, Static, XML)
 
-Existing templates can be edited with built-in editor, which provides intelligent syntax highlighting.
+Existing templates can be edited with the built-in editor, which provides intelligent syntax highlighting.
 
-TIP: **Tip:** The font size in template editor can be adjusted with a [configuration override](general/system-configuration-overrides.md#codemirror_fontsize).
+TIP: **Tip:** The font size in the template editor can be adjusted with a [configuration override](general/system-configuration-overrides.md#codemirror_fontsize).
 
-You can also edit template preferences and set front-end access permissions for it.
+You can also edit template preferences and set front-end access permissions for the template.
 
 ![Template Editor](_images/template-edit.png)
 
 ## Saving templates as files
 
-Templates, Template Groups, Templates, Global Variable, and Template Partials are always saved into database and this is their primary souce, however by default they are also saved as regular folders and files on your server.
+Template Groups, Templates, Global Variables, and Template Partials are always saved into the database and this is their primary source, however by default they are also saved as regular folders and files on your server.
 
 This behavior is controlled by [system configuration overrides](general/system-configuration-overrides.md#save_tmpl_files)in `system/user/config/config.php`:
 ```php
@@ -65,7 +65,7 @@ $config['save_tmpl_files'] = 'y';
 $config['save_tmpl_globals'] = 'y';
 ```
 
-The directory structure would be similar to shown below
+The directory structure would be similar to what is shown below:
 
 ```
 |-- system
@@ -102,13 +102,13 @@ The directory structure would be similar to shown below
 |   |   |   |   |   |-- index.html
 ```
 
-This allows you to use your preferred text editor to edit Templates and then FTP the changes to the server.
+This allows you to use your preferred text editor to edit Templates and then transfer the changes to the server.
 
 `default_site` and `second_msm_site` are the site short names if you're running [Multiple Site Manager](msm/overview.md). If you have just one site, `default_site` is going to be the only one you need.
 
-`_partials` folder will be holding your [template partials](templates/partials.md) for the site, and `_global_partials` will be holding partials that are shared through all MSM sites.
+`_partials` folder holds your [template partials](templates/partials.md) for the site, and `_global_partials` holds partials that are shared through all MSM sites.
 
-`_variables` folder will be holding your [template variables](templates/variable.md) for the site, and `_global_variables` will be holding variables that are shared through all MSM sites.
+`_variables` folder holds your [template variables](templates/variable.md) for the site, and `_global_variables` holds variables that are shared through all MSM sites.
 
 These are the naming rules that ExpressionEngine applies to these resources:
 
@@ -121,11 +121,11 @@ These are the naming rules that ExpressionEngine applies to these resources:
   - _.xml_ creates an 'xml' template type
 - Template group names (not including the .group) and template names (not including the .extension) are limited to 50 characters. Anything longer than that will be truncated by the database and fail to match the file.
 
-Having several templates with same name but different extensions is not supported.
+Having several templates with the same name but different extensions is not supported.
 
-The existing templates are syncronized with the files as soon as any site page is accessed. However if you created new template or new template group on file system, you need to visit `Developer -> Templates` section of Control Panel in order to have them created in database.
+The existing templates are synchronized with the files as soon as any site page is accessed. However if you created a new template or a new template group on the file system, you will need to visit the `Developer -> Templates` section of the Control Panel in order to have them created in the database.
 
-NOTE: **Note:** When saving templates as files, `index.html` will be placed automatically into each template group folders when the templates are synchronized.
+NOTE: **Note:** When saving templates as files, `index.html` will be placed automatically into each template group folder when the templates are synchronized.
 
 ## Hidden Templates
 
@@ -158,7 +158,7 @@ Additionally, PHP code in templates will operate slower than same code wrapped i
 
 ExpressionEngine allows you to place [PHP](https://www.php.net/) code within your Templates so that it can be executed, allowing more dynamic capability with your content.
 
-In order for this feature to be available, it needs to be enabled by adding 
+In order for this feature to be available, it needs to be enabled by adding
 ```php
     $config['allow_php'] = 'y';
 ```