From a87bcd50775c93aed91a725d71c4b66b0902422d Mon Sep 17 00:00:00 2001
From: Vividh Pandey <91251535+VividhPandey003@users.noreply.github.com>
Date: Sun, 13 Feb 2022 15:49:26 +0530
Subject: [PATCH] documentation: Add Third Party Schema

Solved issue: #34243
---
 packages/gatsby/src/redux/actions/restricted.ts | 7 ++++---
 1 file changed, 4 insertions(+), 3 deletions(-)

diff --git a/packages/gatsby/src/redux/actions/restricted.ts b/packages/gatsby/src/redux/actions/restricted.ts
index 4c01c88586dae..cb105dfa6ddd9 100644
--- a/packages/gatsby/src/redux/actions/restricted.ts
+++ b/packages/gatsby/src/redux/actions/restricted.ts
@@ -37,9 +37,10 @@ export const actions = {
    * Add a third-party schema to be merged into main schema. Schema has to be a
    * graphql-js GraphQLSchema object.
    *
-   * This schema is going to be merged as-is. This can easily break the main
-   * Gatsby schema, so it's user's responsibility to make sure it doesn't happen
-   * (by e.g. namespacing the schema).
+   * This schema is going to be merged as-is. Merging it in this way will
+   * easily break the main Gatsby Schema. Since we do not want that, therefore
+   * it is the user's responsibility to make sure that it does not happen.
+   * One such way of avoiding it is by namespacing the schema.
    *
    * @availableIn [createSchemaCustomization, sourceNodes]
    *