Merge pull request #663 from ExpressionEngine/feature/fix-docs-typos

Fix typos and spelling mistakes

Author: matthewjohns0n

docs/add-ons/consent.md

@@ -454,7 +454,7 @@ If this tag would not output any consent requests due to your filters, the conte
 
     type='necessary'
 
-Type of cookies to display. Possible options are `necessary`, `functionality`, `performance` and `targeting`. If omited, all cookies will be displayed.
+Type of cookies to display. Possible options are `necessary`, `functionality`, `performance` and `targeting`. If omitted, all cookies will be displayed.
 
 It is also possible to combine several types, e.g. `type="performance|targeting"`.
 
@@ -470,7 +470,7 @@ Limits display of cookies by cookie provider.
 If the cookie is provided by an add-on, the provider matches the add-ons short name, e.g. `comment` or `forum`
 The core ExpressionEngine cookies are identified by `ee` as provider.
 If cookie is only being used in Control Panel, the provider is set to `cp`.
-Possible options are `necessary`, `functionality`, `performance` and `targeting`. If omited, all cookies will be displayed.
+Possible options are `necessary`, `functionality`, `performance` and `targeting`. If omitted, all cookies will be displayed.
 
 It is also possible to combine several providers, e.g. `type="ee|cp"`.
 

docs/add-ons/pro-search/filters.md

@@ -226,7 +226,7 @@ will result in values `> 0` and `< 10` rather than `>= 0` and `<= 10`.
 NOTE: **Note:** For numeric fields, make sure the Field Content option in the field’s settings is set to Number, Integer or Decimal.
 
 ### Supported Fields
-Apart from any custom numeric or date field, the following stardard channel fields are supported:
+Apart from any custom numeric or date field, the following standard channel fields are supported:
 
 - `entry_date`
 - `edit_date`

docs/add-ons/pro-variables/type.md

@@ -40,7 +40,7 @@ Character to separate multiple values. Either a new line (`\n`), a pipe (`|`) or
 
 ## Date
 
-Displays a date picker. To output anything other than a timestamp, use the `{exp:pro_variables:single}` tag. This takes the same parameters as the native Date field. Additionaly, use `modifier="relative"` to output a relative date string.
+Displays a date picker. To output anything other than a timestamp, use the `{exp:pro_variables:single}` tag. This takes the same parameters as the native Date field. Additionally, use `modifier="relative"` to output a relative date string.
 
 ### Code examples
 
@@ -66,7 +66,7 @@ Uses the native [Grid field](/fieldtypes/grid.md). All native types are availabl
 
 #### `modifier`
 
-Any of the available [modifiers](/fieldtypes/grid.md#modifiers), which will trigger the ouput the modifier provides.
+Any of the available [modifiers](/fieldtypes/grid.md#modifiers), which will trigger the output the modifier provides.
 
 ### Code examples
 
@@ -304,7 +304,7 @@ Limit the number of rows displayed.
 
 ## Text Input
 
-Displays a single line edit input field. The _maxlength_ property can be set as well as the _size_ of the input fied. You can also define a regular expression _pattern_ to validate the value, and the _text direction_ of the input field.
+Displays a single line edit input field. The _maxlength_ property can be set as well as the _size_ of the input field. You can also define a regular expression _pattern_ to validate the value, and the _text direction_ of the input field.
 
 ### Settings
 

docs/add-ons/rte.md

@@ -169,7 +169,7 @@ NOTE: **Warning** Doing this requires advanced development skills.
 
 In order to create custom CKEditor build:
  - Clone [GitHub repo](https://github.com/ExpressionEngine/ExpressionEngine/)
- - Install NPM packages by runnin `npm install`
+ - Install NPM packages by running `npm install`
  - Follow the installation instructions for the plugin itself
  - Make your changes to `js-src\ckeditor5-build-classic\src\ckeditor.js` and other files as necessary.
  - Run the command `npm run build:ckeditor`

docs/add-ons/search/index.md

@@ -23,7 +23,7 @@ The [Advanced Search Form](add-ons/search/advanced.md) tag allows you to display
 
 ## Displaying Search Results
 
-The [Displaying Search Results](add-ons/search/results.md) page details the tags available for controling how you display results from your searches.
+The [Displaying Search Results](add-ons/search/results.md) page details the tags available for controlling how you display results from your searches.
 
 ## Search Syntax
 

docs/add-ons/spam.md

@@ -29,7 +29,7 @@ The Spam Module works by calculating the probability that a piece of content is
 
 ### Word Limit
 
-This is the number of unqiue words the Spam Module keeps track of when learning from your Spam Trap. More words is more accurate, but this will slow down the Spam Module everytime it tries to classify content as spam.
+This is the number of unique words the Spam Module keeps track of when learning from your Spam Trap. More words is more accurate, but this will slow down the Spam Module everytime it tries to classify content as spam.
 
 ### Content Limit
 

docs/add-ons/structure/overview.md

@@ -13,4 +13,4 @@ Structure is a powerful add-on that lets you create pages, generate navigation,
 
 It forgoes the default template_group/template setup and creates “static” and “listing” pages that are all editable through a tree sitemap view. With Structure enabled, traditional page style content and multiple entry pages can live within the same area.
 
-NOTE:**Note:** Documentation for Structure is still being migrated. Until this is complete, please refernce the [Structure documentation on EEHarbor's website](https://eeharbor.com/structure/documentation).
+NOTE:**Note:** Documentation for Structure is still being migrated. Until this is complete, please reference the [Structure documentation on EEHarbor's website](https://eeharbor.com/structure/documentation).

docs/advanced-usage/front-end/frontend.md

@@ -35,7 +35,7 @@ After editing data, content can be saved by one of two ways:
 ![save without reload](_images/ee-pro-save-reload.png)
 
 ## Unsaved Changes
-When a user edits data and has unsaved changes, Pro will create an autosave of the entry and alert the user via a notification on the edit window with unsaved changes. The autosave is triggerd based on the default autosave interval of 60 seconds. If you want to ensure users do not accidentally lose unsaved changes adjust the `[autosave_interval_seconds]` system config override to a lower interval between autosaves. A setting of 10 seconds is the recommendation.
+When a user edits data and has unsaved changes, Pro will create an autosave of the entry and alert the user via a notification on the edit window with unsaved changes. The autosave is triggered based on the default autosave interval of 60 seconds. If you want to ensure users do not accidentally lose unsaved changes adjust the `[autosave_interval_seconds]` system config override to a lower interval between autosaves. A setting of 10 seconds is the recommendation.
 
 ![unsaved changes](_images/pro_unsaved_changes.png)
 

docs/channels/channel-form/inputs.md

@@ -37,7 +37,7 @@ Set the date of the entry and apply an enabled datepicker:
 
     <p>Date <br> <input type="text" name="entry_date" value="{entry_date}" maxlength="23" size="25" rel="date-picker" data-timestamp="{entry_timestamp}"></p>
 
-NOTE: **Note:** All date formats should match what the user has defined in their localization settings. The date fields will autmatically use that format and validate against it.
+NOTE: **Note:** All date formats should match what the user has defined in their localization settings. The date fields will automatically use that format and validate against it.
 
 ### Expiration Date
 

docs/channels/entry-linking.md

@@ -89,7 +89,7 @@ Or you can exclude channels by including the word "not" followed by a space:
 
     entry_id="12"
 
-You can limit the tag to specific entries, or more practically, you can ommit specific entries from showing up in the cycle, by using "not":
+You can limit the tag to specific entries, or more practically, you can omit specific entries from showing up in the cycle, by using "not":
 
     entry_id="not 2|9|23|50"