finalizing and approving PR to close #100!

Author: vsoch

_posts/recipes/2017-05-09-hostlibs-gpus-and-mpi.md

@@ -6,7 +6,7 @@ permalink: tutorial-gpu-drivers-open-mpi-mtls
 
 **Note: _Much of the GPU portion of this tutorial is deprecated by the `--nv`
 option that automatically binds host system driver libraries into your 
-container at runtime.  See [the `exec` command](/docs-exec#a-gpu-example) for 
+container at runtime.  See the [`exec`](/docs-exec#a-gpu-example) command for 
 an example_**
 
 Singularity does a fantastic job  of isolating you from the host so you don't

pages/docs/contributing/contributing-docs.md

@@ -116,9 +116,15 @@ asciinema rec -w 1 demo-asciicast.js
 asciinema play demo-asciicast.js
 ```
 Make sure to resize your terminal to 25 rows x 115 columns or less before you 
-begin your recording.  Otherwise it will not display properly on the webpage.
+begin your recording.  Otherwise it will not display properly on the webpage. To get the size of your current terminal (in lines and columns) you can use `tput`:
 
-Once you've generated an asciicast, you should drop the file (e.g., `demo-asciicast.js`) into the `assets/asciicast` folder, and then include the following in the page or post:
+```
+echo -e "lines\ncols"|tput -S
+34
+80
+```
+
+Once you've generated an asciicast, you should drop the file (e.g., `demo-asciicast.js`) into the `assets/asciicast` folder. Since we will have many asciicasts here, please name it meaningfully. Then include the following in the page or post:
 
 ```bash
 {{ "{% include asciicast.html source='demo-asciicast.js' title='How to make demos' author='[email protected]'" }}%}

pages/docs/overview/faq.md

@@ -215,7 +215,7 @@ See the Singularity on HPC page for more details.
 
 Yes. Many users run GPU dependant code within Singularity containers.  The
 experimental `--nv` option allows you to leverage host GPUs without installing 
-system level drivers into your container. See [the `exec` command](/docs-exec#a-gpu-example) for
+system level drivers into your container. See the [`exec`](/docs-exec#a-gpu-example) command for
 an example.
 
 ## Container portability

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

@@ -146,9 +146,10 @@ You can add environment variables to be sourced when the container is used in th
 
 ```
 %environment
-    export VADER=badguy
-    export LUKE=goodguy
-    export SOLO=someguy
+    VADER=badguy
+    LUKE=goodguy
+    SOLO=someguy
+    export VADER LUKE SOLO
 ```
 
 See <a href="/docs-environment-metadata">Environment and Metadata</a> for more information about the `%labels` and `%environment` sections.

pages/docs/user-docs/docs-exec.md

@@ -93,7 +93,7 @@ Hello World: The Python version is 3.5.2
 ```
 
 ### A GPU example
-If you're host system has an NVIDIA GPU card and a driver installed you can
+If your host system has an NVIDIA GPU card and a driver installed you can
 leverage the card with the `--nv` option.  (This example requires a fairly 
 recent version of the NVIDIA driver on the host system to run the latest 
 version of TensorFlow.

pages/docs/user-docs/docs-export.md

@@ -6,4 +6,16 @@ toc: false
 folder: docs
 ---
 
-Export is a way to dump the contents of your container into a .tar.gz, or a stream to put into some other place. For example, you could stream this into an in memory tar in python.
+Export is a way to dump the contents of your container into a .tar.gz, or a stream to put into some other place. For example, you could stream this into an in memory tar in python. 
+
+Here we export an image into a `.tar` file:
+
+```
+singularity export container.img > container.tar
+```
+
+And here is the recommended way to compress your image:
+
+```
+singularity export container.img | gzip -9 > container.img.gz
+```

pages/docs/user-docs/docs-import.md

@@ -6,4 +6,10 @@ toc: false
 folder: docs
 ---
 
-Singularity import is essentially taking a dump of files and folders and adding them to your image. This works for local compressed things (e.g., tar.gz) but also for docker image layers that you don't have on your system. As of version 2.3, import of docker layers includes the environment and metadata without needing sudo.
+Singularity import is essentially taking a dump of files and folders and adding them to your image. This works for local compressed things (e.g., tar.gz) but also for docker image layers that you don't have on your system. As of version 2.3, import of docker layers includes the environment and metadata without needing sudo. It's generally very intuitive.
+
+As an example, here is a common use case: wanting to import a Docker image:
+
+```
+singularity import container.img docker://ubuntu:latest
+```

pages/docs/user-docs/docs-inspect.md

@@ -10,7 +10,7 @@ How can you sniff an image? We have provided the inspect command for you to easi
 
 {% include toc.html %}
 
-This inspect is essential for making containers understandable by other tools and applications.
+This command is essential for making containers understandable by other tools and applications.
 
 
 ## JSON Api Standard

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

@@ -18,7 +18,7 @@ $ singularity run centos7.img
 $ ./centos7.img
 ```
 
-In both cases, we are executing the container's "runscript," which is the executable `/singularity` at the root of the image, which is either an actual file (version 2.2 and earlier) or a link to one (2.3 and later). For example, looking at a 2.3 image, I can see the runscript via the path to the link:
+In both cases, we are executing the container's "runscript"  (the executable `/singularity` at the root of the image) that is either an actual file (version 2.2 and earlier) or a link to one (2.3 and later). For example, looking at a 2.3 image, I can see the runscript via the path to the link:
 
 ```
 $ singularity exec centos7.img cat /singularity
@@ -51,7 +51,7 @@ motorbot
 ```
 
 ### Defining the Runscript
-When you first create a contianer, the runscript is defined using the followinge order of operations:
+When you first create a container, the runscript is defined using the following order of operations:
 
  1. A user defined runscript in the `%runscript` section of a bootstrap takes preference over all
  2. If the user has not defined a runscript and is importing a Docker container, the Docker `ENTRYPOINT` is used.