From d288d43f19d9360e9676c638badc2ecd52649713 Mon Sep 17 00:00:00 2001
From: Kitayoshi <midare@utakana.de>
Date: Thu, 17 Feb 2022 06:06:18 +0800
Subject: [PATCH] Update MDX Guide config example (#34405)

The previous example may cause an unintentional change of the current `pageExtensions` setting, especially for the people who are not familiar with <https://nextjs.org/docs/api-reference/next.config.js/custom-page-extensions>

## Documentation / Examples

- [x] Make sure the linting passes by running `yarn lint`
---
 docs/advanced-features/using-mdx.md | 3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)

diff --git a/docs/advanced-features/using-mdx.md b/docs/advanced-features/using-mdx.md
index bdfb3b3e8f3d0..8087473ca22d1 100644
--- a/docs/advanced-features/using-mdx.md
+++ b/docs/advanced-features/using-mdx.md
@@ -51,7 +51,8 @@ The following steps outline how to setup `@next/mdx` in your Next.js project:
      },
    })
    module.exports = withMDX({
-     pageExtensions: ['js', 'jsx', 'md', 'mdx'],
+     // Append the default value with md extensions
+     pageExtensions: ['ts', 'tsx', 'js', 'jsx', 'md', 'mdx'],
    })
    ```