Skip to content

Commit afef588

Browse files
Update modules/ROOT/pages/create-instance-task-flex.adoc
Co-authored-by: Diane E Hirsch <diane.hirsch@mulesoft.com>
1 parent f9d838f commit afef588

1 file changed

Lines changed: 1 addition & 1 deletion

File tree

modules/ROOT/pages/create-instance-task-flex.adoc

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -133,7 +133,7 @@ To define the route order, use the up and down arrows to arrange the routes.
133133

134134
Route ordering is very important when a request can meet the route rules of multiple routes. You should order the routes with more complex route rules first. If you do not define a route order, routes are ordered in the order they were created.
135135

136-
For example, in a configuration where route one has the `GET` method defined as a rule and route two has no route rules defined, all `GET` requests are sent to route one and all other requests are sent to route two. If the route order was reversed and route one had no route rules, Flex Gateway would direct all requests to route one before any `GET` requests could reach route two.
136+
For example, in a configuration in which route one has the `GET` method defined as a rule and route two has no route rules defined, all `GET` requests are sent to route one and all other requests are sent to route two. If the route order was reversed and route one had no route rules, Flex Gateway would direct all requests to route one before any `GET` requests could reach route two.
137137

138138
=== Upstreams
139139

0 commit comments

Comments
 (0)