Merge pull request #1356 from david-fritz-gravwell/issue-1346

fix language on compound query limits.

configuration/parameters.md

@@ -440,6 +440,7 @@ Default Value:        `4`
 Example:        `Max-Block-Size=8`  
 Description:        The Max-Block-Size specifies a value in megabytes and is used as a hint to tell indexers the maximum block size they can generate when pushing entries into the pipeline.  Larger blocks reduce pressure on the pipeline, but increase memory pressure.  Large memory and high throughput systems can increase this value to increase throughput, smaller memory systems can decrease this size to reduce memory pressure.  The Prebuff-Block-Hint and Max-Block-Size parameters intersect to provide two knobs that tune ingest and search throughput.  At Gravwell, on the 128GB nodes, the following is achieved: a clean 1GB/s of search throughput; a 1.25 million entry per second ingest with a Max-Block-Size of 16; and a Prebuff-Block-Hint of 8 is achieved
 
+(config_params_render_store_limit)=
 ### **Render-Store-Limit**
 Applies to:		Webserver  
 Default Value:	1024  

search/search.md

@@ -230,7 +230,7 @@ This gives us a table of just connections that didn't have a corresponding DNS q
 ![](compound-ex2.png)
 
 ```{note}
-Compound queries create ephemeral resources that exist only during the query, however those resources can and do consume disk space and are restricted by the [Resource-Max-Size](config_params_resource-max-size)` global configuration variable which defaults to 512MB.  If the ephemeral resource is larger than the specified size the query will fail.
+Compound queries create ephemeral resources that exist only during the query, however those resources can and do consume disk space and are restricted by the [Render-Store-Limit](config_params_render_store_limit) global configuration variable which defaults to 1024MB. If the ephemeral resource is larger than the specified size, the query will fail.
 ```
 
 (specify-search-timeframe-in-query)=