From 7898b3a3766b8c374515a093f9a51b9672fb4a49 Mon Sep 17 00:00:00 2001
From: duy-ce <51443420+duy-ce@users.noreply.github.com>
Date: Tue, 19 Jan 2021 15:21:41 +0700
Subject: [PATCH] Update production-build.md

---
 docusaurus/docs/production-build.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/docusaurus/docs/production-build.md b/docusaurus/docs/production-build.md
index 8acb30fc9eb..85de958d9ec 100644
--- a/docusaurus/docs/production-build.md
+++ b/docusaurus/docs/production-build.md
@@ -32,5 +32,5 @@ Using `Cache-Control: max-age=31536000` for your `build/static` assets, and `Cac
 ## Profiling
 
 ReactDOM automatically supports profiling in development mode for v16.5+, but since profiling adds some small
-additional overhead it is opt-in for production mode. You can opt-in by using the `--profile` flag. Use `npm run build -- --profile` or `yarn build --profile` to enable profiling in the production build. See the [React docs](https://reactjs.org/docs/optimizing-performance.html#profiling-components-with-the-devtools-profiler) for details about profiling
+additional overhead it is opt-in for production mode. You can opt-in by using the `--profile` flag. Use `npm run build --profile` or `yarn build --profile` to enable profiling in the production build. See the [React docs](https://reactjs.org/docs/optimizing-performance.html#profiling-components-with-the-devtools-profiler) for details about profiling
 using the React DevTools.