updating links

Author: GodloveD

_posts/releases/2017-10-02-release-2.4.md

@@ -17,7 +17,7 @@ Building an image is now more intuitive with the introduction of our `build` com
 sudo singularity build container.simg Singularity
 ```
 
-If you are tired of needing to estimate your image size, that issue goes away with build. The default format for a Singularity image base is now a smaller, compressed file format called **SquashFS**.  This format is also a much better fit for reproducible containers, as it is immutable. For more details, see our [build](/docs-build) documentation.
+If you are tired of needing to estimate your image size, that issue goes away with build. The default format for a Singularity image base is now a smaller, compressed file format called **SquashFS**.  This format is also a much better fit for reproducible containers, as it is immutable. For more details, see our [build](/docs-build-container) documentation.
 
 **Build Bases**
 We originally supported just using an existing distribution package or docker as a base for building images. With 2.4, we have extended that set to include another Singularity image (`localimage`), a Singularity Hub or Registry image (`shub`) or the host operating system (`self`).

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

@@ -59,7 +59,7 @@ When you first create a container, the runscript is defined using the following
  4. If the user has not defined a runscript and the Docker container doesn't have an `ENTRYPOINT`, we look for `CMD`, even if the user hasn't asked for it.
  5. If the user has not deifned a runscript, and there is no `ENTRYPOINT` or `CMD` (or we aren't importing Docker at all) then we default to `/bin/bash`
 
-Here is how you would define the runscript section when you [build](/docs-build) an image:
+Here is how you would define the runscript section when you [build](/docs-build-container) an image:
 
 ```bash
 Bootstrap: docker

pages/docs/user-docs/docs-flow.md

@@ -26,7 +26,7 @@ The diagram below is a visual depiction of how you can use Singularity to build
    <img style="max-width:900px" src="/assets/img/diagram/singularity-2.4-flow.png">
 </a>
 
-Singularity production images are immutable. This is a feature added as of Singularity 2.4, and it ensures a higher level of reproducibility and verification of images. To read more about the details, check out the  [build](docs-build) docs. However, immutability is not so great when you are testing, debugging, or otherwise want to quickly change your image. We will proceed by describing a typical workflow of developing first, building a final image, and using in production. 
+Singularity production images are immutable. This is a feature added as of Singularity 2.4, and it ensures a higher level of reproducibility and verification of images. To read more about the details, check out the  [build](docs-build-container) docs. However, immutability is not so great when you are testing, debugging, or otherwise want to quickly change your image. We will proceed by describing a typical workflow of developing first, building a final image, and using in production. 
 
 ### 1. Development Commands
 If you want a writable image or folder for developing, you have two options:

pages/docs/user-docs/docs-quickstart.md

@@ -102,7 +102,7 @@ $ singularity help --app foo container.img  # See the help for foo, if provided
 ```
 
 ## Download pre-built images
-You can use the [`pull`](docs-pull) and [`build`](docs-build) commands to download pre-built images from an external resource like [Singularity Hub](https://singularity-hub.org/) or [Docker Hub](https://hub.docker.com/).  When called on a native Singularity images like those provided on Singularity Hub, `pull` simply downloads the image file to your system.   
+You can use the [`pull`](docs-pull) and [`build`](docs-build-container) commands to download pre-built images from an external resource like [Singularity Hub](https://singularity-hub.org/) or [Docker Hub](https://hub.docker.com/).  When called on a native Singularity images like those provided on Singularity Hub, `pull` simply downloads the image file to your system.   
 
 
 ```

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 [build](docs-build)
+ - `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-container)
  - `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.
@@ -468,4 +468,4 @@ When crafting your recipe, it is best to consider the following:
 6. Ensure that the container's `/etc/passwd`, `/etc/group`, `/etc/shadow`, and no other sensitive files have anything but the bare essentials within them.
 7. It is encouraged to build containers from a recipe instead of a sandbox that has been manually changed. This ensures greatest possibility of reproducibility and mitigates the *black box effect*.
 
-Are you a recipe pro and now ready to build? Take a look at the [build](docs-build) documentation.
+Are you a recipe pro and now ready to build? Take a look at the [build](docs-build-container) documentation.

pages/docs/user-docs/docs-usage.md

@@ -18,7 +18,7 @@ If you type `singularity` without any arguments, you will see a high level help
 
 **Container Actions**
 
-- [build](/docs-build): Build a container on your user endpoint or build environment
+- [build](/docs-build-container): Build a container on your user endpoint or build environment
 - [exec](/docs-exec): Execute a command to your container
 - [inspect](/docs-inspect): See labels, run and test scripts, and environment variables
 - [pull](/docs-pull): pull an image from Docker or Singularity Hub

pages/docs/user-docs/image-create.md

@@ -5,7 +5,7 @@ permalink: /docs-create
 folder: docs
 ---
 
-A Singularity image, which can be referred to as a "container," is a single file that contains a virtual file system. As of Singularity 2.4, we strongly recommend that you build (create and install) an image using <a href="/docs-build">build</a>. If you have reason to create an empty image, or use creat for any other reason, the original `create` command is replaced with a more specific `image.create`. After creating an image you can install an operating system, applications, and save meta-data with it.
+A Singularity image, which can be referred to as a "container," is a single file that contains a virtual file system. As of Singularity 2.4, we strongly recommend that you build (create and install) an image using <a href="/docs-build-container">build</a>. If you have reason to create an empty image, or use creat for any other reason, the original `create` command is replaced with a more specific `image.create`. After creating an image you can install an operating system, applications, and save meta-data with it.
 
 Whereas Docker assembles images from layers that are stored on your computer (viewed with the `docker history` command), a Singularity image is just one file that can sit on your Desktop, in a folder on your cluster, or anywhere. Having Singularity containers housed within a single image file greatly simplifies management tasks such as sharing, copying, and branching your containers. It also means that standard Linux file system concepts like permissions, ownership, and ACLs apply to the container (e.g. I can give read only access to a colleague, or block access completely with a simple `chmod` command).
 

pages/docs/user-docs/user-guide.md

@@ -165,7 +165,7 @@ Once you have the container with the necessary applications, libraries and data
 ### Singularity Commands
 How do the commands work? Here is where to look for more information:
 
-- [build](/docs-build): Build a container on your user endpoint or build environment
+- [build](/docs-build-container): Build a container on your user endpoint or build environment
 - [exec](/docs-exec): Execute a command to your container
 - [inspect](/docs-inspect): See labels, run and test scripts, and environment variables
 - [pull](/docs-pull): pull an image from Docker or Singularity Hub