be stronger about the teachable moment

docs/patterns/sharding-content.md

@@ -266,7 +266,7 @@ As an alternative to cross-shard queries in this workload might be using an exte
 
 The workload team is aware that if the data catalog or its concurrent usage grows significantly more than three database instances might be required. The workload team doesn't expect to dynamically add database servers and will endure workload downtime if a new shard needs to come online. Bringing a new shard instance online requires moving data from existing shards into the new shard along with an update to the shard map table. This fairly static approach allows the workload to confidently cache the shard key database mapping in the website code.
 
-The shard key logic in this example has an upper limit of 11 maximum physical shards. If the workload team performs load estimation tests and evaluates that more than 11 physical databases are eventually going to be required, a change to the shard key logic would need to be made. This change involves the careful planning of code modifications and data migration to the new key logic.
+The shard key logic in this example has a hard upper limit of 11 maximum physical shards. If the workload team performs load estimation tests and evaluates that more than 11 databases instances are eventually going to be required, an invasive change to the shard key logic would need to be made. This change involves the careful planning of code modifications and data migration to the new key logic.
 
 ### SDK functionality