docs: remove offline-first approach from migration guide

Author: soberm

src/directory/directory.mjs

@@ -1911,9 +1911,7 @@ export const directory = {
                             {
                               path: 'src/pages/gen1/[platform]/build-a-backend/more-features/datastore/migrate-from-datastore/add-local-caching/index.mdx'
                             },
-                            {
-                              path: 'src/pages/gen1/[platform]/build-a-backend/more-features/datastore/migrate-from-datastore/build-offline-support/index.mdx'
-                            },
+
                             {
                               path: 'src/pages/gen1/[platform]/build-a-backend/more-features/datastore/migrate-from-datastore/advanced-patterns/index.mdx'
                             },

src/pages/gen1/[platform]/build-a-backend/more-features/datastore/migrate-from-datastore/advanced-patterns/index.mdx

@@ -530,23 +530,23 @@ DataStore dispatched 9 distinct events via Hub. Of the 9:
 | Partially replaced | 2 | `networkStatus` (use browser APIs), `subscriptionsEstablished` (monitor subscription callbacks) |
 | No equivalent | 7 | `syncQueriesStarted`, `syncQueriesReady`, `modelSynced`, `outboxMutationEnqueued`, `outboxMutationProcessed`, `outboxStatus`, `storageSubscribed` |
 
-The 7 with no equivalent describe sync engine behavior, and Apollo Client does not have a sync engine. For the Offline-First strategy, the custom sync engine and mutation queue provide extension points for emitting similar events.
+The 7 with no equivalent describe sync engine behavior, and Apollo Client does not have a sync engine.
 
 ### Selective sync (syncExpressions)
 
-DataStore's `syncExpressions` let you filter which records synced from server to local store. Apollo has no equivalent for API Only or Local Caching. For Offline-First, the custom sync engine could implement sync filters, but this requires custom code.
+DataStore's `syncExpressions` let you filter which records synced from server to local store. Apollo has no equivalent for API Only or Local Caching.
 
 ### Lifecycle methods
 
 | Method | Apollo Equivalent | Rating |
 |---|---|---|
 | `DataStore.start()` | None (Apollo queries on demand) | None |
 | `DataStore.stop()` | Unsubscribe manually; `apolloClient.stop()` cancels in-flight | None |
-| `DataStore.clear()` | `apolloClient.clearStore()` + `persistor.purge()` + Dexie `db.delete()` | Partial |
+| `DataStore.clear()` | `apolloClient.clearStore()` + `persistor.purge()` | Partial |
 
 ### Conflict handler configuration
 
-This IS covered in the migration guide. API Only/Local Caching handle conflicts server-side. Offline-First uses custom client-side conflict resolution. **Rating: Full** (different location, same capability).
+This IS covered in the migration guide. API Only and Local Caching handle conflicts server-side. **Rating: Full** (different location, same capability).
 
 ### Summary