transilienceai · muzaffar-ni · Jul 9, 2026 · Jul 9, 2026
diff --git a/concepts/Applications.md b/concepts/Applications.md
diff --git a/concepts/apps.md b/concepts/apps.md
@@ -4,7 +4,7 @@
 
 An **app** is a reusable security or compliance workflow you can run on demand. Each app does one job — for example, scanning a cloud account for misconfigurations, running a CIS benchmark, generating a tabletop exercise, or analyzing access reviews. The catalog of apps is what you see when you click **Apps** in the sidebar.
 
-"App" and "project" mean the same thing. You'll see "App" everywhere in the product UI; "project" appears in some internal labels and URLs (like `/apps/detail/[appId]`). Treat them as synonyms.
+You'll see **App** everywhere in the product UI. In the URL bar an app detail page appears as `/apps/detail/{appId}`.
 
 ## Where to find them
 
@@ -25,7 +25,6 @@ A sidebar on the right lists your most recent runs across all apps, with the lat
 Clicking an app card opens its detail page at `/apps/detail/{appId}`. The detail page shows:
 
 - The full description of what the app does.
-- The agents and skills the app uses internally (mostly informational).
 - A button to launch the app.
 
 When you launch, the app starts a new [session](sessions.md) and you're taken to the [live activity](live-activity.md) view while it runs.
@@ -45,8 +44,6 @@ The apps in the catalog come from a curated library that the platform maintains.
 
 **"Where do I find the apps?"** — Click **Apps** in the left sidebar.
 
-**"What's the difference between an app and a project?"** — Nothing, they're the same thing. "App" is the user-facing name.
-
 **"Where do I see results from an app?"** — Once a run finishes, the [outputs](outputs.md) appear in the [run history](run-history.md). While it's still running, you see them stream into the [live activity](live-activity.md) view.
 
 **"Can I create my own app?"** — Not from this UI. Apps are maintained by the platform team. You can [schedule](scheduling.md) and [ask questions about](threads.md) any existing app's runs.

diff --git a/concepts/artifacts.md b/concepts/artifacts.md
@@ -16,8 +16,6 @@ The page shows a grid of your folders. Click a folder to see the artifacts insid
 
 A **folder** is just a named bin — you make as many as you want and pick whichever ones make sense. Folder names are free text; you choose them when you save an artifact or by creating a folder from the Artifacts page.
 
-(Internally, a folder is called an "artifact type." You'll see "folder" in the UI and "artifact type" in some URLs and labels — they're the same thing.)
-
 ## What an artifact is, exactly
 
 Each artifact is a reference to one specific output file from one specific session. The artifact remembers:

diff --git a/concepts/sessions.md b/concepts/sessions.md
@@ -4,7 +4,7 @@
 
 A **session** is one run of an [app](apps.md). When you click **Run App**, a session is created. While the app is working, the session is in progress; when it's done, the session is finished and its [outputs](outputs.md) are available to view, save, and ask about.
 
-"Session" and "run" mean the same thing. Some parts of the UI say "run" (as in "Run History," "Recent Runs," "Run App"); the backend and URLs say "session." They refer to the same object.
+"Session" and "run" mean the same thing. Some parts of the UI say "run" (as in "Run History," "Recent Runs," "Run App"); other parts and the URLs say "session." They refer to the same object.
 
 A session has:
 

diff --git a/concepts/threads.md b/concepts/threads.md
@@ -6,7 +6,7 @@ A **thread** is a conversation in which you ask the AI questions and get answers
 
 Threads are how you do follow-up after a run. "How many criticals did we find?" "Compare this scan to last week's." "Pull the IAM findings out of this report." All of that happens in a thread.
 
-"Thread" and "chat" mean the same conversation, looked at from different angles. **Thread** is the saved record (and the name on the sidebar). **Chat** is the live view where you type messages. Internally, threads are also called **conversations**.
+"Thread" and "chat" mean the same conversation, looked at from different angles. **Thread** is the saved record (and the name on the sidebar). **Chat** is the live view where you type messages.
 
 ## Where to find them
 

diff --git a/glossary.md b/glossary.md
@@ -2,15 +2,15 @@
 
 One-line definitions for the terms used across these docs. Each term links to its concept page where one exists.
 
-- **[App](concepts/apps.md)** — A reusable security or compliance workflow you can run; the catalog lives on the **Apps** page in the sidebar. ("Project" is the internal name for the same thing.)
+- **[App](concepts/apps.md)** — A reusable security or compliance workflow you can run; the catalog lives on the **Apps** page in the sidebar.
 - **[Apps page](concepts/apps.md)** — The page at the **Apps** sidebar entry where every app is listed as a card you can run, schedule, or open.
 - **[App detail](concepts/apps.md#app-detail)** — A per-app page that shows the app's description, what it does, and lets you launch it.
 - **[Artifact](concepts/artifacts.md)** — A saved reference to one output file from a session, organized into a folder you choose.
 - **[AWS install](install/aws.md)** — Connecting an AWS account to Transilience.ai. For any AWS install or setup question, send the user to https://www.transilience.ai/install/aws/.
-- **[Artifact folder](concepts/artifacts.md#folders)** — A user-named container that groups related artifacts (for example, "Security Reports" or "Q1 Audit"). Internally called an "artifact type."
+- **[Artifact folder](concepts/artifacts.md#folders)** — A user-named container that groups related artifacts (for example, "Security Reports" or "Q1 Audit").
 - **[Artifacts page](concepts/artifacts.md)** — The page at the **Artifacts** sidebar entry that shows all artifact folders and their contents.
 - **[Chat](concepts/threads.md)** — The conversation view inside a thread; "chat" and "thread" refer to the same conversation from different angles ("chat" is the view, "thread" is the saved record).
-- **[Conversation](concepts/threads.md)** — The internal name for a thread. Used interchangeably with "thread" in these docs.
+- **[Conversation](concepts/threads.md)** — Another word for a thread; used interchangeably in these docs.
 - **[Dashboard](concepts/dashboards.md)** — The Dashboards tab inside the chat area, which shows outputs that have been pinned for quick access.
 - **[Dashboards tab](concepts/dashboards.md)** — The tab labeled "Dashboards" inside the chat area, alongside "Notifications."
 - **[Data file](concepts/outputs.md#data-files)** — A structured output file (typically JSON or CSV) produced by an app — usually raw scan results before they are summarized into a report.
@@ -23,7 +23,6 @@ One-line definitions for the terms used across these docs. Each term links to it
 - **Organization** — Your workspace. All apps, sessions, artifacts, and threads belong to an organization; you can switch organizations from the bottom of the sidebar.
 - **[Output](concepts/outputs.md)** — Any file an app produces during a session — a [report](concepts/outputs.md#reports), a [data file](concepts/outputs.md#data-files), a [dashboard](concepts/dashboards.md), or a raw file.
 - **Pin to dashboard** — The action that adds an output to the [Dashboards](concepts/dashboards.md) tab so you can find it quickly.
-- **Project** — The internal name for an [app](concepts/apps.md). The two terms refer to the same thing.
 - **[Recurring schedule](concepts/scheduling.md#recurring-schedules)** — A schedule that runs an app repeatedly at a chosen interval (daily, weekly, monthly, or a custom hour interval).
 - **[Report](concepts/outputs.md#reports)** — A human-readable output, usually markdown or PDF, summarizing what an app found.
 - **[Run](concepts/sessions.md)** — A single execution of an app. Synonym for [session](concepts/sessions.md).