Edit to README.bst to note that the ssh keys needed in the targets en…

…tries are the hosts public ssh key and not the users defined in the same entry

README.rst

@@ -67,9 +67,9 @@ the nodes & use the live cluster ad hoc), might look like this::
 	- [mon.1, osd.1]
 	- [mon.2, client.0]
 	targets:
-	  [email protected]: ssh-rsa long_key_here
-	  [email protected]: ssh-rsa other_key
-	  [email protected]: ssh-rsa third_key
+	  [email protected]: ssh-rsa host07_ssh_key 
+	  [email protected]: ssh-rsa host08_ssh_key
+	  [email protected]: ssh-rsa host09_ssh_key
 	tasks:
 	- ceph:
 	- ceph-fuse: [client.0]
@@ -81,7 +81,9 @@ Note the colon after every task name in the ``tasks`` section.
 
 You need to be able to SSH in to the listed targets without
 passphrases, and the remote user needs to have passphraseless `sudo`
-access.
+access. Note that the ssh key at the end of the ``targets``
+entries are the public ssh keys for the hosts. 
+On Ubuntu, this is located at /etc/ssh/ssh_host_rsa_key.pub
 
 If you'd save the above file as ``example.yaml``, you could run
 teuthology on it by saying::