From fc8458ee3434a9d6c30b4177b5c17d02dbcc83fc Mon Sep 17 00:00:00 2001 From: XhmikosR Date: Sat, 10 Aug 2019 13:14:12 +0300 Subject: [PATCH] Fix typo. --- README.md | 2 +- docs/watch-examples.md | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/README.md b/README.md index 5482741..3085179 100644 --- a/README.md +++ b/README.md @@ -478,7 +478,7 @@ Spawning does cause a performance hit (usually 500ms for most environments). It #### How can I have the browser reload for files listed in a task? Instead of restarting your server each time a static file is changed, start a static web server using (grunt-contrib-connect)[https://github.com/gruntjs/grunt-contrib-connect]. -You'll have the `connect` web server on seperate port ex: port 9000 from your main server. When the 'livereload' option is enabled for 'watch' tasks, it will handle triggerring the live reload server for each tasks and when files are modified, which then server back to main server ex: 3000. The main server must include a script tag or a browser extension to the livereload server in order for the browser automatically. +You'll have the `connect` web server on separate port ex: port 9000 from your main server. When the 'livereload' option is enabled for 'watch' tasks, it will handle triggering the live reload server for each tasks and when files are modified, which then server back to main server ex: 3000. The main server must include a script tag or a browser extension to the livereload server in order for the browser automatically. ## Release History diff --git a/docs/watch-examples.md b/docs/watch-examples.md index 5d754c7..cedd165 100644 --- a/docs/watch-examples.md +++ b/docs/watch-examples.md @@ -224,4 +224,4 @@ Spawning does cause a performance hit (usually 500ms for most environments). It ## How can I have the browser reload for files listed in a task? Instead of restarting your server each time a static file is changed, start a static web server using (grunt-contrib-connect)[https://github.com/gruntjs/grunt-contrib-connect]. -You'll have the `connect` web server on seperate port ex: port 9000 from your main server. When the 'livereload' option is enabled for 'watch' tasks, it will handle triggerring the live reload server for each tasks and when files are modified, which then server back to main server ex: 3000. The main server must include a script tag or a browser extension to the livereload server in order for the browser automatically. +You'll have the `connect` web server on separate port ex: port 9000 from your main server. When the 'livereload' option is enabled for 'watch' tasks, it will handle triggering the live reload server for each tasks and when files are modified, which then server back to main server ex: 3000. The main server must include a script tag or a browser extension to the livereload server in order for the browser automatically.