Minor documentation updates to avoid Sphinx warnings.

Author: njhenry

src/openpois/io/osm_history.py

@@ -7,6 +7,7 @@
 This module downloads OpenStreetMap data for a given area of interest.
 
 It is broken into the following functions:
+
 - build_query_string: Builds an Overpass query string for a given date and bbox.
 - build_date_range: Creates a list of dates for querying.
 - collect_element_ids: Queries Overpass for element IDs across a date range.

src/openpois/io/osm_snapshot.py

@@ -9,6 +9,7 @@
 and pyosmium parsing.
 
 It is broken into the following functions:
+
 - download_pbf: Downloads a PBF file from a URL via streaming HTTP.
 - filter_pbf: Runs osmium tags-filter to produce a reduced POI-only PBF.
 - parse_pbf_to_geodataframe: Parses the filtered PBF with pyosmium into a
@@ -362,6 +363,7 @@ def download_osm_snapshot(
     GeoParquet.
 
     Steps:
+
     1. download_pbf  — streams the Geofabrik US extract (~11 GB) to
        raw_pbf_path.
     2. filter_pbf    — runs osmium tags-filter to produce a small POI-only PBF.

src/openpois/io/overture.py

@@ -8,6 +8,7 @@
 given bounding box and set of taxonomy categories.
 
 It is broken into the following functions:
+
 - get_latest_release_date: Finds the most recent Overture release by listing S3.
 - build_overture_s3_path: Constructs the S3 glob path for a given release.
 - download_overture_snapshot: Queries S3 via DuckDB, filters by bbox and
@@ -90,9 +91,8 @@ def build_overture_s3_path(
         bucket: The S3 bucket name.
 
     Returns:
-        S3 path string suitable for DuckDB read_parquet(), e.g.:
-        's3://overturemaps-us-west-2/release/2026-02-18.0/
-            theme=places/type=place/*.parquet'
+        S3 path string suitable for DuckDB ``read_parquet()``, e.g.
+        ``s3://overturemaps-us-west-2/release/2026-02-18.0/theme=places/type=place/``
     """
     return (
         f"s3://{bucket}/release/{release_date}"

src/openpois/osm/change_plots.py

@@ -23,12 +23,13 @@ def change_plot_reshape_data(
     Reshape data for the change plot. The data comes in with one row per POI-tag, and
     is reshaped by elapsed days since the POI-tag was added. For each elapsed day, there
     are four possibilities:
-        1. Confirmed unchanged: The tag was observed unchanged on or *after* this day
-        2. Confirmed changed: The tag was last observed changed on or *before* this day
-        2. Unsure: The tag was last observed unchanged *before* this day, but has not yet
-            been observed changed
-        4. Aged out: The maximum time elapsed between when the tag was added and our data
-            download is *before* this day, so we should drop it from the plot
+
+    1. Confirmed unchanged: The tag was observed unchanged on or *after* this day
+    2. Confirmed changed: The tag was last observed changed on or *before* this day
+    3. Unsure: The tag was last observed unchanged *before* this day, but has not yet
+       been observed changed
+    4. Aged out: The maximum time elapsed between when the tag was added and our data
+       download is *before* this day, so we should drop it from the plot
 
     Args:
         observations: DataFrame with observations. Each row is an iteration of a