feat(copy): WhyUs — warmer language, 3-AM framing

Tile 2 headline now 'Built by people who know what 3 AM looks like.'
Bodies soften 'bidirectional protocol / signed config' into plain-value
language. nJAMS-legacy trademark review note preserved.

src/components/sections/WhyUs.astro

@@ -14,19 +14,19 @@
       <div class="rounded-lg border border-border bg-bg-elevated p-8">
         <h3 class="text-xl font-bold text-text mb-4">Generic APMs do not understand Camel. Cameleer does.</h3>
         <p class="text-text-muted leading-relaxed mb-4">
-          Our Java agent speaks 45+ Apache Camel EIP node types natively — choices, splits, multicasts, doTry, error handlers, dynamic endpoints, thread boundaries in async routes. It extracts your route topology as a first-class graph, not a pile of metrics.
+          Most monitoring tools see your app as a Java process and a pile of HTTP calls. Cameleer understands that you are running a Camel app — choices, splits, multicasts, error handlers, and every other EIP pattern as first-class citizens.
         </p>
         <p class="text-text-muted leading-relaxed">
-          A bidirectional protocol lets the server push deep-trace requests, per-route recording toggles, and signed config changes back to running agents — turning passive observability into active control. Not something you build in a weekend.
+          So when you ask "why did this exchange fail?", you get an answer, not a log tail. And you can reach back into a running app to replay a message, deep-trace a correlation ID, or toggle recording — observability that does things, not just shows them.
         </p>
       </div>
       <div class="rounded-lg border border-border bg-bg-elevated p-8">
-        <h3 class="text-xl font-bold text-text mb-4">Built by people who have shipped this class of product before.</h3>
+        <h3 class="text-xl font-bold text-text mb-4">Built by people who know what 3 AM looks like.</h3>
         <p class="text-text-muted leading-relaxed mb-4">
-          The Cameleer team spent years building and supporting integration monitoring for banks, insurers, and logistics operators. We know what integration teams actually need at 3 AM — and what they never use.
+          We spent years building integration monitoring for banks, insurers, and logistics operators — the kind of shops where a stuck exchange at 3 AM means someone's phone is ringing. We know what integration teams actually need then, and what they never use.
         </p>
         <p class="text-text-muted leading-relaxed">
-          Cameleer is what we would build today, purpose-built for Apache Camel — no legacy, no retrofit, no assumptions about a generic middleware platform.
+          Cameleer is what we would build today, purpose-built for Apache Camel. No legacy, no retrofit, no assumptions about a generic middleware platform.
         </p>
       </div>
     </div>