From 187bba149ed5c336c854d3a8edc0b4199c386f4d Mon Sep 17 00:00:00 2001
From: Christian Rößler
Date: Mon, 25 Nov 2013 14:13:48 +0100
Subject: [doc] setup_howto: minor additions -> default usage

---
 doc/setup_howto | 11 +++++------
 1 file changed, 5 insertions(+), 6 deletions(-)

(limited to 'doc')

diff --git a/doc/setup_howto b/doc/setup_howto
index abc7e2bb..73226a39 100644
--- a/doc/setup_howto
+++ b/doc/setup_howto
@@ -88,7 +88,6 @@ Build addons (vmware etc.)
 # ./mltk remote debug -c -b (as always: -d -> debug when appropriate)
 
 
-
 7. Packaging
 
 When using the parameter 'server' either an IP adress or 'local' is expected. 
@@ -107,17 +106,17 @@ server machine via rsync. To facilitate this rsync-ing it may be wise to
 add the ssh key to the build machine (authorized_keys), as then no password 
 has to be given when syncing from the server machine.
 
-## Das würde ich für die Zukunft als Default annehmen. Das andere ist ja eher
-## zum Testen in sehr kleinem Setup.
 So, remember to execute
 # ./mltk remote -n
-on the build machine, if the build is going to by synchronized to a dedicated 
-server machine.
+on the build machine, as the build is usually going to by synchronized to a 
+dedicated server machine.
 
 
 7.1 Packaging locally (build and server machine are the same machine)
 
-To package stages and addons (for example vmware), presuming the same machine 
+Even though the usual way to go is using dedicated machines to build and to 
+serve it is possible to package locally, e.g. for testing purposes. So, to 
+package stages and addons (for example vmware), presuming the same machine 
 is used for building and serving:
 # ./mltk server local stage31 -e stage31
 # ./mltk server local stage32 -e stage32
-- 
cgit v1.2.3-55-g7522