From e5d01a0712f49bf7ce48e9c678e7fe1c1b433bf0 Mon Sep 17 00:00:00 2001 From: Titus Date: Tue, 16 Jul 2024 11:22:32 +0200 Subject: [PATCH] Apply suggestions from code review Signed-off-by: Titus --- docs/docs/using-mdx.mdx | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/docs/docs/using-mdx.mdx b/docs/docs/using-mdx.mdx index 66249ad65..40f89dfcb 100644 --- a/docs/docs/using-mdx.mdx +++ b/docs/docs/using-mdx.mdx @@ -263,7 +263,7 @@ MDX using imported components! Because MDX files *are* components, they can also import each other: ```mdx path="example.mdx" -import License from './license.mdx' // Assumes an integration is used to compile MDX -> JS. +import License from './license.md' // Assumes an integration is used to compile markdown -> JS. import Contributing from './docs/contributing.mdx' # Hello world @@ -468,7 +468,7 @@ cumbersome. Like so: ```mdx path="post.mdx" -import License from './license.mdx' // Assumes an integration is used to compile MDX -> JS. +import License from './license.md' // Assumes an integration is used to compile markdown -> JS. import Contributing from './docs/contributing.mdx' # Hello world @@ -517,7 +517,7 @@ Set it up like so: Now you can remove the explicit and verbose component passing: ```diff - import License from './license.mdx' // Assumes an integration is used to compile MDX -> JS. + import License from './license.md' // Assumes an integration is used to compile markdown -> JS. import Contributing from './docs/contributing.mdx' # Hello world