docs: fix Rhai relative links (#4298)

Fixes broken links on https://www.apollographql.com/docs/router/customizations/native/ Co-authored-by: Geoffroy Couprie <[email protected]>
apollographql · Dec 5, 2023 · c75319f · c75319f
1 parent 433bf2b
commit c75319f
Show file tree

Hide file tree

Showing 3 changed files with 4 additions and 4 deletions.
diff --git a/docs/shared/elastic-notice.mdx b/docs/shared/elastic-notice.mdx
@@ -1,5 +1,5 @@
 <Note>
 
-The Apollo Router source code and all its distributions are made available under the [Elastic License v2.0 (ELv2) license](/resources/elastic-license-v2-faq/).
+The Apollo Router source code and all its distributions are made available under the [Elastic License v2.0 (ELv2) license](https://www.apollographql.com/docs/resources/elastic-license-v2-faq/#can-i-extend-or-modify-the-gateway-or-router-by-creating-plugins).
 
 </Note>
diff --git a/docs/shared/native-plugin-notice.mdx b/docs/shared/native-plugin-notice.mdx
@@ -3,6 +3,6 @@
 - Native plugins require familiarity with programming in Rust.
 - Native plugins require compiling a custom router binary from source, which can introduce unexpected behavior in your router that's difficult to diagnose and support.
 
-Instead, for most router customizations, Apollo recommends creating either a [Rhai script](/customizations/rhai/) or an [external coprocessor](/customizations/coprocessor/). Both of these customizations are supported by Apollo and provide strong separation of concerns and fault isolation.
+Instead, for most router customizations, Apollo recommends creating either a [Rhai script](https://www.apollographql.com/docs/router/customizations/rhai/) or an [external coprocessor](https://www.apollographql.com/docs/router/customizations/coprocessor). Both of these customizations are supported by Apollo and provide strong separation of concerns and fault isolation.
 
 If you must create a native plugin, please [open a GitHub issue](https://github.com/apollographql/router/issues), and Apollo can investigate adding the custom capability to the stock router binary.
diff --git a/docs/source/customizations/native.mdx b/docs/source/customizations/native.mdx
@@ -295,8 +295,8 @@ There is no sequencing for plugin registration, and registrations might even exe
 
 Within a given service (router, subgraph, etc.), a _request_ is handled in the following order:
 
-* [Rhai script](../rhai)
-* [External coprocessor](../coprocessor)
+* [Rhai script](./rhai)
+* [External coprocessor](./coprocessor)
 * Rust plugins, in the same order they're declared in your [YAML configuration file](../configuration/overview/#yaml-config-file).
 
 The corresponding _response_ is handled in the opposite order.