fix: error message typo

docs/pages/debug/+Page.mdx

@@ -2,7 +2,7 @@ import { Link } from '@brillout/docpress'
 
 In general, if you run into any issues with Vike, we recommend that you <Link href="/faq#how-can-i-reach-out-for-help">reach out to us</Link>.
 
-> If you report a Vike bug, then we quickly fix it (usually under 24 hours).
+> If you report a Vike bug, then we quickly fix it (usually within 24 hours).
 
 That said, you can also dig into issues yourself.
 

docs/pages/index/sections/Reliable/Reliable.tsx

@@ -66,8 +66,8 @@ const benefits = [
     href: '/why#flexible-and-reliable-by-prioritization',
     description: (
       <>
-        We are responsive with a clear guideline on how to receive assistance. Bugs are quickly fixed (usually under 24
-        hours).
+        We are responsive and provide clear guidelines on how to receive reliable assistance. Bugs are quickly fixed
+        (usually within 24 hours).
       </>
     ),
     image: <BugFixSVG />

docs/pages/why/+Page.mdx

@@ -35,7 +35,7 @@ Another example is Vike's server middleware <Link href="/renderPage"><code>rende
 
 If you create a feature request and explain why it's blocking then we treat it with higher priority.
 
-We quickly fix bugs (usually under 24 hours).
+We quickly fix bugs (usually within 24 hours).
 
 Vike's team is responsive and we provide <Link href="/faq#how-can-i-reach-out-for-help">a clear guideline</Link> on how to receive reliable assistance.
 

vike/utils/assert.ts

@@ -54,7 +54,7 @@ function assert(condition: unknown, debugInfo?: unknown): asserts condition {
 
   const link = pc.blue('https://github.com/vikejs/vike/issues/new')
   let errMsg = [
-    `You stumbled upon a Vike bug. Go to ${link} and copy-paste this error. A maintainer will fix the bug (usually under 24 hours).`,
+    `You stumbled upon a Vike bug. Go to ${link} and copy-paste this error. A maintainer will fix the bug (usually within 24 hours).`,
     debugStr
   ]
     .filter(Boolean)