docs: backtick the remaining two bracketed intervals

Neither warned — rustdoc only flags bracketed prose that could parse as an
item path, and `[512k + 4, 512k + 508]` (snap.rs) and `[0, 1]` (camera.rs)
do not. They are the same latent shape d89b19f fixed in ramp.rs though, and
the backticks are right on their own terms: these are ranges, and the
surrounding text already marks its other operands as code.

Comment-only; 175 tests unchanged and the crate's rustdoc stays clean.

Co-Authored-By: Claude Opus 5 <[email protected]>

 src/camera.rs | 2 +-
 src/snap.rs   | 2 +-
 2 files changed, 2 insertions(+), 2 deletions(-)

diff --git a/src/camera.rs b/src/camera.rs
index c19e2b6..a31e999 100644
--- a/src/camera.rs
+++ b/src/camera.rs
@@ -95,7 +95,7 @@ pub fn centered_window_origin(pan: f64, extent: f64, zoom: f64, win: f64) -> f64
 }
 
 /// Anchor-stable zoom-pan interpolation between two cameras at progress
-/// `p` ∈ [0, 1]: zoom log-lerps, and pan is DERIVED from the unique world
+/// `p` ∈ `[0, 1]`: zoom log-lerps, and pan is DERIVED from the unique world
 /// point that maps to the same screen position under both cameras — so the
 /// whole transition reads as a single zoom about a stationary anchor
 /// instead of a sideways slide-while-zooming (independent pan/zoom lerp
diff --git a/src/snap.rs b/src/snap.rs
index 5b234b9..0a96b5b 100644
--- a/src/snap.rs
+++ b/src/snap.rs
@@ -314,7 +314,7 @@ mod tests {
     use super::*;
 
     /// Square 512 cells, no gap, fade inset 4: visible cell k spans
-    /// [512k + 4, 512k + 508]. Border width is irrelevant to snapping now —
+    /// `[512k + 4, 512k + 508]`. Border width is irrelevant to snapping now —
     /// content edges land on the targets and the border overhangs outward.
     fn params() -> SnapParams {
         SnapParams {