Fix Kubespray installation docs

Change-Id: I087765836e76e9bb2278d3ebbe24ccf9fe83b3a4
diff --git a/prereqs/k8s-multi-node.md b/prereqs/k8s-multi-node.md
index d606416..febe128 100644
--- a/prereqs/k8s-multi-node.md
+++ b/prereqs/k8s-multi-node.md
@@ -25,7 +25,7 @@
     * Run Ubuntu 16.04 server
     * Able to communicate together (ping one each other)
     * Have the same user *cord* configured, that you can use to remotely access them from the operator machine
-    * The user *cord* is sudoer on each machine, and it doesn't need a password to get sudoer privileges
+    * The user *cord* is sudoer on each machine, and it doesn't need a password to get sudoer privileges (see to authorize a password-less access from the development/management machine in the sections below)
 
 ## Download the Kubespray Installation Scripts
 
@@ -46,6 +46,13 @@
 * Export the k8s configuration file path as environment variable to
    let the user access a specific deployment
 
+## Prepare for the Kubespray installation
+
+Before starting the installation make sure that
+
+* The development/management machine has password-less access to the target machine(s), meaning the public key of the development/management machine has been copied in the authorization_keys files on the target machines. If you don't know how to do a script called *copy-ssh-keys.sh* is provided. To copy your public key to a target machine run *./copy-ssh-keys.sh TARGET_MACHINE_IP*. Repeat this procedure for each target machine.
+* All target machines don't mount any swap partition. It's easy as simply installing Ubuntu without a swap partition or -once the OS is already installed- commenting out the corresponding line in */etc/fstab* and reboot.
+
 ## Install Kubespray
 
 The following example assumes that
@@ -61,7 +68,6 @@
 
 * Cleans up any old Kubespray installation folder (may be there from previous installations)
 * Clones the official Kubespray installation repository
-* Copies the public key of the operator machine, over to each target machine
 * Installs required software and configures the target machines as prescribed in the Kubespray guide
 * Deploys Kubespray
 * Downloads and exports the access configuration outside the Kubespray folder, so it won’t be removed at the next execution of the script (for example while trying to re-deploy the POD, or while deploying a different POD)
@@ -71,8 +77,9 @@
 ./setup.sh -i onf 10.90.0.101 10.90.0.102 10.90.0.103
 ```
 
-At the beginning of the installation you will be asked to insert your
+> **NOTE:** at the beginning of the installation you will be asked to insert your
 password multiple times.
+> **NOTE:** the official Kubespray instalation procedure -run by the script- will automatically change the hostname of the target machine(s) with nodeX (where X is an incremental number starting from 1).
 
 At the end of the procedure, Kubespray should be installed and running
 on the remote machines.