From f25600fe3388ddc77ea4f69ae13f001d79d48bf7 Mon Sep 17 00:00:00 2001
From: Christian Sany <20772036+christiansany@users.noreply.github.com>
Date: Tue, 22 Jul 2025 11:53:11 +0200
Subject: [PATCH] Update throw-on-field-error-directive.md

Currently on https://relay.dev/docs/guides/throw-on-field-error-directive/, this slash at the end of the file name will result in a double slash when visiting the site.

This change will remove the double slash and make the link work.
---
 .../version-v20.0.0/guides/throw-on-field-error-directive.md    | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/website/versioned_docs/version-v20.0.0/guides/throw-on-field-error-directive.md b/website/versioned_docs/version-v20.0.0/guides/throw-on-field-error-directive.md
index 8e5ab3b8df86c..77eb790c18dd9 100644
--- a/website/versioned_docs/version-v20.0.0/guides/throw-on-field-error-directive.md
+++ b/website/versioned_docs/version-v20.0.0/guides/throw-on-field-error-directive.md
@@ -15,7 +15,7 @@ The `@throwOnFieldError` directive can be added to fragments and queries. When
 this directive is used, the Relay runtime will throw an exception if a field
 with a field error is encountered while reading the fragment or query, or if
 Relay is missing data due to a
-[graph relationship change](../debugging/why-null.md/#graph-relationship-change).
+[graph relationship change](../debugging/why-null.md#graph-relationship-change).
 
 In addition to causing the Relay runtime to throw an exception if a field error
 is encountered, the `@throwOnFieldError` directive also enables generation of