Update articles/cosmos-db/sql/throughput-control-spark.md

TheovanKraay · FabianMeiswinkel · web-flow · commit 0e561870135c · 2022-06-23T14:59:03.000+01:00
Co-authored-by: Fabian Meiswinkel &lt;fabian@meiswinkel.com&gt;
diff --git a/articles/cosmos-db/sql/throughput-control-spark.md b/articles/cosmos-db/sql/throughput-control-spark.md
@@ -56,7 +56,7 @@ Within the Spark config of a given application, we can then specify parameters f
     "spark.cosmos.throughputControl.globalControl.container" -> "ThroughputControl"
 ```
 
-In the above example, the `targetThroughputThreshold` is defined as **0.95**, so rate limiting will occur (and requests will be retried) when clients consume more than 95% of the throughput that is allocated to the container. This configuration is stored as a document in the throughput container that looks like the below:
+In the above example, the `targetThroughputThreshold` is defined as **0.95**, so rate limiting will occur (and requests will be retried) when clients consume more than 95% (+/- 5-10 percent) of the throughput that is allocated to the container. This configuration is stored as a document in the throughput container that looks like the below:
 
 ```json
     {

Original file line number	Diff line number	Diff line change
`@@ -56,7 +56,7 @@ Within the Spark config of a given application, we can then specify parameters f`
`56`	`56`	`"spark.cosmos.throughputControl.globalControl.container" -> "ThroughputControl"`
`57`	`57`	```
`58`	`58`
`59`		-In the above example, the `targetThroughputThreshold` is defined as 0.95, so rate limiting will occur (and requests will be retried) when clients consume more than 95% of the throughput that is allocated to the container. This configuration is stored as a document in the throughput container that looks like the below:
	`59`	+In the above example, the `targetThroughputThreshold` is defined as 0.95, so rate limiting will occur (and requests will be retried) when clients consume more than 95% (+/- 5-10 percent) of the throughput that is allocated to the container. This configuration is stored as a document in the throughput container that looks like the below:
`60`	`60`
`61`	`61`	```json
`62`	`62`	`{`