more work on man page (take 3)

README.md

@@ -68,6 +68,9 @@ repository to the `/root` directory. The main container is Google's
 [`values.yaml`](common/helm/values.yaml) (see "Configuration" below).
 The program `gcp-cloudsql-archive.py` in turn calls `gcloud`.
 
+See also the [man page for
+`gcp-cloudsql-archive.py`](gcp-cloudsql-archive.md).
+
 ## Configuration
 
 All configuration is made in
@@ -136,7 +139,10 @@ the data from the Cloud SQL instance and write to the Cloud Storage
 bucket. The permissions needed are described on the ["Exporting and
 importing using SQL dump files" page][1].
 
-See also [this StackOverflow answer][6].
+You will also need to grant the service account associated with the Cloud
+SQL instance the right to create storage objects. For more details on this
+as well as Terraform code to enable these permissions see [this
+StackOverflow answer][6].
 
 
 [1]: https://cloud.google.com/sdk/gcloud/reference/sql/export/sql

gcp-cloudsql-archive.md

@@ -24,7 +24,7 @@ Example: In the context of GCP project **my-project** export the databases
 
 The above command will dump the databases **db1**, **db2**, and **db3** to
 the objects `gs://my-bucket/db1.gz`, `gs://my-bucket/db2.gz`,
-`gs://my-bucket/db3.gz` respectively.
+and `gs://my-bucket/db3.gz` respectively.
 
 Note that the "option" **--databases** is required.