Skip to content

Colota - Android GPS Location tracker

fix(docs): correct three screen paths that name screens the app does not have (#659)

Max Dietrichffc6dc723b9b
diff --git a/apps/docs/docs/api-reference.md b/apps/docs/docs/api-reference.md
index 6a5502b3..39d6271f 100644
--- a/apps/docs/docs/api-reference.md
+++ b/apps/docs/docs/api-reference.md
@@ -10,7 +10,7 @@ Reference for the HTTP requests Colota sends to your server.
**Method:** `POST` (default) or `GET`
-Configure the HTTP method in **Settings > API Settings > HTTP Method**.
+Configure the HTTP method in **Settings → API Field Mapping → HTTP Method**.
### POST (default)
diff --git a/apps/docs/docs/configuration/authentication.md b/apps/docs/docs/configuration/authentication.md
index a832678f..6c50ffad 100644
--- a/apps/docs/docs/configuration/authentication.md
+++ b/apps/docs/docs/configuration/authentication.md
@@ -6,7 +6,7 @@ sidebar_position: 5
import ScreenshotGallery from '@site/src/components/ScreenshotGallery'
-Colota supports multiple authentication methods, configurable in **Settings > Authentication & Headers**.
+Colota supports multiple authentication methods, configurable in **Settings → Connection → Authentication & Headers**.
<ScreenshotGallery screenshots={[ { src: "/img/screenshots/Authentication.png", label: "Authentication" }, ]} />
diff --git a/apps/docs/docs/guides/deep-link-setup.md b/apps/docs/docs/guides/deep-link-setup.md
index 95949cc4..d964ca07 100644
--- a/apps/docs/docs/guides/deep-link-setup.md
+++ b/apps/docs/docs/guides/deep-link-setup.md
@@ -16,7 +16,7 @@ Fill in the settings you want to configure. Only the fields you set will be incl
## Sharing From the App
-You can also generate a setup link straight from an existing installation, without the browser generator. Open **Settings -> Share Setup**, tick which categories to include - Tracking, Sync, API, Geofences, Profiles and Credentials - and tap **Share** to send the `colota://setup` link through any app.
+You can also generate a setup link straight from an existing installation, without the browser generator. Open **Settings → Share Setup**, tick which categories to include - Tracking, Sync, API, Geofences, Tracking profiles and Credentials - and tap **Share** to send the `colota://setup` link through any app.
Credentials are off by default. Enabling them puts your username, password, bearer token or custom headers into the link in plain text, so only share it over a trusted channel.
diff --git a/apps/docs/docs/security.md b/apps/docs/docs/security.md
index 054e8d3f..a4ff7e52 100644
--- a/apps/docs/docs/security.md
+++ b/apps/docs/docs/security.md
@@ -15,7 +15,7 @@ HTTPS is enforced for all public server endpoints. HTTP is only allowed for priv
Colota's HTTPS chain validation accepts two trust sources, either of which is sufficient:
1. **System CAs** that ship with Android - the normal public web (Let's Encrypt, DigiCert, etc.)
-2. **In-app imported CA** added via Settings -> Authentication & Headers -> Client Certificate (mTLS) -> Trusted Server CA. One slot, trusted only by Colota.
+2. **In-app imported CA** added via Settings → Connection → Authentication & Headers → Client Certificate (mTLS) → Trusted Server CA. One slot, trusted only by Colota.
User-installed device CAs (from Android Settings -> Encryption & credentials) are not honored, so malware or a coerced profile that plants a CA in the device store can't intercept Colota's sync. Self-hosted users running a private CA should import it via the in-app path.