diff --git a/docs/content/extras/livereload.md b/docs/content/extras/livereload.md
index a32614f58..ebbd3da2c 100644
--- a/docs/content/extras/livereload.md
+++ b/docs/content/extras/livereload.md
@@ -5,24 +5,24 @@ menu:
parent: extras
next: /extras/menus
prev: /extras/crossreferences
-title: Live Reload
+title: LiveReload
weight: 50
---
-Hugo may not be the first static site generator to utilize live reload
+Hugo may not be the first static site generator to utilize LiveReload
technology, but it’s the first to do it right.
-The combination of Hugo’s insane build speed and live reload make
+The combination of Hugo’s insane build speed and LiveReload make
crafting your content pure joy. Virtually instantly after you hit save
your rebuilt content will appear in your browser.
-## Using livereload
+## Using LiveReload
-Hugo comes with livereload built in. There are no additional packages to
-install. A common way to use hugo while developing a site is to have
-hugo run a server and watch for changes.
+Hugo comes with LiveReload built in. There are no additional packages to
+install. A common way to use Hugo while developing a site is to have
+Hugo run a server and watch for changes:
- hugo server --watch
+ $ hugo server --watch
This will run a full functioning web server while simultaneously
watching your file system for additions, deletions or changes within
@@ -40,22 +40,18 @@ fast they are barely noticeable, you merely need to glance at your open
browser and you will see the change already there.
This means that keeping the site open on a second monitor (or another
-half of your current monitor), allows you to see exactly what your
+half of your current monitor) allows you to see exactly what your
content looks like without even leaving your text editor.
-## Disabling livereload
+## Disabling LiveReload
-Live reload accomplishes this by injecting javascript into the pages it
+LiveReload works by injecting JavaScript into the pages it
creates that creates a web socket client to the hugo web socket server.
Awesome for development, but not something you would want to do in
production. Since many people use `hugo server --watch` in production to
instantly display any updated content, we’ve made it easy to disable the
-live reload functionality.
-
- hugo server --watch --disableLiveReload
-
-
-
+LiveReload functionality.
+ $ hugo server --watch --disableLiveReload
diff --git a/docs/content/extras/menus.md b/docs/content/extras/menus.md
index 5362903a7..957432567 100644
--- a/docs/content/extras/menus.md
+++ b/docs/content/extras/menus.md
@@ -41,7 +41,7 @@ And the following functions:
* **HasChildren** bool
-Additionally there are some relevant functions available on the page:
+Additionally, there are some relevant functions available on the page:
* **IsMenuCurrent** (menu string, menuEntry *MenuEntry ) bool
* **HasMenuCurrent** (menu string, menuEntry *MenuEntry) bool
@@ -89,7 +89,7 @@ available.
You can also add entries to menus that aren’t attached to a piece of
content. This takes place in the sitewide [config file](/overview/configuration).
-Here’s an example (in TOML):
+Here’s an example `config.toml`:
[[menu.main]]
name = "about hugo"
@@ -101,7 +101,7 @@ Here’s an example (in TOML):
pre = ""
weight = -100
-Here’s an example (in YAML):
+And the equivalent example `config.yaml`:
---
menu:
@@ -142,7 +142,7 @@ The following is an example: