From b3e3c1a5733be4a640c63838c9130cc34407e052 Mon Sep 17 00:00:00 2001 From: Deborah <38264052+deborahniesz@users.noreply.github.com> Date: Tue, 22 Oct 2024 14:19:09 -0300 Subject: [PATCH] [DOCS] Fixing broken links (#10541) --- docs/docusaurus/docs/reference/api_reference.md | 2 +- .../docs/reference/learn/data_quality_use_cases/missingness.md | 2 +- .../version-0.18/reference/learn/terms/data_context.md | 2 +- 3 files changed, 3 insertions(+), 3 deletions(-) diff --git a/docs/docusaurus/docs/reference/api_reference.md b/docs/docusaurus/docs/reference/api_reference.md index a7e3dd7aebde..30a8ac0abf91 100644 --- a/docs/docusaurus/docs/reference/api_reference.md +++ b/docs/docusaurus/docs/reference/api_reference.md @@ -5,4 +5,4 @@ displayed_sidebar: gx_apis Great Expectations (GX) API reference content is generated from classes and methods docstrings. -If the code or documentation needs improvement, see the [contributor docs](https://docs.greatexpectations.io/docs/core/contribute/contribute), or submit your feedback on [Slack](https://greatexpectations.io/slack). +If the code or documentation needs improvement, see the [contributor docs](https://docs.greatexpectations.io/docs/core/introduction/community_resources/#contribute-code-or-documentation), or submit your feedback on [Slack](https://greatexpectations.io/slack). diff --git a/docs/docusaurus/docs/reference/learn/data_quality_use_cases/missingness.md b/docs/docusaurus/docs/reference/learn/data_quality_use_cases/missingness.md index 635a7650f3d5..b8e5625f8d1c 100644 --- a/docs/docusaurus/docs/reference/learn/data_quality_use_cases/missingness.md +++ b/docs/docusaurus/docs/reference/learn/data_quality_use_cases/missingness.md @@ -11,7 +11,7 @@ In this guide, you will learn how to leverage GX to effectively handle missing d ## Prerequisite knowledge -This article assumes basic familiarity with GX components and workflows. If you're new to GX, start with the [GX Overview](https://docs.greatexpectations.io/docs/guides/overview) to familiarize yourself with key concepts and setup procedures. +This article assumes basic familiarity with GX components and workflows. If you're new to GX, start with the [GX Overview](https://docs.greatexpectations.io/docs/cloud/overview/gx_cloud_overview/) to familiarize yourself with key concepts and setup procedures. ## Data preview diff --git a/docs/docusaurus/versioned_docs/version-0.18/reference/learn/terms/data_context.md b/docs/docusaurus/versioned_docs/version-0.18/reference/learn/terms/data_context.md index 9ee30f9f7e34..b52615ad2121 100644 --- a/docs/docusaurus/versioned_docs/version-0.18/reference/learn/terms/data_context.md +++ b/docs/docusaurus/versioned_docs/version-0.18/reference/learn/terms/data_context.md @@ -40,7 +40,7 @@ A Data Context includes basic create, read, update, and delete (CRUD) operations The Data Context helps you create components such as Data Sources, Checkpoints, and Expectation Suites and manage where the information about those components is stored. -For production deployments, you will want to define these components according to your Data Source and production environment. This may include storing information about those components in something other than your local environment. To view implementation examples for specific environments and Data Sources, see [Integrations](https://docs.greatexpectations.io/docs/category/integrations). +For production deployments, you will want to define these components according to your Data Source and production environment. This may include storing information about those components in something other than your local environment. To view implementation examples for specific environments and Data Sources, see [Integrations](https://greatexpectations.io/integrations/). ## GX Cloud compatibility