(DOCSP-26576): Updated subset mode details. (#568)

* (DOCSP-26576): Updated subset mode details.

* (DOCSP-26576): Incorporated Zach's feedback.

* (DOCSP-26576): Incorporated Matt's feedback.

Author: corryroot

source/chart-type-reference/geospatial-heatmap.txt

@@ -16,14 +16,6 @@ You can use geospatial heatmap charts to visualize how
 geographic areas of a map compare to one another based on a given
 criterion.
 
-.. note::
-
-   Heatmap charts can use a maximum of 10,000 documents. If you
-   create a heatmap with a collection of more than 10,000
-   documents, turn on :ref:`Subset Mode <charts-subset-mode>` or use a
-   :ref:`filter <charts-filter-documents>`. Otherwise, your chart may
-   use incomplete or misleading data.
-
 Geospatial Heatmap Encoding Channels
 ------------------------------------
 

source/subset-mode.txt

@@ -9,10 +9,10 @@ Subset Mode
 You can enable :guilabel:`Subset Mode` in MongoDB Charts to restrict 
 the input collection to ``1000`` randomly selected documents. To toggle
 :guilabel:`Subset Mode`, use the toggle in the :guilabel:`Preview` 
-section. The :guilabel:`Subset Mode` setting for a chart persists when 
-the chart renders on a dashboard. So, if you enable subset mode when 
-you build a chart, the data that renders in the dashboard is also 
-sampled.
+section. The :guilabel:`Subset Mode` setting for a chart doesn't 
+persist when the chart renders on a dashboard. So, if you enable 
+subset mode when you build a chart, the data that renders in the 
+dashboard isn't sampled.
 
 .. note::
 
@@ -21,25 +21,17 @@ sampled.
    documents *before* it applies the filter. So, |charts| might use 
    fewer than ``1000`` documents to plot the chart.
 
-Use Cases
----------
+Use Case
+--------
 
-Consider using :guilabel:`Subset Mode` in the following scenarios:
-
-- When you draft a chart and heavily modify chart options. In this
-  situation, :guilabel:`Subset Mode` lets the chart render quickly 
-  during the building process. When you feel satisfied with your chart, 
-  you can disable :guilabel:`Subset Mode` to have all documents 
-  included in your final visualization.
-
-- When you visualize a large data source and the chosen data is
-  sufficiently aggregated (e.g. showing averages of fields) so
-  you don't need all documents to obtain a useful visualization.
-  In this case, if you leave :guilabel:`Subset Mode` enabled for the 
-  rendered dashboard, you can still retain a useful chart.
+Consider using :guilabel:`Subset Mode` when you draft a chart and 
+heavily modify chart options. In this situation, 
+:guilabel:`Subset Mode` lets the chart render quickly 
+during the building process. When you feel satisfied with your chart, 
+save it as soon as possible.
 
 .. note::
 
    Due to the random nature of sampling, when you have 
    :guilabel:`Subset Mode` enabled, your visualizations might change 
-   each time the chart loads.
+   each time the chart loads in the chart builder.

source/view-export-chart-data.txt

@@ -44,8 +44,6 @@ data source that considers:
 
 - :ref:`Pipelines applied to the data source <data-sources-pipeline>`
 
-- :ref:`Subset Mode <charts-subset-mode>` (if toggled on)
-
 - :ref:`Queries <query-bar>` or
   :ref:`pipelines specified in the Chart Builder <charts-agg-pipeline>`