aurora git commit: Fix minor inconsistencies in the storage documentation.

[ke...@apache.org]

Repository: aurora
Updated Branches:
  refs/heads/master 7408cb3ea -> 8816d49a4


Fix minor inconsistencies in the storage documentation.

Reviewed at https://reviews.apache.org/r/39169/


Project: http://git-wip-us.apache.org/repos/asf/aurora/repo
Commit: http://git-wip-us.apache.org/repos/asf/aurora/commit/8816d49a
Tree: http://git-wip-us.apache.org/repos/asf/aurora/tree/8816d49a
Diff: http://git-wip-us.apache.org/repos/asf/aurora/diff/8816d49a

Branch: refs/heads/master
Commit: 8816d49a4286ebe0610a2cfb103fbc1fa420f641
Parents: 7408cb3
Author: Stephan Erb <st...@dev.static-void.de>
Authored: Fri Oct 9 14:00:03 2015 +0100
Committer: Kevin Sweeney <ke...@apache.org>
Committed: Fri Oct 9 14:00:03 2015 +0100

----------------------------------------------------------------------
 docs/storage-config.md | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)
----------------------------------------------------------------------


http://git-wip-us.apache.org/repos/asf/aurora/blob/8816d49a/docs/storage-config.md
----------------------------------------------------------------------
diff --git a/docs/storage-config.md b/docs/storage-config.md
index 4ec33a1..c838ea3 100644
--- a/docs/storage-config.md
+++ b/docs/storage-config.md
@@ -99,7 +99,7 @@ accomplished by updating the following scheduler configuration options:
   * Set `-mesos_master_address` to a non-existent zk address. This will prevent scheduler from
     registering with Mesos. E.g.: `-mesos_master_address=zk://localhost:2181`
   * `-max_registration_delay` - set to sufficiently long interval to prevent registration timeout
-    and as a result scheduler suicide. E.g: `-max_registration_delay=360min`
+    and as a result scheduler suicide. E.g: `-max_registration_delay=360mins`
   * Make sure `-reconciliation_initial_delay` option is set high enough (e.g.: `365days`) to
     prevent accidental task GC. This is important as scheduler will attempt to reconcile the cluster
     state and will kill all tasks when restarted with an empty Mesos replicated log.
@@ -112,7 +112,7 @@ Get rid of the corrupted files and re-initialize Mesos replicate log:
 
 * Stop schedulers
 * Delete all files under `-native_log_file_path` on all schedulers
-* Initialize Mesos replica's log file: `mesos-log initialize <-native_log_file_path>`
+* Initialize Mesos replica's log file: `mesos-log initialize --path=<-native_log_file_path>`
 * Restart schedulers
 
 ### Restore from backup