Merge "Fix README instructions"

README.rst

@@ -120,16 +120,15 @@ Usage
 
    If you previously ran a test with refstack-client without the ``--upload``
    option, you can later upload your results to a RefStack API server
-   anonymously or with your digital signature. By default, results uploaded
-   with signature are private and you can decide to share or delete the results
-   later. Uploading results with signature is the recommended option.
+   with your digital signature. By default, the results are private and you can
+   decide to share or delete the results later.
 
-   Following is the command to upload your result anonymously::
+   Following is the command to upload your result::
 
-       refstack-client upload <Path of results file>
+       refstack-client upload <Path of results file> -i <path-to-private-key>
 
    The results file is a JSON file generated by refstack-client when a test has
-   completed. This is saved in .tempest/.testrepository. When you use the
+   completed. This is saved in .tempest/.stestr. When you use the
    ``upload`` command, you can also override the RefStack API server uploaded to
    with the ``--url`` option.
 
@@ -137,11 +136,11 @@ Usage
    using an existing subunit file. This requires that you pass in the Keystone
    endpoint URL for the cloud that was tested to generate the subunit data::
 
-       refstack-client upload-subunit --keystone-endpoint http://some.url:5000/v3 <Path of subunit file>
+       refstack-client upload-subunit \
+         --keystone-endpoint http://some.url:5000/v3 <Path of subunit file> \
+         -i <path-to-private-key>
 
-   Result can also be uploaded with signature by adding
-   ``-i <path-to-private-key>`` option.  Intructions for uploading data with
-   signature can be found at
+   Intructions for uploading data with signature can be found at
    https://github.com/openstack/refstack/blob/master/doc/source/uploading_private_results.rst
 
 7. Create a JSON web token to use for authentication to your privately