Merge branch 'master' of github.com:singularityware/singularityware.github.io

Author: vsoch

pages/docs/admin-docs/advanced-config.md

@@ -25,7 +25,7 @@ While the PID namespace is a *neat* feature, it does not have much practical usa
 Even if the PID namespace is enabled by the system administrator here, it is not implemented by default when running containers. The user will have to specify they wish to implement un-sharing of the PID namespace as it must fork a child process.
 
 
-### ENABLE OVERLAY (boolean, default='yes')
+### ENABLE OVERLAY (boolean, default='no')
 The overlay file system creates a writable substrate to create bind points if necessary. This feature is very useful when implementing bind points within containers where the bind point may not already exist so it helps with portability of containers. Enabling this option has been known to cause some kernels to panic as this feature maybe present within a kernel, but has not proved to be stable as of the time of this writing (e.g. the Red Hat 7.2 kernel).
 
 ### CONFIG PASSWD,GROUP,RESOLV_CONF (boolean, default='yes')

pages/docs/admin-docs/image-environment.md

@@ -45,7 +45,9 @@ $
 ```
 
 But notice how even though the directory location is not resolvable, the directory contents are available.
-Standard IO and pipes
+
+
+## Standard IO and pipes
 
 Singularity automatically sends and receives all standard IO from the host to the applications within the container to facilitate expected behavior from the interaction between the host and the container. For example:
 

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

@@ -28,7 +28,7 @@ As mentioned above, Singularity containers utilize a single file which is the co
 
 ### User Freedom
 
-System integrators, administrators, and engineers spend a lot of effort maintaining the operating systems on the resources they are reasonable for, and as a result tend to take a cautious approach on their systems. As a result, you may see hosts installed with a production, mission critical operating system that is "old" and may not have a lot of packages available for it. Or you may see software or libraries that are too old or incompatible with the software you need to run, or maybe just haven't installed the software stack you need due to complexities with building, specific software knowledge, incompatibilities or conflicts with other installed programs.
+System integrators, administrators, and engineers spend a lot of effort maintaining the operating systems on the resources they are responsible for, and as a result tend to take a cautious approach on their systems. As a result, you may see hosts installed with a production, mission critical operating system that is "old" and may not have a lot of packages available for it. Or you may see software or libraries that are too old or incompatible with the software you need to run, or maybe just haven't installed the software stack you need due to complexities with building, specific software knowledge, incompatibilities or conflicts with other installed programs.
 
 Singularity can give the user the freedom they need to install the applications, versions, and dependencies for their workflows without impacting the system in any way. Users can define their own working environment and literally copy that environment image (single file) to a shared resource, and run their workflow inside that image.