svn commit: r1709951 - /incubator/singa/site/trunk/content/markdown/docs/mesos.md

[wangwei]

Author: wangwei
Date: Thu Oct 22 04:31:15 2015
New Revision: 1709951

URL: http://svn.apache.org/viewvc?rev=1709951&view=rev
Log:
update the title of mesos doc page

Modified:
    incubator/singa/site/trunk/content/markdown/docs/mesos.md

Modified: incubator/singa/site/trunk/content/markdown/docs/mesos.md
URL: 
http://svn.apache.org/viewvc/incubator/singa/site/trunk/content/markdown/docs/mesos.md?rev=1709951&r1=1709950&r2=1709951&view=diff
==============================================================================
--- incubator/singa/site/trunk/content/markdown/docs/mesos.md (original)
+++ incubator/singa/site/trunk/content/markdown/docs/mesos.md Thu Oct 22 
04:31:15 2015
@@ -1,7 +1,7 @@
-# Distributed Training on Mesos
+#Distributed Training on Mesos
 
-This guide explains how to start SINGA distributed training on a Mesos 
cluster. It assumes that both Mesos and HDFS are already running, and every 
node has SINGA installed. 
-We assume the architecture depicted below, in which a cluster nodes are Docker 
container. Refer to [Docker guide](docker.html) for details of how to start 
individual nodes and set up network connection between them (make sure 
[weave](http://weave.works/guides/weave-docker-ubuntu-simple.html) is running 
at each node, and the cluster's headnode is running in container `node0`)  
+This guide explains how to start SINGA distributed training on a Mesos 
cluster. It assumes that both Mesos and HDFS are already running, and every 
node has SINGA installed.
+We assume the architecture depicted below, in which a cluster nodes are Docker 
container. Refer to [Docker guide](docker.html) for details of how to start 
individual nodes and set up network connection between them (make sure 
[weave](http://weave.works/guides/weave-docker-ubuntu-simple.html) is running 
at each node, and the cluster's headnode is running in container `node0`)
 
 ![Nothing](http://www.comp.nus.edu.sg/~dinhtta/files/singa_mesos.png)
 
@@ -30,15 +30,15 @@ To check if the setup has been successfu
 
 ````
 hadoop dfsadmin -report
-```` 
+````
 
-#### Mesos logs 
-Mesos logs are stored at `/opt/lt-mesos-master.INFO` on `node0` and 
`/opt/lt-mesos-slave.INFO` at other nodes. 
+#### Mesos logs
+Mesos logs are stored at `/opt/lt-mesos-master.INFO` on `node0` and 
`/opt/lt-mesos-slave.INFO` at other nodes.
 
 ---
 
 ## Starting SINGA training on Mesos
-Assumed that Mesos and HDFS are already started, SINGA job can be launched at 
**any** container. 
+Assumed that Mesos and HDFS are already started, SINGA job can be launched at 
**any** container.
 
 #### Launching job
 
@@ -52,7 +52,7 @@ Assumed that Mesos and HDFS are already
 3. Start the job:
     + If starting for the first time:
 
-                 ./scheduler <job config file> -scheduler_conf <scheduler 
config file> -singa_conf <SINGA config file> 
+                 ./scheduler <job config file> -scheduler_conf <scheduler 
config file> -singa_conf <SINGA config file>
     + If not the first time:
 
                  ./scheduler <job config file>
@@ -70,7 +70,7 @@ during SINGA execution can be found at:
             
/tmp/mesos/slaves/xxxxx-Sx/frameworks/xxxxx/executors/SINGA_x/runs/latest/stderr
 
 Other artifacts, like files downloaded from HDFS (`job.conf`) and `stdout` can 
be found in the same
-directory. 
+directory.
 
 #### Stopping