updating specs

Author: cblanquera

docs/README.md

@@ -1,7 +1,7 @@
 # API Reference
 
 - [Data](./api/data/Nest.md)
-  `Nest`, readonly wrappers, map/set helpers, parsers, and cookies.
+  `Nest`, readonly wrappers, map and set helpers, parsers, and cookie helpers.
 - [Events](./api/events/EventEmitter.md)
   `EventEmitter`, `ExpressEmitter`, and `RouteEmitter`.
 - [Queues](./api/queue/ItemQueue.md)
@@ -21,7 +21,7 @@
 - [Map](./api/data/Map.md)
 - [Set](./api/data/Set.md)
 - [Parsers](./api/data/Parsers.md)
-- [cookie](./api/data/Cookie.md)
+- [Cookie](./api/data/Cookie.md)
 
 ## Events
 

docs/api/router/Session.md

@@ -6,15 +6,17 @@ Cookie-oriented session storage for requests and responses.
 
 ```ts
 import type { CallableSession } from '@stackpress/lib';
-import { session } from '@stackpress/lib/Session';
-import { ReadSession, WriteSession } from '@stackpress/lib/Session';
+import { ReadSession, WriteSession, session } from '@stackpress/lib/Session';
 ```
 
-`ReadSession`, `WriteSession`, and `session()` are package-exported by the `@stackpress/lib/Session` subpath. They are not re-exported from the root barrel.
+Import `ReadSession`, `WriteSession`, and `session()` from the
+`@stackpress/lib/Session` subpath. The root barrel only re-exports the
+`CallableSession` type.
 
 ## When To Use It
 
-Use these APIs when you need one session abstraction for request reads and response-side cookie revisions.
+Use these APIs when you need one session abstraction for request reads and
+response-side cookie revisions.
 
 ## API
 
@@ -66,7 +68,8 @@ store('sessionId');
 store.get('sessionId');
 ```
 
-`session(data?)` returns a `CallableSession` with these additional exposed properties:
+`session(data?)` returns a `CallableSession` with the usual callable lookup plus
+these exposed properties:
 
 - `data`
 - `options`

docs/api/types/README.md

@@ -34,7 +34,9 @@ import type {
 } from '@stackpress/lib/types';
 ```
 
-`@stackpress/lib/types` is the intended import path for the type surface. Many types are re-exported from the root barrel, but the dedicated types subpath is the clearest stable reference point.
+Use `@stackpress/lib/types` when you want a dedicated import path for the public
+type surface. Many of these types are also re-exported from the root barrel, but
+the `types` subpath is the clearest stable reference point.
 
 ## Data Types