Remove lingering DO references

nebari-dev · Nov 18, 2024 · 9554d08 · 9554d08
1 parent 7728109
commit 9554d08
Show file tree

Hide file tree

Showing 2 changed files with 1 addition and 2 deletions.
diff --git a/docs/docs/explanations/advanced-configuration.md b/docs/docs/explanations/advanced-configuration.md
@@ -265,7 +265,6 @@ domain: demo.nebari.dev
 
 `provider`: Determines the cloud provider used to deploy infrastructure related resources on Nebari. Possible values are:
 
-- `do` for DigitalOcean
 - `aws` for Amazon Web Services
 - `gcp` for Google Could Provider
 - `azure` for Microsoft Azure

diff --git a/docs/docs/get-started/deploy.mdx b/docs/docs/get-started/deploy.mdx
@@ -29,7 +29,7 @@ If you are not sure which option to choose, a cloud installation is likely your
 :::note
 The cloud installation is based on Kubernetes, but knowledge of Kubernetes is **NOT** required nor is in-depth knowledge about the specific provider required either.
 
-Currently, Nebari supports [Amazon AWS][nebari-aws], [DigitalOcean][nebari-do], [Google GCP][nebari-gcp], and [Azure][nebari-azure].
+Currently, Nebari supports [Amazon AWS][nebari-aws], [Google GCP][nebari-gcp], and [Azure][nebari-azure].
 :::
 
 </TabItem>