docs: the running system's other names in permission-sets and authentication say "this system" or drop the noun; client-sdk cites cloud ADR-0028

permission-sets.mdx: "cannot be edited in the environment" and "cannot be
removed from the environment" say "this system", beside the bullet's own
"A set authored in this system". authentication.mdx: the bootstrap-status
fail-open sentence drops the noun ("when one may already exist"), as
:252 in the same section names the running system. client-sdk.mdx: the
ai.models() comment cites cloud ADR-0028, as the TSDoc and the
plugin-endpoints row do.

Claude-Session: https://claude.ai/code/session_01SYEJqDL3NXxrJRBVqaMu9T
Co-authored-by: Claude <noreply@anthropic.com>

Author: claude

content/docs/api/client-sdk.mdx

@@ -392,7 +392,7 @@ for await (const frame of await client.ai.chatStream({ messages })) {
 }
 
 await client.ai.complete({ prompt: 'Summarise this account in one line:' });
-await client.ai.models();                // plan-filtered picker list (ADR-0028)
+await client.ai.models();                // plan-filtered picker list (cloud ADR-0028)
 
 // Conversations — all six routes, scoped to the authenticated user server-side.
 const conv = await client.ai.conversations.create({ title: 'Q3 pipeline' });

content/docs/permissions/authentication.mdx

@@ -265,8 +265,7 @@ creation); `client.auth.bootstrapStatus()` is the SDK method that builds it.
 
 It **fails open**: if no data engine is wired, or the count query throws, it
 answers `{ "hasOwner": true }` so a client falls through to the ordinary login
-flow rather than offering to create an owner on an environment that may already
-have one.
+flow rather than offering to create an owner when one may already exist.
 
 <Callout type="warn">
 This route is unauthenticated, so treat `hasOwner: false` as a hint to render a

content/docs/permissions/permission-sets.mdx

@@ -377,7 +377,7 @@ goes through the metadata door (`PUT` or `DELETE /api/v1/meta/permission/:name`)
 which requires `manage_metadata` — and, under a `group` or `isolated` tenancy
 posture, the platform operator. This has three author-visible consequences:
 
-- **A set shipped in code cannot be edited in the environment.** That is a set
+- **A set shipped in code cannot be edited in this system.** That is a set
   an installed package declares (a `*.permission.ts` file, a stack's
   `permissionSets`) or a platform default such as `member_default`. Editing it
   through Setup or the metadata API answers `403 NOT_OVERRIDABLE` and stores
@@ -392,7 +392,7 @@ posture, the platform operator. This has three author-visible consequences:
   rename. Clone the set to a new name instead.
 - **A delete depends on where the definition lives.** A set authored in this
   system is removed. A set that ships with an installed package/app cannot
-  be removed from the environment: its definition stays served from the
+  be removed from this system: its definition stays served from the
   package. Uninstall the owning package to remove a packaged set entirely.
 
 An older database keeps the `sys_permission_set` table and its rows, and