update docs

Author: datacharmer

Diff for: README.md

@@ -1,7 +1,7 @@
 [DBdeployer](https://github.com/datacharmer/dbdeployer) is a tool that deploys MySQL database servers easily.
 This is a port of [MySQL-Sandbox](https://github.com/datacharmer/mysql-sandbox), originally written in Perl, and re-designed from the ground up in [Go](https://golang.org). See the [features comparison](https://github.com/datacharmer/dbdeployer/blob/master/docs/features.md) for more detail.
 
-Documentation updated for version 1.41.0 (26-Oct-2019 20:41 UTC)
+Documentation updated for version 1.42.0 (02-Nov-2019 08:44 UTC)
 
 [![Build Status](https://travis-ci.org/datacharmer/dbdeployer.svg "Travis CI status")](https://travis-ci.org/datacharmer/dbdeployer)
 
@@ -58,7 +58,7 @@ Get the one for your O.S. from [dbdeployer releases](https://github.com/datachar
 
 For example:
 
-    $ VERSION=1.41.0
+    $ VERSION=1.42.0
     $ OS=linux
     $ origin=https://github.com/datacharmer/dbdeployer/releases/download/v$VERSION
     $ wget $origin/dbdeployer-$VERSION.$OS.tar.gz
@@ -161,7 +161,7 @@ For example:
 The program doesn't have any dependencies. Everything is included in the binary. Calling *dbdeployer* without arguments or with ``--help`` will show the main help screen.
 
     $ dbdeployer --version
-    dbdeployer version 1.41.0
+    dbdeployer version 1.42.0
 
 
     $ dbdeployer -h
@@ -391,14 +391,14 @@ The ``deploy replication`` command will install a master and two or more slaves,
     Flags:
       -h, --help                     help for replication
           --master-ip string         Which IP the slaves will connect to (default "127.0.0.1")
-          --master-list string       Which nodes are masters in a multi-source deployment (default "1,2")
+          --master-list string       Which nodes are masters in a multi-source deployment
           --ndb-nodes int            How many NDB nodes will be installed (default 3)
       -n, --nodes int                How many nodes will be installed (default 3)
           --read-only-slaves         Set read-only for slaves
           --repl-history-dir         uses the replication directory to store mysql client history
           --semi-sync                Use semi-synchronous plugin
           --single-primary           Using single primary for group replication
-          --slave-list string        Which nodes are slaves in a multi-source deployment (default "3")
+          --slave-list string        Which nodes are slaves in a multi-source deployment
           --super-read-only-slaves   Set super-read-only for slaves
       -t, --topology string          Which topology will be installed (default "master-slave")
 
@@ -1950,10 +1950,10 @@ Should you need to compile your own binaries for dbdeployer, follow these steps:
 Between this file and [the API API list](https://github.com/datacharmer/dbdeployer/blob/master/docs/API/API-1.1.md), you have all the existing documentation for dbdeployer.
 Should you need additional formats, though, dbdeployer is able to generate them on-the-fly. Tou will need the docs-enabled binaries: in the distribution list, you will find:
 
-* dbdeployer-1.41.0-docs.linux.tar.gz
-* dbdeployer-1.41.0-docs.osx.tar.gz
-* dbdeployer-1.41.0.linux.tar.gz
-* dbdeployer-1.41.0.osx.tar.gz
+* dbdeployer-1.42.0-docs.linux.tar.gz
+* dbdeployer-1.42.0-docs.osx.tar.gz
+* dbdeployer-1.42.0.linux.tar.gz
+* dbdeployer-1.42.0.osx.tar.gz
 
 The executables containing ``-docs`` in their name have the same capabilities of the regular ones, but in addition they can run the *hidden* command ``tree``, with alias ``docs``.