Correct the isochrone token cost to 10 per contour in the docs

Author: Nathaniel Henry

docs/getting_started.rst

@@ -46,7 +46,7 @@ Every metered reply carries its accounting:
    print(summary.tokens_charged, "charged;", summary.tokens_remaining, "left")
 
 Metering is **1 token per returned row** (minimum 1 per request); isochrones are the
-exception at **1 token per contour**. A ``304`` revalidation is free.
+exception at **10 tokens per contour**. A ``304`` revalidation is free.
 
 Pagination
 ----------

docs/tutorials/amenity_basket.rst

@@ -68,7 +68,7 @@ Which amenities to add, and where
 ---------------------------------
 
 A new facility of type *X* placed at a block covers every block within a 15-minute
-walk of it — exactly a ``direction="from"`` walk isochrone (1 token each). We greedily
+walk of it — exactly a ``direction="from"`` walk isochrone (10 tokens each). We greedily
 pick the five sites that turn the most *currently-uncovered* residents into
 fully-covered ones.
 
@@ -127,7 +127,8 @@ Token cost
 
 - ``places``: free. ``blocks_query`` disc (~700 blocks × 6 categories):
   **~4,000 tokens** (cache ``rows`` and reuse it for the geometry pull).
-- Up to 25 candidate isochrones: **~25 tokens**.
+- Up to 25 candidate isochrones (1 contour each, 10 tokens): **~250 tokens**.
 
-Just inside a 5,000-token month. Shrink ``radius_m`` (or the candidate count) to
-trade coverage for budget; widen it, across several months, for a whole city.
+Around 4,300 tokens — inside a 5,000-token month. Shrink ``radius_m`` (or the
+candidate count) to trade coverage for budget; widen it, across several months, for a
+whole city.

docs/tutorials/home_search.rst

@@ -73,8 +73,8 @@ Block replies carry only GEOIDs, so join census-block boundaries. With
 Narrow to the overlap of two commutes
 -------------------------------------
 
-Say the two of you work near Kendall Square and downtown Boston. A **15-minute
-transit isochrone** from each workplace is one token per contour:
+Say the two of you work near Kendall Square and downtown Boston. A **20-minute
+transit isochrone** from each workplace is 10 tokens per contour:
 
 .. code-block:: python
 
@@ -97,7 +97,7 @@ Token cost
 - ``places`` + ``destination_types``: **free**.
 - ``place_blocks`` over Somerville (~800 blocks × 3 categories): **~2,400 tokens**
   (once; reuse the result for the map by caching ``rows``).
-- Two transit isochrones: **~2 tokens**.
+- Two transit isochrones (1 contour each): **~20 tokens**.
 
 Comfortably inside a 5,000-token month. For a larger city, replace
 ``place_blocks(geoid, …)`` with a bounded disc —

docs/tutorials/index.rst

@@ -4,7 +4,7 @@ Tutorials
 Three worked analyses, each written to run comfortably inside a **5,000-token
 monthly allowance**. The pattern is the same throughout: discover ids from the
 **free** catalog, pull one **bounded** slice of data, do the analysis **locally**
-(free), and lean on **isochrones** (1 token per contour) for walksheds. Every
+(free), and lean on **isochrones** (10 tokens per contour) for walksheds. Every
 tutorial ends with an estimated token cost.
 
 .. toctree::