From 35660699d88bb0aa19d7247678a4759413aa6e7a Mon Sep 17 00:00:00 2001 From: PlanetScale Actions Bot Date: Wed, 17 Jul 2024 18:37:27 +0000 Subject: [PATCH] docs: upstream https://github.com/planetscale/www/commit/5d2e13ff7f6a3b093afad0f556a2b729b9d904e7 --- docs/concepts/security.md | 2 +- docs/enterprise/managed/gcp/back-up-and-restore.md | 2 +- docs/enterprise/vschema.md | 2 +- docs/integrations/vantage.md | 2 +- 4 files changed, 4 insertions(+), 4 deletions(-) diff --git a/docs/concepts/security.md b/docs/concepts/security.md index 560af61c..537af7c6 100644 --- a/docs/concepts/security.md +++ b/docs/concepts/security.md @@ -21,7 +21,7 @@ Below is a breakdown of common security and compliance requirements by PlanetSca | [Private database connectivity](/docs/concepts/security#private-database-connectivity) | ❌ | ❌ | ✔ | ✔ | | Dedicated AWS/GCP account | ❌ | ❌ | ✔ | ✔ | | [PCI compliant](/docs/concepts/security#pci-compliance) | ❌ | ❌ | ❌ | ✔ (on AWS) | -| [Your own AWS/GCP account](/security#deploy-in-your-own-aws-or-gcp-account) | ❌ | ❌ | ❌ | ✔ | +| [Your own AWS/GCP account](/docs/concepts/security#deploy-in-your-own-aws-or-gcp-account) | ❌ | ❌ | ❌ | ✔ | ## Available on all PlanetScale plans diff --git a/docs/enterprise/managed/gcp/back-up-and-restore.md b/docs/enterprise/managed/gcp/back-up-and-restore.md index 6f2c21d6..71b1b6c4 100644 --- a/docs/enterprise/managed/gcp/back-up-and-restore.md +++ b/docs/enterprise/managed/gcp/back-up-and-restore.md @@ -7,7 +7,7 @@ date: '2023-11-06' PlanetScale Managed backup and restore functions like the hosted PlanetScale product. For more info, see [how to create, schedule, and restore backups for your PlanetScale databases](/docs/concepts/back-up-and-restore). -To learn more about the backup and restore access levels, see the [database level permissions documentation](/access-control#database-level-permissions). +To learn more about the backup and restore access levels, see the [database level permissions documentation](/docs/concepts/access-control#database-level-permissions). By default, databases are automatically backed up once per day to a Cloud Storage bucket in the customer's GCP project. This default can be adjusted when working with PlanetScale Support. However, configuring and validating additional backup frequencies is the customer's responsibility. diff --git a/docs/enterprise/vschema.md b/docs/enterprise/vschema.md index ef9f6ab9..1f9db84e 100644 --- a/docs/enterprise/vschema.md +++ b/docs/enterprise/vschema.md @@ -32,4 +32,4 @@ From here, you can inspect your VSchema configuration JSON file. ![VSchema JSON view](/assets/docs/enterprise/vschema.png) Vschema cannot be modified from this menu. -If you need this modified, please reach out to your account manager or [PlanetScale Support](https://planetscale.com/contact). +If you need this modified, please reach out to your account manager or [PlanetScale Support](/contact). diff --git a/docs/integrations/vantage.md b/docs/integrations/vantage.md index 46b56672..6dded8e7 100644 --- a/docs/integrations/vantage.md +++ b/docs/integrations/vantage.md @@ -17,7 +17,7 @@ Beyond reporting, set up budget alerts, forecast usage, and view active database - A [Vantage account](https://console.vantage.sh/signup) {% callout type="note" %} -Database cost reporting in Vantage is not available for [PlanetScale Managed](docs/enterprise/managed/overview) customers via the integration. +Database cost reporting in Vantage is not available for [PlanetScale Managed](/docs/enterprise/managed/overview) customers via the integration. {% /callout %} ## Configure the Vantage integration