Skip to content

Commit a3fca70

Browse files
committed
Fix typo: wont -> won't
1 parent bfc84a8 commit a3fca70

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

articles/application-gateway/multiple-site-overview.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -31,7 +31,7 @@ For example, if you have 2 listeners with associated host names of `*.contoso.co
3131

3232
The ordering of rules can be established by providing a **Priority** field value to the request routing rules associated with the listeners. You can specify an integer value from 1 to 20000 with 1 being the highest priority and 20000 being the lowest priority. If incoming client traffic matches with multiple listeners, the request routing rule with highest priority is used to serve the request. Each request routing rule must have a unique priority value.
3333

34-
The priority field only impacts the order of evaluation of a request routing rule, this wont change the order of evaluation of path based rules within a `PathBasedRouting` request routing rule.
34+
The priority field only impacts the order of evaluation of a request routing rule, this won't change the order of evaluation of path based rules within a `PathBasedRouting` request routing rule.
3535

3636
> [!NOTE]
3737
> To use rule priority, you must specify rule priority field values for all the existing request routing rules. Once the rule priority field is in use, any new routing rule that is created must have a rule priority field value as part of its configuration.

0 commit comments

Comments
 (0)