From ffbf19181228c9e9d786fdad033d743ceed09fad Mon Sep 17 00:00:00 2001
From: Marisa Smith <66020208+mesmith027@users.noreply.github.com>
Date: Sun, 2 Oct 2022 19:07:46 -0400
Subject: [PATCH] updated intro paragraph (#7833)

Expanded intro to better tell the story, link the Great expectations webpage and docs.
---
 .../content/openmetadata/integrations/great-expectations.md     | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/openmetadata-docs/content/openmetadata/integrations/great-expectations.md b/openmetadata-docs/content/openmetadata/integrations/great-expectations.md
index 4448632d3b1..0b45b29ab4d 100644
--- a/openmetadata-docs/content/openmetadata/integrations/great-expectations.md
+++ b/openmetadata-docs/content/openmetadata/integrations/great-expectations.md
@@ -4,7 +4,7 @@ slug: /openmetadata/integrations/great-expectations
 ---
 
 # Great Expectations
-Configure Great Expectations to integrate with OpenMetadata and ingest your tests results to your table service page.
+For Data Quality tests the open source python package Great Expectations stands out from the crowd. For those of you who don't know, [Great Expectations](https://greatexpectations.io/) is a shared, open standard for data quality. It helps data teams eliminate pipeline debt, through data testing, documentation, and profiling. Learn more about the product in [their documentation](https://docs.greatexpectations.io/docs/).  With this tutorial, we show you how to configure Great Expectations to integrate with OpenMetadata and ingest your test results to your table service page.
 
 ## Requirements