Updates docs/yarn-scripts/overview.md

Auto commit by GitBook Editor
htmlburger · Jun 12, 2018 · e2444f6 · e2444f6
1 parent 7a1c316
commit e2444f6
Show file tree

Hide file tree

Showing 2 changed files with 10 additions and 9 deletions.
diff --git a/docs/asset-pipeline/overview.md b/docs/asset-pipeline/overview.md
@@ -15,14 +15,7 @@ The WP Emerge Theme comes with a powerful asset build process which covers a mul
 1. Run your desired build process:
     - To run the build process in production mode run `yarn build`
     - To run the build process in development mode run `yarn dev`. This will also watch files for changes and run Browsersync.
-
-## Browsersync
-
-By default, Browsersync will setup a simple web server and serve your files through a custom port in order to establish a communication channel between the build process and your browser like this:
-`http://localhost:3000/`
-
-This is not ideal when working on WordPress projects that are setup in a subdirectory, for example. To let Browsersync know your site's url simply pass it as a parameter when running the dev task:
-`yarn dev --dev-url=http://localhost/my/nested/subdirectory/wordpress/`
+    - For more information, check out the [Yarn Scripts](../yarn-scripts/overview.md) article.
 
 ## Importing assets
 

diff --git a/docs/yarn-scripts/overview.md b/docs/yarn-scripts/overview.md
@@ -2,7 +2,7 @@
 
 ## `yarn dev`
 
-Run the build process in development mode and enable Browsersync.
+Run the build process in development mode and enable [Browsersync](#browsersync).
 
 ## `yarn build`
 
@@ -15,3 +15,11 @@ Run the scripts and styles linters (`eslint` and `stylelint` respectively), repo
 ## `yarn lint-fix`
 
 Run the scripts and styles linters (`eslint` and `stylelint` respectively), fixing any fixable lint rule violations.
+
+## Browsersync
+
+By default, Browsersync will setup a simple web server and serve your files through a custom port in order to establish a communication channel between the build process and your browser like this:
+`http://localhost:3000/`
+
+This is not ideal when working on WordPress projects that are setup in a subdirectory, for example. To let Browsersync know your site's url simply pass it as a parameter when running the dev task:
+`yarn dev --dev-url=http://localhost/my/nested/subdirectory/wordpress/`