threadpools -> thread pools

Author: bjormel

…img/monitoring-container-threadpools.png …mg/monitoring-container-thread-pools.pngassets/img/monitoring-container-threadpools.png renamed to assets/img/monitoring-container-thread-pools.png assets/img/monitoring-container-threadpools.png renamed to assets/img/monitoring-container-thread-pools.png

@@ -50,7 +50,7 @@ <h3 id="dashboard-tabs">Tabs and filters</h3>
         <td>Document counts, Proton resource usage, executor utilization, maintenance jobs</td>
         <td>Deep investigation of search engine internals</td></tr>
     <tr><td><strong>Resources</strong></td>
-        <td>CPU, memory, disk, GPU, JVM, threadpools</td>
+        <td>CPU, memory, disk, GPU, JVM, thread pools</td>
         <td>Sizing and scaling decisions</td></tr>
     <tr><td><strong>Health</strong></td>
         <td>Cluster state, data consistency, restarts, reindexing, resource limits</td>
@@ -396,7 +396,7 @@ <h3 id="resources-tab">Resources tab</h3>
 <p>
   The Resources tab is the primary tool for sizing decisions. Node-level resources
   (CPU, memory, disk) are grouped per cluster. Container-specific metrics
-  (JVM, threadpools, GPU, network) are grouped per container cluster.
+  (JVM, thread pools, GPU, network) are grouped per container cluster.
 </p>
 
 <h4 id="resources-healthy-values">Typical healthy values</h4>
@@ -419,8 +419,8 @@ <h4 id="resources-healthy-values">Typical healthy values</h4>
   (especially disk index fusion) temporarily increase resource usage.
 </p>
 
-<h4 id="container-threadpools">Container threadpools</h4>
-<img src="/assets/img/monitoring-container-threadpools.png" alt="Container threadpools row with per-pool avg/max panels">
+<h4 id="container-thread-pools">Container thread pools</h4>
+<img src="/assets/img/monitoring-container-thread-pools.png" alt="Container thread pools row with per-pool avg/max panels">
 <p>Which thread pools exist on a container depends on which elements are configured
   in <code>services.xml</code>:</p>
 <table class="table">
@@ -454,7 +454,7 @@ <h4 id="container-threadpools">Container threadpools</h4>
     The default pool uses a synchronous queue (capacity 0), so there is no buffering &mdash;
     if no thread is available, the task is rejected.</li>
   <li><strong>Queue utilization</strong> &mdash; percentage of configured queue capacity used
-    (only meaningful for threadpools with bounded queues)</li>
+    (only meaningful for thread pools with bounded queues)</li>
 </ul>
 
 <h4 id="jvm-memory">JVM memory breakdown</h4>