/* ==========================================================================
   Divigi — service-pages.css
   Spacing for the generated location and industry service pages.

   Scoped to .service-area .service-box, which only the service page renderer
   outputs, so list styling everywhere else is untouched.

   The selectors carry .service-area deliberately. The theme's own rule is
   `:where(.pt-locsvc) .service-area .service-box li` — :where() contributes
   nothing, so that is two classes and an element, and a plainer `.service-box
   li` loses to it and silently does nothing. Matching the shape ties the
   specificity, and this file is enqueued after the bundle, so it wins.
   ========================================================================== */

/* The sub-service bullets.

   The real problem was not the gap BETWEEN items — it was the leading inside
   them: 20px on 18px text, a ratio of 1.11. Any bullet that wrapped to a second
   line closed up tighter internally than the 5px separating it from the next
   bullet, so the list read as one grey block rather than as separate points.
   The leading has to be fixed first; extra margin alone just spaces out
   paragraphs that are still cramped. */
.service-area .service-box li,
.service-area .whyus li {
	line-height: 1.55;
	margin-bottom: 12px;
}

.service-area .service-box li:last-child,
.service-area .whyus li:last-child {
	margin-bottom: 0;
}

/* Tight groups, generous separation. The list belongs to the paragraph above
   it, so this gap stays well below the 50px that separates one sub-service from
   the next — enough to part them, not enough to break the pair. */
.service-area .service-box .content-first ul,
.service-area .whyus ul {
	margin-top: 16px;
}

/* The body copy carries the same leading as the bullets, so the block reads as
   one voice rather than two. */
.service-area .service-box .content-first p,
.service-area .whyus p {
	line-height: 1.55;
}

/* Reading measure.

   Widening the container to 1760px pushed these paragraphs to 138 characters
   per line on a 2560 screen — nearly twice the 65–75 that reads comfortably. At
   that length the eye loses its place on the return sweep, and the wider the
   display the worse it gets, so the page punishes the best screens.

   Capping the text rather than the container keeps the extra width where it is
   useful — the layout, the sidebar, the icon column — while the prose itself
   stays at a readable length. ch tracks the font, so this holds if the type
   scale changes. */
.service-area .service-box .content-first p,
.service-area .service-box .content-first li,
.service-area .whyus p,
.service-area .whyus li {
	max-width: 72ch;
}