docs: update references to renamed compose.storage-s3.yml

Author: simonvanlierde

CHANGELOG.md

@@ -22,7 +22,7 @@ First tagged release: the stack is runnable, demoable, and validated in CI.
 - README: architecture diagram, demo quickstart, screenshot, design
   decisions.
 - ADR 0001 recording the single-host OTLP-native architecture, and a
-  commented `compose.storage.s3.yml` stub documenting the storage
+  commented `compose.storage-s3.yml` stub documenting the storage
   scale-out path.
 
 ### Changed

README.md

@@ -125,7 +125,7 @@ someone.
 Everything persists to local Docker volumes (`loki_data`, `tempo_data`,
 `prometheus_data`, `grafana_data`). Swap Loki / Tempo storage to S3-compatible
 (Backblaze B2, Cloudflare R2, Hetzner, MinIO) when you outgrow local disk —
-`compose.storage.s3.yml` documents the concrete shape of that change, and
+`compose.storage-s3.yml` documents the concrete shape of that change, and
 `docs/adr/0001-observability-stack.md` records the architecture rationale.
 
 ## Design decisions

compose.storage-s3.yml

@@ -32,7 +32,7 @@
 #              secret_key: ${S3_SECRET_ACCESS_KEY}
 #
 #   2. Uncomment the overlay below and run:
-#        docker compose -f compose.yml -f compose.storage.s3.yml up -d
+#        docker compose -f compose.yml -f compose.storage-s3.yml up -d
 #
 # services:
 #   loki:

docs/adr/0001-observability-stack.md

@@ -43,6 +43,6 @@ endpoints via Cloudflare Tunnel; bind everything else to `127.0.0.1`.
   fire-and-forget) and the stack rebuilds from this repo in minutes.
 - Local disk bounds retention (30d logs/metrics, 7d traces). The escape hatch,
   reached before any move to distributed ingest, is S3-compatible storage for
-  Loki and Tempo — see `compose.storage.s3.yml`.
+  Loki and Tempo — see `compose.storage-s3.yml`.
 - Every image is pinned and validated by `just check` in CI, so the stack
   stays reproducible.