diff --git a/_visualize/input_lists.json b/_visualize/input_lists.json
index 466c3031c..d7dac0c79 100644
--- a/_visualize/input_lists.json
+++ b/_visualize/input_lists.json
@@ -54,7 +54,6 @@
         "hpc/dcp",
         "hpc/mpifileutils",
         "hpc/openlorenz",
-        "hpc/spindle",
         "hpcgroup/ariesncl",
         "hpcgroup/bgqncl",
         "hpcgroup/chatterbug",
diff --git a/about/faq.md b/about/faq.md
index b4f7411e2..c415802aa 100644
--- a/about/faq.md
+++ b/about/faq.md
@@ -164,7 +164,9 @@ If you've set up your repository within the **LLNL organization**, you don't nee
     * See also [GitHub's instructions](https://docs.github.com/en/repositories/creating-and-managing-repositories/transferring-a-repository) for transferring a repo.
     * Sometimes the transferring organization wants to retain a copy (mirror or fork) of the repo, or a project lead "takes" the repo with them to another organization.
 
-* **Standalone organization.** Alternatively, if you do not wish to transfer your repo, you can instead submit a pull request updating the [`input_lists.json` file](https://github.com/LLNL/llnl.github.io/blob/main/_visualize/input_lists.json) with your organization and/or repository names. List your organization under the `"orgs"` line *only if you intend for all of its repositories to be included in the catalog* (e.g., `glvis`); otherwise, list only the repository under the `"repos"` line within the context of your organization (e.g., `hpc/spindle`).
+* **Standalone organization.** Alternatively, if you do not wish to transfer your repo, you can instead submit a pull request updating the [`input_lists.json` file](https://github.com/LLNL/llnl.github.io/blob/main/_visualize/input_lists.json) with your organization and/or repository names. List your organization under the `"orgs"` line *only if you intend for all of its repositories to be included in the catalog* (e.g., `glvis`); otherwise, list only the repository under the `"repos"` line within the context of your organization (e.g., `ceed/laghos`).
+
+    * If you transfer your repo *from* a standalone organization into the LLNL org, please remove it from `"orgs"` in the [`input_lists.json` file](https://github.com/LLNL/llnl.github.io/blob/main/_visualize/input_lists.json). You don't need to explicitly add it to the LLNL org in the JSON file; all public repos under the LLNL org are automatically pulled into the catalog.
 
 If you have a **project logo**, please follow the [Contributing Guidelines](/about/contribute) (see the question [How do I change how a specific repo appears in the catalog?](https://software.llnl.gov/about/contribute/#catalog)) for naming and uploading the file. If your repo is part of a non-LLNL organization that has its own avatar, that image will automatically display next to the repo name in the catalog, unless superseded by a repo-specific logo.