Enforce style guide: fix long sentence and Windows path display

datumctl/quickstart.mdx

@@ -1,7 +1,7 @@
 ---
 title: "Quickstart"
 sidebarTitle: "Quickstart"
 description: "Install datumctl, log in, pick a context, and run your first command."
 ---
 
 This guide takes you from nothing installed to running your first command against Datum Cloud. Follow the steps in order — the whole path takes just a few minutes.
@@ -49,7 +49,7 @@
         For a one-off invocation without adding `datumctl` to your profile, use `nix run github:datum-cloud/datumctl` instead.
       </Tab>
       <Tab title="Windows">
-        Download the latest Windows release from the [GitHub Releases page](https://github.com/datum-cloud/datumctl/releases/latest), extract it, and move `datumctl.exe` to a directory such as `C:\\Tools\\datumctl\\`.
+        Download the latest Windows release from the [GitHub Releases page](https://github.com/datum-cloud/datumctl/releases/latest), extract it, and move `datumctl.exe` to a directory such as `C:\Tools\datumctl\`.
 
         Add that directory to your `PATH`, then open a new terminal.
       </Tab>
@@ -149,18 +149,18 @@
     Find which resource types exist and inspect their fields before you author manifests.
   </Card>
   <Card title="Output formats & scripting" icon="terminal" href="/datumctl/output-and-scripting">
     Machine-readable output, structured errors, and wrapping datumctl in CI and agents.
   </Card>
   <Card title="Interactive console" icon="table-columns" href="/datumctl/console">
     Browse and inspect resources in a full-screen, keyboard-driven UI.
   </Card>
   <Card title="Using plugins" icon="puzzle-piece" href="/datumctl/plugins/using-plugins">
     Extend datumctl with additional commands from a plugin catalog.
   </Card>
   <Card title="Managing accounts" icon="key" href="/datumctl/auth/managing-accounts">
     Manage multiple accounts, switch users, sign out, and print access tokens.
   </Card>
   <Card title="Overview" icon="compass" href="/datumctl/overview">
     Understand how datumctl is structured and how it talks to Datum Cloud.
   </Card>
 </CardGroup>

platform/locations.mdx

@@ -3,7 +3,7 @@
 description: "Datum's global footprint of Regions and Availability Zones, and how to check which locations are available to use in your project"
 ---
 
 Datum’s infrastructure footprint is organized into points of presence (PoPs) that are packaged into Regions and Availability Zones (AZs). See our [Locations](https://www.datum.net/locations/) for a visual overview of all PoPs.
 
 Each Region represents a specific geographic and network boundary, while each AZ provides independent capacity within that Region. This structure supports predictable latency, fault isolation, and regulatory alignment.
 
@@ -24,13 +24,13 @@
 
 `Example: us-east-1a`
 
 Regions and AZs are defined by distance and policy boundaries.
 
 - When Points of Presence in the same country are separated by more than about 5 milliseconds round-trip time (RTT), Datum creates a new Region.
 - If multiple PoPs exist in the same metro but operate independently (for example, separate network clusters or facilities), they become separate AZs. Increment the Count value to the next letter.
 - If PoPs are within about 5 milliseconds RTT and part of the same operational domain, they remain in the same Region. Example: us-east-1a, us-east-1b, us-east-1c.
 
 _Note: regulatory and export control requirements may restrict or define where data and workloads can reside. These boundaries take precedence over latency-based placement rules._
 
 ## Regions
 
@@ -38,7 +38,7 @@
 | --- | --- |
 | ae-north-1 | Dubai |
 | au-east-1 | Sydney |
 | br-east-1 | São Paolo |
 | ca-east-1 | Toronto |
 | cl-central-1 | Santiago |
 | de-central-1 | Frankfurt |
@@ -48,14 +48,14 @@
 | nl-west-1 | Amsterdam |
 | sg-central-1 | Singapore |
 | us-central-1 | Dallas |
 | us-east-1 | Ashburn |
 | us-east-2 | New York City |
 | us-west-1 | San Jose, California |
 | za-central-1 | Johannesburg |
 
 ## Check what's available to your project
 
-The table above is Datum's global footprint. What you can deploy into is a narrower, per-project question: Datum represents each usable location as a `Location` resource, and the ones inside your project's own control plane are the ones offered to you.
+The table above is Datum's global footprint. What you can deploy into is a narrower, per-project question. Datum represents each usable location as a `Location` resource, and the ones inside your project's own control plane are the ones available to you.
 
 `datumctl get locations` lists them:
 
@@ -69,7 +69,7 @@
 us-east-1      datum-managed   IAD    20h
 ```
 
 Each row is a location you can place work in today. `NAME` is the identifier you reference elsewhere, and matches the region codes in the table above: `us-central-1` is Dallas, `us-east-1` is Ashburn. `CITY` is the airport-style code for the metro it serves. `CLASS` is the kind of capacity behind it, where `datum-managed` is Datum's own footprint.
 
 <Tip>
   This list reflects your active project scope. If a location you expect is missing, confirm you are pointed at the right project. See [Contexts & scoping](/datumctl/contexts-and-scoping).
@@ -96,7 +96,7 @@
 
 ## Region tracing
 
 Visit [<u>https://edge.datum.net/</u>](https://edge.datum.net/) to learn which Datum Region and availability zone you're reaching via anycast. If you're using Datum Tunnels, this will be your entrypoint into our network.
 
 You can also access our zones and locations programmatically: