docs(concepts): use the permission vocabulary in when-to-use; tighten two compare sentences

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

Author: claude

content/docs/concepts/compare.mdx

@@ -13,8 +13,8 @@ an executable business ontology, is defined on [Business Ontology](/docs/concept
 
 ## Knowledge ontologies
 
-**What it is.** OWL and RDF, the W3C standards for describing a domain as classes,
-properties and axioms, and the tools built on them, such as the Protégé editor. A
+**What it is.** RDF and OWL, the W3C standards for describing a domain as statements,
+classes, properties and axioms, and the tools built on them, such as the Protégé editor. A
 reasoner infers facts nobody stored and checks that the whole description is
 consistent.
 
@@ -52,8 +52,8 @@ systems that stay where they are, so people and agents can act on operational de
 in one place.
 
 **The difference.** It is still a layer over systems that live elsewhere and, in
-Palantir's case, a proprietary platform. ObjectStack generates the database, API, UI
-and MCP tools from the definition, and it is Apache-2.0.
+Palantir's case, a proprietary platform. ObjectStack derives the database schema, API,
+UI and MCP tools from the definition, and it is Apache-2.0.
 
 ## Metadata-driven application platforms
 

content/docs/concepts/when-to-use.mdx

@@ -59,7 +59,7 @@ The ontology is one sentence with five parts. Answer them for your business:
 1. **What we have** — the objects and their fields.
 2. **How it relates** — the lookups and master-detail links between them.
 3. **What can be done** — the actions a user or an agent may take on a record.
-4. **Who may do it** — roles, row-level and field-level access, sharing.
+4. **Who may do it** — permission sets, row-level and field-level security, sharing.
 5. **What happens when** — record triggers, scheduled jobs, approvals, workflows.
 
 If the team can answer them, the ontology is a day's work, because an agent does the