diff --git a/concepts/cuda-catalog-and-cache.mdx b/concepts/cuda-catalog-and-cache.mdx
index de374f8..863800a 100644
--- a/concepts/cuda-catalog-and-cache.mdx
+++ b/concepts/cuda-catalog-and-cache.mdx
@@ -13,7 +13,7 @@ Nix users first need to add `https://cache.flox.dev` to the list of `extra-subst
 
 This article covers how Flox and Nix users can consume pre-built CUDA packages from the Flox Catalog and Flox binary cache. **Flox users** can skip ahead to [Flox users: Getting pre-built CUDA dependencies from the Flox Catalog](#flox-users-getting-pre-built-cuda-dependencies-from-the-flox-catalog). **Nix users** can skip ahead to [Nix users: Getting CUDA packages from Flox's public binary cache](#nix-users-getting-cuda-packages-from-floxs-public-binary-cache).
 
-**Note**: The Flox binary cache depends on the voluntary work of the [Nixpkgs CUDA maintainers](https://nixos.org/community/teams/cuda/), who package and maintain NVIDIA's CUDA software for Nixpkgs. This team also tests PyTorch and other critical CUDA-accelerated packages against core NVIDIA CUDA dependencies, working tirelessly to make sure these packages build and link correctly against the evolving NVIDIA CUDA stack. CUDA-on-Nix would not be a reality without them.
+**Note**: The Flox binary cache depends on the voluntary work of the [Nixpkgs CUDA maintainers](https://nixos.org/community/teams/cuda/), who package and maintain NVIDIA's CUDA software for Nixpkgs. This team also tests PyTorch and other critical CUDA-accelerated packages against core NVIDIA CUDA dependencies, working tirelessly to make sure these packages build and link correctly against the ever-evolving NVIDIA CUDA stack. CUDA-on-Nix would not be a reality without them.
 
 
 ## CUDA dependencies and Nixpkgs
@@ -93,9 +93,9 @@ Flox builds [Nixpkgs' `release-cuda` jobset](https://github.com/nixos/nixpkgs/bl
 | Cache URL  | https://cache.flox.dev                                           |
 | Public Key | flox-cache-public-1:7F4OyH7ZCnFhcze3fJdfyXYLQw/aV7GEed86nQ7IsOs= |
 
-Which store paths are available in the cache depends on the specific Nixpkgs revisions that Flox builds against. Flox currently evaluates and builds CUDA packages against revisions from [its own Nixpkgs fork](https://github.com/flox/nixpkgs). This repo tracks the upstream `nixpkgs-unstable` branch across four distinct [Flox-maintained branches](/concepts/base-catalog#flox-branches): `unstable`, `staging`, `stable`, and `lts`.
+Which store paths are available in the cache depends on the specific Nixpkgs revisions that Flox builds against. Flox currently evaluates and builds CUDA packages against revisions from [its own Nixpkgs fork](https://github.com/flox/nixpkgs). This repo tracks the upstream `nixos-unstable` branch across four distinct [Flox-maintained branches](/concepts/base-catalog#flox-branches): `unstable`, `staging`, `stable`, and `lts`.
 
-These branch names describe Flox's Nixpkgs update schedules, *not* the stability of the software they reference. In general the `unstable` branch tracks upstream `nixpkgs-unstable` most closely (i.e., on a daily update schedule). Notably, Flox does not presently build against Nixpkgs release channels, so users that pin to revisions from these channels are unlikely to find matching CUDA store paths in the Flox cache. Because different Nixpkgs revisions can produce different store paths for the same package, **choosing a revision that Flox builds against significantly increases the chances of a cache hit**.
+These branch names describe Flox's Nixpkgs update schedules, *not* the stability of the software they reference. In general the `unstable` branch tracks upstream `nixos-unstable` most closely (i.e., on a daily update schedule). Notably, Flox does not presently build against Nixpkgs release channels, so users that pin to revisions from these channels are unlikely to find matching CUDA store paths in the Flox cache. Because different Nixpkgs revisions can produce different store paths for the same package, **choosing a revision that Flox builds against significantly increases the chances of a cache hit**.
 
 <Warning>
 NixOS users who do not want system builds to query the Flox cache for NVIDIA driver derivations and other CUDA package derivations should read [Control which builds query the Flox cache](#control-which-builds-query-the-flox-cache) before adding it to `extra-substituters`.