From 2cb41ec6f00b8fa5abbd86822ea57ffb0c1e5f04 Mon Sep 17 00:00:00 2001
From: boiboi <87666954+boiiiboi@users.noreply.github.com>
Date: Thu, 21 Nov 2024 17:29:57 +0900
Subject: [PATCH] Fix documentation typo: Correct v4CompatibilityMode value for
 disabling retro-compatibility (#2294)

This PR corrects a typo in the documentation. The step to disable the retro-compatibility flag currently instructs setting v4CompatibilityMode to true. However, the correct value should be false to disable retro-compatibility and start using the new response format.
---
 docusaurus/docs/dev-docs/migration/v4-to-v5/step-by-step.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/docusaurus/docs/dev-docs/migration/v4-to-v5/step-by-step.md b/docusaurus/docs/dev-docs/migration/v4-to-v5/step-by-step.md
index a648efd27b..385264abfe 100644
--- a/docusaurus/docs/dev-docs/migration/v4-to-v5/step-by-step.md
+++ b/docusaurus/docs/dev-docs/migration/v4-to-v5/step-by-step.md
@@ -119,4 +119,4 @@ Follow the steps below and leverage retro-compatibility flags and guided migrati
 1. Enable the retro-compatibility flag by setting `v4CompatibilityMode` to `true` in the `graphl.config` object of [the `/config/plugins.js|ts` file](/dev-docs/configurations/plugins#graphql).
 2. Update your queries and mutations only, guided by the dedicated [breaking change entry for GraphQL](/dev-docs/migration/v4-to-v5/breaking-changes/graphql-api-updated).
 3. Validate that your client is running correctly.
-4. Disable the retro-compatibily flag by setting `v4CompatibilityMode` to `true` and start using the new response format.
+4. Disable the retro-compatibily flag by setting `v4CompatibilityMode` to `false` and start using the new response format.