Update customer example details

README.md

@@ -12,7 +12,8 @@ This is also an infrastructure as code solution, meaning that it should only req
 Once deployed, the endpoint generally takes 1-3 seconds to execute when called, and is [idempotent](https://en.wikipedia.org/wiki/Idempotence), so changes will only be implemented once when the specified route either does not exist in one or more custom route tables or the next hop value changes.
 Routes will not be programmatically removed by this solution.
 
-One customer success story to date is that this solution was used in [us-east-1](https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/using-regions-availability-zones.html) to synchronize 26 production routes across 4 custom route tables (104 concurrent route synchronizations) within 4 seconds.
+One customer success story to date is that this solution was used in [us-east-1](https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/using-regions-availability-zones.html) to synchronize 26 production routes across 4 custom route tables (104 concurrent route synchronizations) with a 5 second polling interval.
+In testing, all route targets updated successfully within 4 seconds.
 This met the customer's requirement of completing all route synchronizations prior to timeout of a mission critical application at 15 seconds, and allowed them to complete a critical maintenance window.
 
 Please test thoroughly.