From 6b52c60d4ee9c77fee832d119d9ef752f51e16e6 Mon Sep 17 00:00:00 2001 From: Michaela Chester <57752987+michaelajsc@users.noreply.github.com> Date: Fri, 16 Aug 2024 14:12:06 +0100 Subject: [PATCH] Update moving-to-federation-2.mdx (#3121) MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Changed "The schema changes you make are backward incompatible with Federation 1..." TO "The schema changes you make are not backward compatible with Federation 1..." --- docs/source/federation-2/moving-to-federation-2.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/source/federation-2/moving-to-federation-2.mdx b/docs/source/federation-2/moving-to-federation-2.mdx index c272919b0..e02e1efd5 100644 --- a/docs/source/federation-2/moving-to-federation-2.mdx +++ b/docs/source/federation-2/moving-to-federation-2.mdx @@ -172,7 +172,7 @@ Federation 2 provides powerful new features that require making some changes to - Safely migrating fields from one subgraph to another with [`@override`](../federated-types/federated-directives#override) - Hiding internal routing fields from graph consumers with [`@inaccessible`](../federated-types/federated-directives#inaccessible) -The schema changes you make are backward incompatible with Federation 1, which means you won't be able to use Federation 1 composition anymore unless you revert those changes. +The schema changes you make are not backward compatible with Federation 1, which means you won't be able to use Federation 1 composition anymore unless you revert those changes. ### Update your subgraph library