From 8331763674671ed238ab75c445fdab8b9ce5b9b1 Mon Sep 17 00:00:00 2001 From: Yangshun Tay Date: Sat, 6 Jun 2020 11:14:40 +0800 Subject: [PATCH] Update migrating-from-v1-to-v2.md --- website/docs/migrating-from-v1-to-v2.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/website/docs/migrating-from-v1-to-v2.md b/website/docs/migrating-from-v1-to-v2.md index 29b9c3c4b6bf..0c0abdb7088c 100644 --- a/website/docs/migrating-from-v1-to-v2.md +++ b/website/docs/migrating-from-v1-to-v2.md @@ -191,7 +191,7 @@ module.exports = { We recommend moving the `docs` folder into the `website` folder and that is also the default directory structure in v2. [Now](https://zeit.co/now) supports [Docusaurus project deployments out-of-the-box](https://github.com/zeit/now-examples/tree/master/docusaurus) if the `docs` directory is within the `website`. It is also generally better for the docs to be within the website so that the docs and the rest of the website code are co-located within one `website` directory. -If you are migrating your Docusaurus v1 website, and there are pending documentation pull requests, you can temporarily keep the `/docs` folder to its original place, to avoid producing conflits. +If you are migrating your Docusaurus v1 website, and there are pending documentation pull requests, you can temporarily keep the `/docs` folder to its original place, to avoid producing conflicts. Refer to migration guide below for each field in `siteConfig.js`.