Merge pull request #1094 from ExpressionEngine/strict-urls-clarification

Tweaking for added clarity and because I can't spell.

Author: TomJaeger

docs/control-panel/settings/template.md

@@ -25,7 +25,7 @@ If you wish to extend this to the second segment, requiring a valid template, th
 
 Our official recommendation is that users **enable** Strict URLs, as doing so makes the path to your content more precise, allows more relevant 404 pages, and does not allow your content to be shown with variances in the URL structure. However, for legacy reasons, Strict URLs are disabled by default.
 
-NOTE: **Note:** The pagination indicator Px is considered a valid first segment and will not trigger a 404 in order to allow pagination on the index page. Thus https://example.com/P5 will not trigger a 404 withe strict_urls enabled.
+NOTE: **Note:** The pagination indicator, upper-case P#, is considered a valid first segment and will not trigger a 404 in order to allow pagination on the index page. Thus https://example.com/P5 will not trigger a 404 with strict_urls enabled.
 
 ### 404 page
 

docs/general/system-configuration-overrides.md

@@ -2987,7 +2987,7 @@ Example Usage:
 
     $config['strict_urls'] = 'n';
 
-NOTE: **Note:** The pagination indicator Px is considered a valid first segment and will not trigger a 404 in order to allow pagination on the index page. Thus https://example.com/P5 will not trigger a 404 withe strict_urls enabled.
+NOTE: **Note:** The pagination indicator, upper-case P#, is considered a valid first segment and will not trigger a 404 in order to allow pagination on the index page. Thus https://example.com/P5 will not trigger a 404 with strict_urls enabled.
 
 **Also found in CP:** `Settings --> Template Settings`: [Enable Strict URLs](control-panel/settings/template.md#enable-strict-urls)