consolidate client platforms

content/docs/development/system-architecture.mdx

@@ -97,7 +97,7 @@ How Olm is hosted depends on the client:
 - **Pangolin CLI** — spawns Olm as a subprocess and manages it over a local API
 - **Olm CLI** — exposes Olm directly for minimal machine-client deployments
 
-Olm is an internal building block, not a product surface. Use the [native clients](/manage/clients/install-client) built for each operating system for the best experience, support, and integration with OS networking APIs. Direct Olm usage is limited to advanced machine-client and automation scenarios; see [Olm (Advanced)](/manage/clients/install-client#olm-advanced) if you need that path.
+Olm is an internal building block, not a product surface. Use the [native clients](/manage/clients/platforms) built for each operating system for the best experience, support, and integration with OS networking APIs. Direct Olm usage is limited to advanced machine-client and automation scenarios; see [Olm](/manage/clients/platforms/olm) if you need that path.
 
 Once connected, the client installs routes for each authorized destination. Pangolin selects the correct site connector automatically; users connect to resources, not to sites directly. See [multi-site routing](/manage/resources/private/multi-site-routing) for how failover works when a resource spans multiple connectors.
 
@@ -106,8 +106,8 @@ Once connected, the client installs routes for each authorized destination. Pang
   User devices, machine clients, and how access is granted.
 </Card>
 
-<Card title="Install clients" icon="download" href="/manage/clients/install-client">
-  Downloads for Mac, Windows, Linux, iOS, iPadOS, and Android.
+<Card title="Platforms" icon="download" href="/manage/clients/platforms">
+  Install, configure, and update clients for Mac, Windows, Linux, iOS, iPadOS, and Android.
 </Card>
 </CardGroup>