Doc fix

Author: ox-harris

site/capabilities.md

@@ -169,7 +169,7 @@ LinkedQL bundles an embeddable SQL engine, **FlashQL**, that brings its full cap
 > Run a full SQL engine in memory — same semantics, zero setup.
 
 ```js
-import { FlashClient } from '@linked-db/linked-ql/flash';
+import { FlashClient } from '@linked-db/linked-ql/flashql';
 const client = new FlashClient();
 
 await client.query(`CREATE TABLE users (id SERIAL, name TEXT)`);

site/flashql.md

@@ -21,7 +21,7 @@ Modern applications need database power without a network layer or the overhead
 Just spin up an instance in-app and run SQL:
 
 ```js
-import { FlashClient } from '@linked-db/linked-ql/flash';
+import { FlashClient } from '@linked-db/linked-ql/flashql';
 
 const db = new FlashClient();
 await db.connect();

site/flashql/foreign-io.md

@@ -19,8 +19,8 @@ With Foreign I/O, you can stream data on demand, materialize remote datasets loc
 Each mode requires FlashQL to be initialized with a remote connection factory:
 
 ```js
-import { FlashClient } from '@linked-db/linked-ql/flash';
-import { PGClient } from '@linked-db/linked-ql/pg';
+import { FlashClient } from '@linked-db/linked-ql/flashql';
+import { PGClient } from '@linked-db/linked-ql/postgres';
 
 const local = new FlashClient({
   onCreateRemoteClient: async (opts) => {

site/overview.md

@@ -11,7 +11,7 @@ LinkedQL is both:
 
 The broader idea captures the **intent** behind each tool in the compensatory layers built around SQL — query builders, ORMs, schema mappers, GraphQL servers, and other application-level boilerplates — and enables these natively within the language.
 
-This brings us to SQL that finally internalizes the external capabilities built around it — **an upgrade**.
+The result is SQL that finally internalizes the external capabilities built around it — **an upgrade**.
 
 Think of LinkedQL as **SQL, upgraded** — for modern applications.