diff --git a/src/components/sections/WhyUs.astro b/src/components/sections/WhyUs.astro index d4ffc88..a5fc5ff 100644 --- a/src/components/sections/WhyUs.astro +++ b/src/components/sections/WhyUs.astro @@ -20,31 +20,14 @@ 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.
-- 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. -
-- Cameleer is what we would build today, purpose-built for Apache Camel. No legacy, no retrofit, no assumptions about a generic middleware platform. -
-+ We spent over a decade building integration monitoring for banks, insurers, and logistics operators โ the kind of shops where a stuck exchange is a regulatory event, not just an inconvenience. +
++ Cameleer is what we'd build today, purpose-built for Apache Camel. No legacy, no retrofit, no assumptions about a generic middleware platform. +