Recapture 0.2.0 screenshots: profile editor, extensions, builder

docs/features/domain-profiles.md

@@ -44,14 +44,16 @@ untouched — that's what lets one Context be "Payments" and another "Infra".
 
 ## Edit a profile
 
-Open a profile in the editor (from the Library) to change it:
+In **Library → Domain profiles**, click **Edit** on a profile's card to open the
+editor:
 
 ![The domain profile editor: metadata on top, raw Markdown below](/img/features/profile-editor.png)
 
 - **Name** and **Markdown file path** at the top.
 - The **raw Markdown** below — what you see is exactly what the client reads.
 - **Save** writes to the profile's file; **Duplicate** copies it as a starting
-  point for a similar team; **Delete** removes it (with confirmation).
+  point for a similar team. To delete a profile, use **Remove** on its Library
+  card.
 
 ## Anatomy of a good profile
 

docs/features/using-extensions.md

@@ -35,7 +35,7 @@ profiles and searches its knowledge folders — those need no setup here.
 
 ## Add an extension
 
-1. Click **Add**.
+1. Click **Install from folder**.
 2. Pick the extension's **folder** — the one containing its
    `neatcontext-extension.json` manifest.
 3. Review and **install** it. The new card appears in the list.
@@ -45,7 +45,7 @@ profiles and searches its knowledge folders — those need no setup here.
 Each card shows the extension's name, description, version, its **tools** (hover
 one for its description), and controls: **Enable/Disable**, **open folder**, and —
 for extensions you added — **remove**. If you change an extension's files later,
-use its **Update** button to pick up the change.
+use its **Reload** button to pick up the change.
 
 :::caution[Extensions are code you run]
 An extension runs on your machine with your user's permissions. Treat a

docs/getting-started.md

@@ -112,8 +112,8 @@ logs, list deployments. Open **Extensions**:
 
 - The bundled **PagerDuty** and **Datadog** connectors are ready to
   [connect](./features/using-extensions.md#connect-an-extension).
-- **Add** installs an extension from a folder; **Create** builds a read-only
-  connector for any JSON HTTP API without writing code.
+- **Install from folder** installs an extension from a folder; **Create** builds a
+  read-only connector for any JSON HTTP API without writing code.
 
 Enable an extension, then select it into your Context. The
 [incident demo](./guides/incident-analysis.md) ships a complete extension plus

docs/guides/incident-analysis.md

@@ -87,8 +87,9 @@ demo README's *Customizing* section).
 ## Step 3 — Add and enable the extension
 
 1. Open the **Extensions** page.
-2. Click **Add** and select the demo's **`extension/`** folder (the one containing
-   `neatcontext-extension.json`). NeatContext installs it as **Ops Demo Systems**.
+2. Click **Install from folder** and select the demo's **`extension/opsdemosystems`**
+   folder (the one containing `neatcontext-extension.json`). NeatContext installs it
+   as **Ops Demo Systems**.
 3. Make sure it's **enabled**. There is nothing to authenticate — it talks straight
    to the local mock systems.