Docs: remove unnecessary --watch flag

docs/content/extras/builders.md

@@ -52,7 +52,4 @@ will pre-populate values based on the content type.
     $ hugo new relative/path/to/content
 
 This assumes it is being run from your working directory and the content
-path starts from your content directory.
+path starts from your content directory. Now, Hugo watches your content directory by default and rebuilds your entire website if any change occurs.
-
-I typically keep two different terminals open, one to run `hugo server
---watch`, and another to use the builders to create new content.

docs/content/tutorials/create-a-multilingual-site.md

@@ -138,11 +138,11 @@ Once you have things set up, you can run `hugo server` or `hugo` before deployin
 ~~~shell
 function hugoserver-com {
   cd /Users/me/dev/mainsite
-  hugo server --buildDrafts --watch --verbose --source="/Users/me/dev/mainsite" --config="/Users/me/dev/mainsite/config_en.toml" --port=1377
+  hugo server --buildDrafts --verbose --source="/Users/me/dev/mainsite" --config="/Users/me/dev/mainsite/config_en.toml" --port=1377
 }
 function hugoserver-jp {
   cd /Users/me/dev/mainsite
-  hugo server --buildDrafts --watch --verbose --source="/Users/me/dev/mainsite" --config="/Users/me/dev/mainsite/config_ja.toml" --port=1399
+  hugo server --buildDrafts --verbose --source="/Users/me/dev/mainsite" --config="/Users/me/dev/mainsite/config_ja.toml" --port=1399
 }
 ~~~
 

docs/content/tutorials/github-pages-blog.md

@@ -166,7 +166,7 @@ After executing these commands and waiting for the GitHub servers to update, the
 Now, as you add new posts to your blog, you will follow steps that look something like the following:
 
 * Create the Markdown source for the new post within the `content/posts` directory
-* Preview your work by running Hugo in server mode with `hugo server --watch`
+* Preview your work by running Hugo in server mode with `hugo server`
 * Run Hugo not in server mode so that the generated urls will be correct for the website
 * Add and commit the new post in `master` branch
 * Push the `master` branch
@@ -252,7 +252,7 @@ Step by step:
 1. Create on GitHub `<your-project>-hugo` repository (it will host Hugo's content)
 2. Create on GitHub `<username>.github.io` repository (it will host the `public` folder: the static website)
 2. `git clone <<your-project>-hugo-url> && cd <your-project>-hugo`
-3. Make your website work locally (`hugo server --watch -t <yourtheme>`)
+3. Make your website work locally (`hugo server -t <yourtheme>`)
 4. Once you are happy with the results, <kbd>Ctrl</kbd>+<kbd>C</kbd> (kill server) and `rm -rf public` (don't worry, it can always be regenerated with `hugo -t <yourtheme>`)
 5. `git submodule add git@github.com:<username>/<username>.github.io.git public`
 6. Almost done: add a `deploy.sh` script to help you (and make it executable: `chmod +x deploy.sh`):

docs/content/tutorials/migrate-from-jekyll.md

@@ -152,7 +152,7 @@ As a bonus, the shortcode named parameters are, arguably, more readable.
 
 ## Finishing touches
 ### Fix content
-Depending on the amount of customization that was done with each post with Jekyll, this step will require more or less effort. There are no hard and fast rules here except that `hugo server --watch` is your friend. Test your changes and fix errors as needed.
+Depending on the amount of customization that was done with each post with Jekyll, this step will require more or less effort. There are no hard and fast rules here except that `hugo server` is your friend. Test your changes and fix errors as needed.
 
 ### Clean up
 You'll want to remove the Jekyll configuration at this point. If you have anything else that isn't used, delete it.