fix typos

Author: kcmartin

src/content/docs/concepts/lifecycle.mdx

@@ -8,7 +8,7 @@ import { Callout } from '@/components/react';
 
 This page is about what happens to a Sprite after you create it. Where it lives, how it sleeps, when it wakes up, and what it remembers.
 
-We'll cover how Sprites hibernate when idle, what counts as “activity,” what persists across wakeups, and how storage behaves under the hood.
+We'll cover how Sprites hibernate when idle, what counts as “activity,” what persists on resume, and how storage behaves under the hood.
 
 ## The Sprite Lifecycle
 
@@ -18,7 +18,7 @@ This model keeps things lean. Sprites pause when you're not using them, so you d
 
 The platform handles this automatically by tracking usage. If nothing interacts with a Sprite for long enough, it goes to sleep. If something hits it again, it spins back up and picks up where it left off.
 
-You don't have to manage any of this directly. But it helps to know what's going on, especially if you're optimizing for latency or trying to debug weird behavior after a resume.
+You don't have to manage any of this directly. But it helps to know what's going on, especially if you're optimizing for latency or trying to debug weird behavior on resume.
 
 ## Automatic Hibernation
 
@@ -107,7 +107,7 @@ These states are not currently exposed in CLI/SDK responses.
 
 ## Services
 
-## 8) Detached Sessions
+## Detached Sessions
 
 Detached sessions let you run long-lived processes inside a Sprite without keeping a connection open. Think of it like starting a background job and coming back later to check on it.
 
@@ -116,7 +116,7 @@ Sessions persist across CLI disconnects and can survive hibernation. If the Spri
 If you're looking to run a persistent service that automatically starts on wake, see [Services](/concepts/services) for complete documentation.
 
 
-## 9) Best Practices
+## Best Practices
 
 You don't need to micromanage Sprite lifecycle — it mostly just works. But a few habits can make things smoother: