diff --git a/modules/ROOT/pages/create-instance-task-flex.adoc b/modules/ROOT/pages/create-instance-task-flex.adoc
index c18236560..262f2728d 100644
--- a/modules/ROOT/pages/create-instance-task-flex.adoc
+++ b/modules/ROOT/pages/create-instance-task-flex.adoc
@@ -52,6 +52,17 @@ In the following diagram, different routes manage requests to flight information
 
 image:multiple-upstreams.png[Flex Gateway manages the traffic to multiple upstreams]
 
+=== Limits
+
+[%header%autowidth.spread,cols="a,>.<a,a"]
+|===
+| Limit | Value | Notes
+| Upstreams per API | 50 | Each API supports 50 upstreams. The 50 upstreams can consist of a combination of different routes.
+| Routes per API | 50 | Each API supports 50 routes. 
+| Upstreams per route| 10|
+| Headers per route rule | 10| 
+| ===
+
 === Routes
 
 Each API instance supports up to 50 routes and each route can support up to 10 upstream services. Configure what requests a route can receive by defining route rules and a route order. At least one route per API instance is required. 
@@ -60,10 +71,6 @@ Before adding additional routes, enter an optional *Route label* for clarity.
 
 You can add additional routes by clicking *Add Route*, and you can delete routes by clicking the *Trash Can* icon (image:trash-can-icon.png[2%,2%]). If only one route is defined, you cannot delete that route.
 
-=== Limits
-
-include::partial$api-manager-limits.adoc[]
-
 ==== Route Rules
 
 You can direct requests to different routes by using route rules. 
@@ -163,6 +170,7 @@ Configure the following fields for each upstream service:
 
 
 
+
 //promote-api
 include::partial$task-promote-api.adoc[]