addressing issues found by v

Author: GodloveD

pages/docs/user-docs/action-build.md

@@ -6,7 +6,7 @@ folder: docs
 toc: false
 ---
 
-`build` is the "Swiss army knife" of container creation.  You can use it to download and assemble pre-built containers from external resources like [Singularity Hub](https://singularity-hub.org/) and [Docker Hub](https://hub.docker.com/).  You can use it to convert containers between the various formats supported by Singularity.  And you can use it in conjunction with a [Singularity Recipe](/docs-recipes) file to create a container from scratch and customized it to fit your needs. 
+`build` is the "Swiss army knife" of container creation.  You can use it to download and assemble existing containers from external resources like [Singularity Hub](https://singularity-hub.org/) and [Docker Hub](https://hub.docker.com/).  You can use it to convert containers between the various formats supported by Singularity.  And you can use it in conjunction with a [Singularity Recipe](/docs-recipes) file to create a container from scratch and customized it to fit your needs. 
 
 {% include toc.html %}
 
@@ -32,7 +32,7 @@ Because `build` can accept an existing container as a target and create a contai
 
 Some things need root...
 
-## Downloading a pre-built container from Singularity Hub
+## Downloading a existing container from Singularity Hub
 You can use the `build` command to download a container from Singularity Hub. 
 
 ```
@@ -43,7 +43,7 @@ The first argument (`lolcow.simg`) specifies a path and name for your container.
 
 But default the container will be converted to a compressed, read-only squashfs file.  If you want your container in a different format use the `--writable` or `--sandbox` options.
 
-## Downloading a pre-built container from Docker Hub
+## Downloading a existing container from Docker Hub
 You can use `build` to download layers from Docker Hub and assemble them into Singularity containers. 
 
 ```

pages/docs/user-docs/docs-environment-metadata.md

@@ -12,7 +12,7 @@ Singularity containers support environment variables and labels that you can add
 
 ## Environment
 
-If you build a container from Singularity Hub or Docker Hub, the environment will be imported into the container at build time. You can also define custom environment variables in your Recipe file like so:
+If you build a container from Singularity Hub or Docker Hub, the environment will be included with the container at build time. You can also define custom environment variables in your Recipe file like so:
 
 ```
 Bootstrap: shub
@@ -23,7 +23,7 @@ From: singularityhub/ubuntu
     export VARIABLE_NAME
 ```
 
-You may need to add environment variables to your container during the `$post` section.  For instance, maybe you will not know the appropriate value of a variable until you have installed some software.  
+You may need to add environment variables to your container during the `%post` section.  For instance, maybe you will not know the appropriate value of a variable until you have installed some software.  
 
 To add variables to the environment during `%post` you can use the `$SINGULARITY_ENVIRONMENT` variable with the following syntax:
 

pages/docs/user-docs/docs-recipes.md

@@ -22,7 +22,7 @@ Please see the [examples](https://github.com/singularityware/singularity/tree/ma
 ### Header
 The header is at the top of the file, and tells Singularity the base Operating System that it should use to build the container.  It is composed of several keywords. Specifically:
 
- - `Bootstrap:` references the kind of base you want to use (e.g., docker, debootstrap, shub). For example, a shub bootstrap will pull containers for shub as bases. A Docker bootstrap will pull docker layers to start your image. For a full list see <a href="/build">build</a>
+ - `Bootstrap:` references the kind of base you want to use (e.g., docker, debootstrap, shub). For example, a shub bootstrap will pull containers for shub as bases. A Docker bootstrap will pull docker layers to start your image. For a full list see [build](docs-build)
  - `From:` is the named container (shub) or reference to layers (Docker) that you want to use (e.g., vsoch/hello-world)
 
 Depending on the value assigned to `Bootstrap:`, other keywords may also be valid in the header.
@@ -45,7 +45,7 @@ Include: yum
 
 Each build base requires particular details during build time.  You can read about them and see examples at the following links:
 
- - [shub](/build-docker) (images hosted on Singularity Hub)
+ - [shub](/build-shub) (images hosted on Singularity Hub)
  - [docker](/build-docker) (images hosted on Docker Hub)
  - [localimage](/build-localimage) (images saved on your machine)
  - [self](/build-self) (a snapshot of your build system)