Fix links and spelling errors

Author: bryannielsen

docs/add-ons/consent.md

@@ -179,7 +179,7 @@ If this tag would not output any consent requests due to your filters, the conte
       No Consent Requests Available
     {/if}
 
-### Conesnt Form Examples
+### Consent Form Examples
 
 #### Simple Bulk Consent Form
 
@@ -466,7 +466,7 @@ If you need to exclude one or several types from display, use `not ` before the
 
     provider='ee'
 
-Limits display of cookies by cookie provider. 
+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`.

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

@@ -117,7 +117,7 @@ This is equal to:
 
 ### SQL parameters
 
-Pro Search supports SQL parameters. This means you can use a SQL query in any pararameter. SQL queries are limited to SELECTs only and should always end with a semi-colon (;). Pro Search will take the first item in the SELECT statement and creates a pipe-separated list from it. If the SQL query produces no results, it sets the parameter value to what comes after the semi-colon. You can optionally prefix the SQL query for better matching. Schematically, such a query looks like this:
+Pro Search supports SQL parameters. This means you can use a SQL query in any parameter. SQL queries are limited to SELECTs only and should always end with a semi-colon (;). Pro Search will take the first item in the SELECT statement and creates a pipe-separated list from it. If the SQL query produces no results, it sets the parameter value to what comes after the semi-colon. You can optionally prefix the SQL query for better matching. Schematically, such a query looks like this:
 
 `param="prefix SELECT field FROM table WHERE lorem = 'ipsum';no results"`
 

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

@@ -40,7 +40,7 @@ The same query with GET variables would look like this:
 
 `domain.com/search/results?keywords=hello+world`
 
-Using GET variables is not possible if the `uri_protocol` config setting is set to QUERY_STRING. It can also cause unexpected behaviour if you’re using the second exception (the question mark) in your `.htaccess` file when hiding `index.php`. If you can, use the encoded query instead as this will always work.
+Using GET variables is not possible if the `uri_protocol` config setting is set to QUERY_STRING. It can also cause unexpected behavior if you’re using the second exception (the question mark) in your `.htaccess` file when hiding `index.php`. If you can, use the encoded query instead as this will always work.
 
 NOTE:**Note:** When using GET variables, make sure Dynamic Channel Query Caching is turned off.
 
@@ -54,7 +54,7 @@ Choose a tag which is used to highlight keywords in the search excerpt. Options
 
 ### Minimum word length
 
-The ft_min_word_len setting of your MySQL installation determines the minimum length of words indexed by the Full Text index. Setting that value here will trigger an alternative search algorithm when the search term is smaller than this size. Defaults to 4. Do not alter unless you have customised your MySQL installation.
+The ft_min_word_len setting of your MySQL installation determines the minimum length of words indexed by the Full Text index. Setting that value here will trigger an alternative search algorithm when the search term is smaller than this size. Defaults to 4. Do not alter unless you have customized your MySQL installation.
 
 ### Stop words
 

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

@@ -51,7 +51,7 @@ When using the suffix option, you can use `{suffix}` in both the variable name a
 
 ## Variable groups
 
-You can create any number of groups to organise your variables. These groups will appear in the Group drop down for each variable, so you can assign a group to it. On the module home page, variable managers can sort the groups using drag and drop. Variable managers can also edit and delete the groups from here, by clicking on the edit or delete icon next to the group name. You can alter the variable order in a group by editing the group’s properties.
+You can create any number of groups to organize your variables. These groups will appear in the Group drop down for each variable, so you can assign a group to it. On the module home page, variable managers can sort the groups using drag and drop. Variable managers can also edit and delete the groups from here, by clicking on the edit or delete icon next to the group name. You can alter the variable order in a group by editing the group’s properties.
 
 
 ### Group label

docs/add-ons/rte.md

@@ -126,7 +126,7 @@ WARN: **Advanced users only.** Please be careful with using this feature and che
 
 Initially the field is loaded with the saved configuration of tool set being edited.
 
-Consult [Redactor Docs](https://imperavi.com/redactor/docs/settings/) or [CKEDitor Docs](https://ckeditor.com/docs/ckeditor5/latest/installation/getting-started/configuration.html) for the list of properties. Note that not all features are supported by the ExpressionEngine implementation.
+Consult [Redactor Docs](https://imperavi.com/redactor/docs/settings/) or [CKEditor Docs](https://ckeditor.com/docs/ckeditor5/latest/installation/getting-started/configuration.html) for the list of properties. Note that not all features are supported by the ExpressionEngine implementation.
 
 #### Extra JavaScript
 JavaScript template to be included with fields using this tool set. Typically used to include extra plugins when using advanced configuration with Redactor.

docs/add-ons/spam.md

@@ -25,7 +25,7 @@ The Spam Module has three important configuration settings:
 
 ### Sensitivity
 
-The Spam Module works by calculating the probability that a piece of content is spam based on all the examples it's seen before. The sensitivity is the cutoff for what we consider spam. This defaults to 70 which means there has to be at least a 70% probability something is spam for it to get flagged. If this is higher you will have fewere false positives but more spam will slip through.
+The Spam Module works by calculating the probability that a piece of content is spam based on all the examples it's seen before. The sensitivity is the cutoff for what we consider spam. This defaults to 70 which means there has to be at least a 70% probability something is spam for it to get flagged. If this is higher you will have fewer false positives but more spam will slip through.
 
 ### Word Limit
 

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

@@ -12,7 +12,7 @@
 [TOC]
 
 ## Overview
-The Dock is a central component of ExpressionEngine's front-end functionality. 
+The Dock is a central component of ExpressionEngine's front-end functionality.
 
 ![dock overview](_images/ee-pro-dock.png)
 
@@ -47,7 +47,7 @@ The Control Panel button on the Dock will open the site's Control Panel in a new
 Prolets are add-on components that reveal some of add-on's functionality for the Control Panel to the front-end, making it possible to edit data directly on the page where it belongs.
 
 ### Built-in Prolets
-ExpressionEngine is shipped with the Entries and Publish prolets. 
+ExpressionEngine is shipped with the Entries and Publish prolets.
 
 Clicking on the Entries prolet opens a prolet window with all entries currently listed. Allowing you to quickly find and edit other entries in your site.
 
@@ -61,6 +61,6 @@ Developers may create third-party prolets that can be installed with add-ons. Re
 ![dock prolets](_images/ee-pro-dock-prolets.png)
 
 ## Disabling
-The Dock can be disabled by either the setting in the [Control Panel](control-panel/settings/front-end-editing.md#general-settings) or [config override](general/system-configuration-overrides.md#enable_dock).
+The Dock can be disabled by either the setting in the [Control Panel](control-panel/settings/front-end-editing.md#enable-dock) or [config override](general/system-configuration-overrides.md#enable_dock).
 
-WARN **Warning**: If the Dock is disabled, all of ExpressionEngine's [Front-End Content Management](advanced-usage/front-end/overview.md) is turned off for the front-end. 
+WARN **Warning**: If the Dock is disabled, all of ExpressionEngine's [Front-End Content Management](advanced-usage/front-end/overview.md) is turned off for the front-end.

docs/channels/channel-form/status.md

@@ -28,6 +28,6 @@ Or use the alternative syntax:
       {/statuses}
     </select>
 
-To manually set an entry's status upon sutmitting the Channel Form, you can use a Hidden field:
+To manually set an entry's status upon submitting the Channel Form, you can use a Hidden field:
 
     <input type="hidden" name="status" value="Shipped" />

docs/channels/entries.md

@@ -274,7 +274,7 @@ When used in an RSS/Atom feed, this parameter allows ExpressionEngine to dynamic
 You can hard code the channel tag to show a specific channel entry. You may also specify multiple entries by separating them with the pipe character:
 
     entry_id="13|42|147"
-    
+
 Or use "not" to exclude entries::
 
     entry_id="not 45|534|807"
@@ -422,7 +422,7 @@ This parameter is for use with entry [pagination](templates/pagination.md) and d
 
 If no parameter is specified, the navigation block will default to the "bottom" behavior.
 
-If the pagination tag pair is not included, the entries returned will not respond to a page indicator in the URL. In othat case you would need to set the parameter to _hidden_ to allow the entries to reflect the pagination in the URL.
+If the pagination tag pair is not included, the entries returned will not respond to a page indicator in the URL. In that case you would need to set the parameter to _hidden_ to allow the entries to reflect the pagination in the URL.
 
 ### `paginate_base=`
 

docs/channels/entry-spanning.md

@@ -84,7 +84,7 @@ The {multi_field=} variable is the core of the ability to span a channel entry a
 
         {multi_field="page1|page2|page3"}
 
-3.  When you initially visit your comment page for an entry, where you xhave the {multi_field} tag in your Template, you will see the content of your "page1" field, just as if you had used the regular {page1} variable.
+3.  When you initially visit your comment page for an entry, where you have the {multi_field} tag in your Template, you will see the content of your "page1" field, just as if you had used the regular {page1} variable.
 4.  If your entry has content in the "page2" field then you will see a "next page" link.
 5.  When you click that link, you'll see your entry again, but instead of {page1} being displayed, in its place would be {page2}.
 6.  This would continue with as many variables/pages as needed.