diff --git a/content/pages/docs/zoo-design-studio/features/data-management/aquarium.mdx b/content/pages/docs/zoo-design-studio/features/data-management/aquarium.mdx
index e4df86a4..37f9c2eb 100644
--- a/content/pages/docs/zoo-design-studio/features/data-management/aquarium.mdx
+++ b/content/pages/docs/zoo-design-studio/features/data-management/aquarium.mdx
@@ -33,10 +33,10 @@ non-empty KCL file without errors open in the project. The `Publish` button is d
current KCL file is empty or has errors.
Publishing requires the project to be stored in Personal Cloud. If you publish a project from a
-Directory library on desktop, the submission dialog warns that a successful submission will move
-the project folder into the managed Personal Cloud folder. Zoo Design Studio closes the project,
-moves it rather than leaving a second copy behind, then reopens it from Personal Cloud and starts
-cloud sync. Projects already in Personal Cloud do not move. In the browser, projects are already
+local library on desktop, the submission dialog warns that a successful submission will move the
+project folder into the managed Personal Cloud folder. Zoo Design Studio closes the project, moves
+it rather than leaving a second copy behind, then reopens it from Personal Cloud and starts cloud
+sync. Projects already in Personal Cloud do not move. In the browser, projects are already
cloud-backed.
To submit a project:
@@ -86,7 +86,7 @@ public Aquarium model.
## Keep or Remove a Publication
The cloud project powers its Aquarium entry. Moving a published project from Personal Cloud to a
-Directory library makes the project local-only by deleting the cloud project, which also deletes
+local library makes the project local-only by deleting the cloud project, which also deletes
the public Aquarium entry. Deleting the project from Personal Cloud has the same effect.
Keep the editable project in Personal Cloud while you want its Aquarium publication to remain
@@ -97,7 +97,7 @@ available.
Keep the model files organized before publishing. Clear names, stable KCL files, and meaningful
parameters make the shared model easier to understand and reuse.
-If a Directory project uses Git or another version-control system, commit and push or back up the
+If a local project uses Git or another version-control system, commit and push or back up the
repository before publishing. The repository folder moves into managed Personal Cloud storage, but
version-control metadata is not uploaded. Cloud operations that replace the managed working copy
can remove excluded local content such as `.git` and ignored files. Consider keeping another clone
diff --git a/content/pages/docs/zoo-design-studio/features/data-management/cloud-sync.mdx b/content/pages/docs/zoo-design-studio/features/data-management/cloud-sync.mdx
index 32dad9f1..69e1cfe9 100644
--- a/content/pages/docs/zoo-design-studio/features/data-management/cloud-sync.mdx
+++ b/content/pages/docs/zoo-design-studio/features/data-management/cloud-sync.mdx
@@ -10,17 +10,17 @@ not automatically upload every project on your computer.
- **Personal Cloud projects sync.** They are stored in your Zoo account so you can open them in the
browser and on other devices. On desktop, Zoo Design Studio also keeps a working copy in a
separate, managed folder while you edit.
-- **Directory projects do not sync.** They stay in the folder you chose on that computer unless you
- move them to Personal Cloud or publish them to Aquarium. Publishing automatically moves a
- Directory project to Personal Cloud after a successful submission.
+- **Projects in local libraries do not sync.** They stay in the folder you chose on that computer
+ unless you move them to Personal Cloud or publish them to Aquarium. Publishing automatically moves
+ a local project to Personal Cloud after a successful submission.
-## Directory, Personal Cloud, and Aquarium
+## Local Projects, Personal Cloud, and Aquarium
These names describe three different parts of project storage and sharing:
| Name | What it means |
| --- | --- |
-| Directory library | Editable project files stored in a folder you choose on one computer. The project is not synced or public while it remains there. |
+| Local Projects | Editable project files stored in a folder you choose on one computer. The project is not synced or public while it remains there. |
| Personal Cloud | An editable project stored privately in your Zoo account, plus a working copy on the device where you open it. |
| Aquarium | A reviewed, public version of a Personal Cloud project. Aquarium is a gallery, not another project library. |
@@ -32,14 +32,14 @@ When you change a Personal Cloud project, Zoo Design Studio saves the change to
first and syncs it to your Zoo account in the background. You can then open the latest synced
version in the browser or on another device signed in to the same Zoo account.
-Zoo Design Studio adds Personal Cloud automatically for signed-in users. On desktop
-Home, it appears beside Directory libraries with a cloud icon.
-Directory libraries have folder icons and show normal paths on your computer, the default one is titled "Default Projects Directory".
-In the browser, Personal Cloud is the only project library.
+Zoo Design Studio adds Personal Cloud automatically for signed-in users. On desktop Home, it appears
+beside local libraries with a cloud icon. Local libraries have folder icons and show normal paths on
+your computer. The default local library is named `Local Projects`, but the example below uses the
+custom title `Workshop Projects`. In the browser, Personal Cloud is the only project library.
@@ -52,13 +52,13 @@ In the browser, Personal Cloud is the only project library.
/>
The Home status `Cloud synced` describes the projects in Personal Cloud. It does not mean that
-projects in Directory libraries have been uploaded.
+projects in local libraries have been uploaded.
## Common Workflows
### Use a Project on Another Device
-1. Create the project in Personal Cloud or move an existing Directory project there.
+1. Create the project in Personal Cloud or move an existing local project there.
2. Wait for Home to show `Cloud synced`.
3. Sign in to Zoo Design Studio with the same account on the other device or in a browser.
4. Open the project from Personal Cloud. Zoo Design Studio downloads a working copy when needed.
@@ -70,7 +70,7 @@ projects in Directory libraries have been uploaded.
3. Wait for the publication status to become `Published`.
4. Share the public Aquarium URL.
-Publishing a Directory project moves it to Personal Cloud as part of a successful submission. See
+Publishing a local project moves it to Personal Cloud as part of a successful submission. See
[Aquarium](/docs/zoo-design-studio/features/data-management/aquarium) for publication details.
## Common Questions
@@ -78,9 +78,9 @@ Publishing a Directory project moves it to Personal Cloud as part of a successfu
### How Do I Know Which Projects Are Saved to the Cloud?
Check the library that contains the project on Home. Only projects in `Personal Cloud` are saved to
-your Zoo account. Projects in a Directory library are local-only, even while Cloud Sync is enabled.
-Move a Directory project to Personal Cloud when you want to start syncing it directly. Publishing a
-Directory project to Aquarium also moves it to Personal Cloud and starts syncing it.
+your Zoo account. Projects in local libraries are local-only, even while Cloud Sync is enabled. Move
+a local project to Personal Cloud when you want to start syncing it directly. Publishing a local
+project to Aquarium also moves it to Personal Cloud and starts syncing it.
### How Much Cloud Storage Do I Get?
@@ -109,7 +109,7 @@ site data.
### Where Do My Files Live?
-Personal Cloud does not use the folders configured for your Directory libraries. On desktop, each
+Personal Cloud does not use the folders configured for your local libraries. On desktop, each
cloud project gets a working copy in the managed Personal Cloud folder. You can see this folder's
path under `Settings` > `User` > `App` > `Libraries` and reveal it in your file explorer.
@@ -133,18 +133,18 @@ No. Cloud Sync keeps the current project available through your Zoo account, but
Git-style history, branches, or code review. Use Git or another backup system when you need revision
history or recovery outside the current synced project.
-### Does a Directory Project Still Use Zoo's Cloud Modeling?
+### Does a Local Project Still Use Zoo's Cloud Modeling?
-Yes. Project storage and modeling computation are separate. A project can remain local in a
-Directory library while Zoo Design Studio uses Zoo's cloud services to execute KCL, render the
-model, or perform other modeling operations. Cloud Sync controls where the project files are saved
-and synchronized; it does not determine where modeling computation runs.
+Yes. Project storage and modeling computation are separate. A project can remain in a local library
+while Zoo Design Studio uses Zoo's cloud services to execute KCL, render the model, or perform other
+modeling operations. Cloud Sync controls where the project files are saved and synchronized; it does
+not determine where modeling computation runs.
## Use Cloud Sync
### Start Syncing
-To start syncing a local Directory project directly, move it to `Personal Cloud`:
+To start syncing a local project, move it to `Personal Cloud`:
1. Select `Move to library` from the Command Bar, the project menu in the top bar, or the project
card context menu on Home.
@@ -159,16 +159,17 @@ on desktop, the project remains local in that folder until you enable it again.
Creating a project directly in `Personal Cloud` also starts it as a synced project. In the browser,
Personal Cloud is the only project library, so projects are cloud-backed by default.
-Publishing a Directory project to Aquarium also moves it into cloud storage. The submission dialog
+Publishing a local project to Aquarium also moves it into cloud storage. The submission dialog
warns about the move before you submit. After a successful submission, Zoo Design Studio moves the
folder to Personal Cloud, reopens it there, and starts cloud sync. Publishing a project that is
already in Personal Cloud does not move its working copy.
-{/* VIDEO PLACEHOLDER: Moving a Directory project to Personal Cloud and watching the sync status reach Cloud synced. */}
+{/* VIDEO PLACEHOLDER: Moving a project from a local library to Personal Cloud and watching the sync
+status reach Cloud synced. */}
@@ -191,19 +192,19 @@ Failed sync work stays queued and is retried automatically.
### Stop Syncing
-To make a synced project local-only, move it from `Personal Cloud` to a Directory library:
+To make a synced project local-only, move it from `Personal Cloud` to a local library:
1. Select `Move to library` from the Command Bar, the project menu in the top bar, or the project
card context menu on Home.
2. Choose the synced project.
-3. Choose a Directory library as the destination.
+3. Choose a local library as the destination.
4. Confirm the move.
Zoo Design Studio disconnects the project from cloud sync and moves the files into the selected
local library. The moved local copy is the project that remains, and future edits happen only in
-that Directory library unless you move the project back to `Personal Cloud`.
+that local library unless you move the project back to `Personal Cloud`.
-**Important:** Moving a project from Personal Cloud to a Directory library deletes the remote cloud
+**Important:** Moving a project from Personal Cloud to a local library deletes the remote cloud
project before moving the remaining local folder. The cloud project is no longer available in the
browser or on other devices. If the project has an Aquarium publication, deleting the cloud project
also deletes its public Aquarium entry. If remote deletion fails, Zoo Design Studio restores the
@@ -212,11 +213,11 @@ cloud link and the move fails.
Turning Cloud Sync off only pauses synchronization; it does not make a project local-only.
A cloud-only project must first be opened and downloaded before it can be moved.
-{/* VIDEO PLACEHOLDER: Moving a Personal Cloud project into a Directory library to make it local-only. */}
+{/* VIDEO PLACEHOLDER: Moving a Personal Cloud project into a local library to make it local-only. */}
@@ -229,7 +230,7 @@ If you delete a project from `Personal Cloud`, Zoo Design Studio deletes the clo
project has a local working copy on that device, the local working copy is removed too. Any Aquarium
publication backed by that cloud project is also deleted.
-If you delete a cloud-backed project from a Directory library, Zoo Design Studio deletes the
+If you delete a cloud-backed project from a local library, Zoo Design Studio deletes the
selected local folder. The cloud project remains in your Zoo account, and the delete dialog says
that the cloud version will not be deleted. Other local folders with the same cloud identity may be
removed if they are exact duplicates or disconnected if they differ.
@@ -238,7 +239,7 @@ Deletion from Personal Cloud propagates to other devices.
This is different from `Move to library`. Use `Move to library` when you want to change where a
project belongs. Use delete when you want to remove the project card from its current library.
-Moving from Personal Cloud to a Directory library also deletes the remote project, but preserves and
+Moving from Personal Cloud to a local library also deletes the remote project, but preserves and
relocates the selected local folder.
### Resolve a Conflict
@@ -343,7 +344,7 @@ Duplicate copies are handled conservatively:
- The canonical copy is kept.
- Extra local copies are not hidden just because they share the same cloud project ID.
-- Directory library copies are not silently deleted.
+- Local library copies are not silently deleted.
- Zoo Design Studio may clean up an exact duplicate in the cloud library only when it can prove that
copy matches the clean synced version.
- Pending, conflicted, unreadable, tombstoned, sync-excluded, or changed copies stay available for
diff --git a/content/pages/docs/zoo-design-studio/features/data-management/default-project-folder.mdx b/content/pages/docs/zoo-design-studio/features/data-management/default-project-folder.mdx
index d4228536..e057b985 100644
--- a/content/pages/docs/zoo-design-studio/features/data-management/default-project-folder.mdx
+++ b/content/pages/docs/zoo-design-studio/features/data-management/default-project-folder.mdx
@@ -1,11 +1,15 @@
---
-title: Default Project Folder
-excerpt: Understand how the legacy default project folder maps to Project Libraries.
+title: Local Projects
+excerpt: Understand the default local project library in Zoo Design Studio.
sidebarPosition: 5
---
-Project Libraries replaced the single Default Project Folder control in current Zoo Design Studio
-releases. The legacy `Project Directory` setting is no longer shown in Settings.
+`Local Projects` is the default local project library in the Zoo Design Studio desktop app. It keeps
+projects in a folder on your computer and does not sync them to your Zoo account.
+
+Older releases exposed this location as a single directory setting under a different name. Current
+releases manage it as a project library. You can rename Local Projects, change its folder, or add
+other local libraries.
Manage project locations under `Settings` > `User` > `App` > `Libraries`. See
[Project Libraries](/docs/zoo-design-studio/features/data-management/project-libraries) for the current
diff --git a/content/pages/docs/zoo-design-studio/features/data-management/index.mdx b/content/pages/docs/zoo-design-studio/features/data-management/index.mdx
index f2001bd5..6c7dd021 100644
--- a/content/pages/docs/zoo-design-studio/features/data-management/index.mdx
+++ b/content/pages/docs/zoo-design-studio/features/data-management/index.mdx
@@ -25,5 +25,5 @@ portable, inspectable, syncable, and practical to version with normal developer
organizing projects across local folders and cloud-backed libraries.
- [Cloud Sync](/docs/zoo-design-studio/features/data-management/cloud-sync) covers syncing projects
through your Zoo account and resolving sync conflicts.
-- [Default Project Folder](/docs/zoo-design-studio/features/data-management/default-project-folder)
- explains how the legacy single-folder setting maps to Project Libraries.
+- [Local Projects](/docs/zoo-design-studio/features/data-management/default-project-folder) explains
+ the default local project library and how it relates to the legacy single-folder setting.
diff --git a/content/pages/docs/zoo-design-studio/features/data-management/project-libraries.mdx b/content/pages/docs/zoo-design-studio/features/data-management/project-libraries.mdx
index 2b6ab619..ce0d62d3 100644
--- a/content/pages/docs/zoo-design-studio/features/data-management/project-libraries.mdx
+++ b/content/pages/docs/zoo-design-studio/features/data-management/project-libraries.mdx
@@ -7,16 +7,17 @@ sidebarPosition: 3
A project library is a place where Zoo Design Studio keeps projects. Libraries also organize the
projects you see on Home.
-On desktop, there are two choices:
+On desktop, projects can live in a local library or Personal Cloud:
-- **Directory** keeps projects in a folder you choose on your computer. These projects remain local
+- **Local Projects** is the default local library. It keeps projects in a folder on your computer.
+ You can change its folder, rename it, or add other local libraries. These projects remain local
unless you move them to Personal Cloud or publish them to Aquarium.
- **Personal Cloud** stores projects in your Zoo account so you can open them on other devices and
in the browser. Zoo Design Studio also keeps a local working copy while you edit on desktop.
-These are separate locations. Adding a Directory library does not sync its projects. To start
-syncing a Directory project directly, move it to Personal Cloud. Publishing a Directory project to
-Aquarium also moves it to Personal Cloud after a successful submission.
+These are separate locations. Projects in local libraries do not sync. To start syncing a local
+project directly, move it to Personal Cloud. Publishing a local project to Aquarium also moves it to
+Personal Cloud after a successful submission.
Aquarium is not a third library. It is a public gallery containing reviewed versions submitted from
Personal Cloud projects. Today, an unpublished Personal Cloud project remains private on both Free
@@ -24,49 +25,51 @@ and paid plans, and changing or canceling a subscription does not remove it. See
[Are Personal Cloud Projects Private?](/docs/zoo-design-studio/features/data-management/cloud-sync#are-personal-cloud-projects-private)
for the current visibility and data-use policy.
-**Only projects in Personal Cloud sync to your Zoo account. Projects remain local-only while they
-stay in a Directory library.**
+**Only projects in Personal Cloud sync to your Zoo account. Projects in local libraries remain
+local-only.**
Zoo Design Studio adds Personal Cloud automatically for signed-in users with Cloud Sync; you do not
need to create it yourself. On desktop Home, its cloud icon and `zoo://personal` address distinguish
-it from Directory libraries, which have folder icons and normal paths on your computer. In the
-browser, Personal Cloud is the default project library and may open directly.
+it from local libraries, which have folder icons and normal paths on your computer. The default local
+library is named `Local Projects`, but you can rename it; the example below uses `Workshop Projects`.
+In the browser, Personal Cloud is the default project library and may open directly.
## Choose a Library
-Zoo Design Studio currently supports two library types.
+Choose where a project lives based on whether you want it stored locally or synced through your Zoo
+account.
| Library | Where the project lives | Use it when |
| --- | --- | --- |
-| Directory | In a folder you choose on this computer. | You want local-only work, a specific folder, or a Git workflow. |
+| Local library | In a folder you choose on this computer. | You want local-only work, a specific folder, or a Git workflow. |
| Personal Cloud | In your Zoo account, plus a working copy on the device where you open it. | You want the project in the browser or on multiple devices. |
-### Directory Libraries
+### Local Projects
-A Directory library points to a normal folder on your computer. Each project is a subfolder inside
-that library folder. A Directory project stays in that folder and is not uploaded to Zoo unless you
-move it to Personal Cloud or submit it to Aquarium.
+Local Projects is the default local project library. It points to a normal folder on your computer,
+and each project is a subfolder inside that library folder. A project stays in that folder and is
+not uploaded to Zoo unless you move it to Personal Cloud or submit it to Aquarium.
-Directory libraries are available in the desktop app. Under `Settings` > `User` > `App` >
-`Libraries`, you can add more than one, rename them, choose different folders, reorder them, or remove
-them from Home. Changing a library path changes which folder Home scans; it does not move projects.
-Removing a Directory library does not delete its folder or projects on disk.
+Local libraries are available in the desktop app. Under `Settings` > `User` > `App` > `Libraries`,
+you can rename Local Projects, add more local libraries, choose different folders, reorder them, or
+remove them from Home. Changing a library path changes which folder Home scans; it does not move
+projects. Removing a local library does not delete its folder or projects on disk.
-Zoo Design Studio projects remain normal, readable files. You can open a Directory project in a text
+Zoo Design Studio projects remain normal, readable files. You can open a local project in a text
editor, search it, copy it, version it with Git, or use it with other filesystem tools.
### Personal Cloud
Personal Cloud stores projects in your Zoo account.
-On desktop, Personal Cloud uses its own managed folder, separate from your Directory libraries.
+On desktop, Personal Cloud uses its own managed folder, separate from your local libraries.
When you create or open a cloud project, Zoo Design Studio puts a working copy in that folder and
syncs your changes in the background. The Personal Cloud settings row shows the folder's path and
can reveal it in your file explorer.
@@ -76,7 +79,7 @@ cloud-only entries. Opening one downloads the project first, then opens the loca
@@ -94,15 +97,16 @@ configured library, Home goes directly to that library's projects.
From Home, choose `Create project`. If more than one writable library is available, the Create
project command includes a `Library` field.
-Creating a project in a Directory library creates a new folder inside that Directory library's path.
-Creating a project in Personal Cloud creates a local cloud working copy and starts cloud sync when
-sync is enabled.
+Creating a project in a local library creates a new folder inside that library's path. Creating a
+project in Personal Cloud creates a local cloud working copy and starts cloud sync when sync is
+enabled.
-{/* VIDEO PLACEHOLDER: Short walkthrough creating one project in a Directory library and one in Personal Cloud. */}
+{/* VIDEO PLACEHOLDER: Short walkthrough creating one project in a local library and one in Personal
+Cloud. */}
@@ -119,10 +123,10 @@ project menu in the top bar, or a project card's context menu on Home.
The result depends on the source and destination:
-- Directory to Directory moves the project folder between local library paths.
-- Directory to Personal Cloud moves it into managed cloud storage and starts cloud sync.
-- Personal Cloud to Directory deletes the remote cloud project, disconnects the local copy, and
- moves that remaining folder to the Directory library.
+- Local library to local library moves the project folder between local library paths.
+- Local library to Personal Cloud moves it into managed cloud storage and starts cloud sync.
+- Personal Cloud to local library deletes the remote cloud project, disconnects the local copy, and
+ moves that remaining folder to the local library.
A cloud-only project must be opened before it can be moved. Moving out of Personal Cloud also
requires Cloud Sync to be enabled.
@@ -135,23 +139,24 @@ the cloud link.
This is the preferred way to move projects between libraries. It lets Zoo Design Studio update the
project files, library membership, and cloud sync metadata together.
-Publishing a Directory project to Aquarium is a special case of the Directory-to-Personal-Cloud
-move. The publishing dialog discloses the storage change before submission. After a successful
+Publishing a local project to Aquarium is a special case of moving from a local library to Personal
+Cloud. The publishing dialog discloses the storage change before submission. After a successful
submission, Zoo Design Studio moves the project folder into Personal Cloud and reopens it there; it
-does not leave another project in the Directory library.
+does not leave another project in the local library.
-{/* VIDEO PLACEHOLDER: Moving a local project into Personal Cloud, then moving it back to a Directory library. */}
+{/* VIDEO PLACEHOLDER: Moving a project from a local library into Personal Cloud, then moving it
+back. */}
@@ -160,8 +165,8 @@ does not leave another project in the Directory library.
Deleting a project follows the library it belongs to:
-- Deleting from a Directory library removes the local project folder.
-- Deleting a cloud-backed copy from a Directory library removes the selected folder but keeps the
+- Deleting from a local library removes the local project folder.
+- Deleting a cloud-backed copy from a local library removes the selected folder but keeps the
cloud project. Other local folders with the same cloud identity may be removed if they are exact
duplicates or disconnected if they differ.
- Deleting from `Personal Cloud` deletes the cloud project and removes the local working copy on the
@@ -174,8 +179,8 @@ Read the confirmation dialog before deleting. Project deletion is permanent and
### Desktop and Browser Differences
-On desktop, Zoo Design Studio can show Directory and Cloud libraries side by side. This lets you keep
-local-only work, Git-based work, and cloud-backed work in one Home view.
+On desktop, Zoo Design Studio can show local libraries and Personal Cloud side by side. This lets
+you keep local-only work, Git-based work, and cloud-backed work in one Home view.
In the browser, Zoo Design Studio uses `Personal Cloud`. Its working copy lives in browser storage,
not in a normal folder that you can manage in Finder, File Explorer, or a terminal. You can edit the
diff --git a/content/pages/docs/zoo-design-studio/features/data-management/version-control/index.mdx b/content/pages/docs/zoo-design-studio/features/data-management/version-control/index.mdx
index a18329e7..df9584ba 100644
--- a/content/pages/docs/zoo-design-studio/features/data-management/version-control/index.mdx
+++ b/content/pages/docs/zoo-design-studio/features/data-management/version-control/index.mdx
@@ -16,9 +16,8 @@ records intentional revision history and reviewable changes.
## Git and Project Libraries
-Use a Directory library when you want a project to remain in a normal folder whose location you
-control. This is the most direct fit for a Git working tree and other filesystem-based development
-tools.
+Use a local library when you want a project to remain in a normal folder whose location you control.
+This is the most direct fit for a Git working tree and other filesystem-based development tools.
Personal Cloud uses a managed working-copy folder on desktop. Cloud Sync uploads project files but
excludes version-control metadata directories such as `.git`, `.hg`, `.svn`, and `.jj`. Those
@@ -29,7 +28,7 @@ remove excluded local files. See
## Publish a Version-Controlled Project
-Publishing a Directory project to Aquarium moves the entire project folder into Personal Cloud
+Publishing a local project to Aquarium moves the entire project folder into Personal Cloud
after a successful submission. Local version-control metadata moves with the folder, but it is not
uploaded or protected by Cloud Sync.
diff --git a/content/pages/docs/zoo-design-studio/features/index.mdx b/content/pages/docs/zoo-design-studio/features/index.mdx
index ba8894fa..aa30ab2f 100644
--- a/content/pages/docs/zoo-design-studio/features/index.mdx
+++ b/content/pages/docs/zoo-design-studio/features/index.mdx
@@ -49,9 +49,8 @@ Studio models into downstream analysis tools while preserving parametric source
### Data Management
-[Data Management](/docs/zoo-design-studio/features/data-management) covers project storage, project
-libraries, cloud sync, import and export workflows, default project folders, and code-based
-version-control workflows.
+[Data Management](/docs/zoo-design-studio/features/data-management) covers project libraries, cloud
+sync, import and export workflows, and code-based version control.
### Technical Support
diff --git a/content/pages/docs/zoo-design-studio/features/system-requirements/index.mdx b/content/pages/docs/zoo-design-studio/features/system-requirements/index.mdx
index 764d9fbc..a3bdd280 100644
--- a/content/pages/docs/zoo-design-studio/features/system-requirements/index.mdx
+++ b/content/pages/docs/zoo-design-studio/features/system-requirements/index.mdx
@@ -27,7 +27,7 @@ local machine, though a stable network connection is still important for respons
## Platform Differences
- Both versions support multiple project files and projects.
-- On desktop, Directory libraries can point to normal folders on disk. The web version only works with projects from Personal
- Cloud.
+- On desktop, local libraries can point to normal folders on disk. The web version only works with
+ projects from Personal Cloud.
- Operating-system integrations such as `Reveal in file explorer`, `New Window`, and
`Export to Slicer` are desktop workflows.
diff --git a/content/pages/docs/zoo-design-studio/features/system-requirements/zoo-stream/index.mdx b/content/pages/docs/zoo-design-studio/features/system-requirements/zoo-stream/index.mdx
index 6e536da4..419f0930 100644
--- a/content/pages/docs/zoo-design-studio/features/system-requirements/zoo-stream/index.mdx
+++ b/content/pages/docs/zoo-design-studio/features/system-requirements/zoo-stream/index.mdx
@@ -115,10 +115,10 @@ centrally.
Zoo Design Studio Stream is about execution and visualization. It does not change the app's
source-file storage model.
-Directory-library projects remain in folders on your desktop computer. Personal Cloud projects
-remain stored in your Zoo account, with a working copy in a managed desktop folder or
-browser-managed cache. The cloud session receives the model data needed to run the engine and
-produce the interactive stream, but it does not decide where your project is stored.
+Projects in local libraries remain in folders on your desktop computer. Personal Cloud projects
+remain stored in your Zoo account, with a working copy in a managed desktop folder or browser-managed
+cache. The cloud session receives the model data needed to run the engine and produce the interactive
+stream, but it does not decide where your project is stored.
That split is the point: keep the control and portability of the app's project storage model while
using remote compute for the expensive CAD work.
diff --git a/content/pages/docs/zoo-design-studio/features/workspace/project-browser.mdx b/content/pages/docs/zoo-design-studio/features/workspace/project-browser.mdx
index 615483b6..8b026484 100644
--- a/content/pages/docs/zoo-design-studio/features/workspace/project-browser.mdx
+++ b/content/pages/docs/zoo-design-studio/features/workspace/project-browser.mdx
@@ -69,7 +69,7 @@ Zoo Design Studio adds a number, such as `-copy-1` or `-copy-2`.
- Cloud projects can appear before they are downloaded locally; opening one creates a local working
copy first.
- A cloud project can have duplicate local copies. The Project Browser keeps the canonical copy
- clear, shows duplicate copies for review, and does not silently delete Directory library copies.
+ clear, shows duplicate copies for review, and does not silently delete local library copies.
For project storage and sync details, see
[Project Libraries](/docs/zoo-design-studio/features/data-management/project-libraries) and
diff --git a/content/pages/docs/zoo-design-studio/features/workspace/settings/user-settings/app/index.mdx b/content/pages/docs/zoo-design-studio/features/workspace/settings/user-settings/app/index.mdx
index 11ecc90b..a39108ef 100644
--- a/content/pages/docs/zoo-design-studio/features/workspace/settings/user-settings/app/index.mdx
+++ b/content/pages/docs/zoo-design-studio/features/workspace/settings/user-settings/app/index.mdx
@@ -20,9 +20,9 @@ Whether to show the debug panel, a development tool.
Project libraries control which project sources appear on Home.
-On desktop, you can add, rename, reorder, and remove Directory libraries. A Directory library points
-to a folder on your computer. Removing the library from settings does not delete the projects in that
-folder.
+On desktop, `Local Projects` is the default local library. You can rename it, add more local
+libraries, choose their folders, reorder them, or remove them. Removing a library from settings does
+not delete the projects in that folder.
With Cloud Sync, the `Personal Cloud` library appears as a Cloud library. Its settings
row shows the resolved local storage path for the cloud working copy.
diff --git a/content/pages/docs/zoo-design-studio/features/workspace/top-bar.mdx b/content/pages/docs/zoo-design-studio/features/workspace/top-bar.mdx
index 6b5abd8b..a96e758c 100644
--- a/content/pages/docs/zoo-design-studio/features/workspace/top-bar.mdx
+++ b/content/pages/docs/zoo-design-studio/features/workspace/top-bar.mdx
@@ -54,7 +54,7 @@ description, and at least one category, then select `Submit for review`. Zoo Des
eligible files from the entire project folder, including subfolders. Files ignored by `.gitignore`,
version-control metadata, internal metadata, and the generated thumbnail are excluded.
-If the project is in a Directory library on desktop, the dialog also discloses that a successful
+If the project is in a local library on desktop, the dialog also discloses that a successful
submission moves the project into Personal Cloud and starts cloud sync. The Aquarium title is
currently also used as the project title, so it can rename the project and its desktop working-copy
folder.