Clean and regen docs (#401)
diff --git a/docs/dyn/genomics_v1.variantsets.html b/docs/dyn/genomics_v1.variantsets.html
index 4354c92..b5a7047 100644
--- a/docs/dyn/genomics_v1.variantsets.html
+++ b/docs/dyn/genomics_v1.variantsets.html
@@ -273,18 +273,18 @@
The object takes the form of:
{ # The variant data export request.
- "projectId": "A String", # Required. The Google Cloud project ID that owns the destination
- # BigQuery dataset. The caller must have WRITE access to this project. This
- # project will also own the resulting export job.
+ "bigqueryDataset": "A String", # Required. The BigQuery dataset to export data to. This dataset must already
+ # exist. Note that this is distinct from the Genomics concept of "dataset".
"bigqueryTable": "A String", # Required. The BigQuery table to export data to.
# If the table doesn't exist, it will be created. If it already exists, it
# will be overwritten.
- "bigqueryDataset": "A String", # Required. The BigQuery dataset to export data to. This dataset must already
- # exist. Note that this is distinct from the Genomics concept of "dataset".
"callSetIds": [ # If provided, only variant call information from the specified call sets
# will be exported. By default all variant calls are exported.
"A String",
],
+ "projectId": "A String", # Required. The Google Cloud project ID that owns the destination
+ # BigQuery dataset. The caller must have WRITE access to this project. This
+ # project will also own the resulting export job.
"format": "A String", # The format for the exported data.
}
@@ -318,7 +318,7 @@
# error message is needed, put the localized message in the error details or
# localize it in the client. The optional error details may contain arbitrary
# information about the error. There is a predefined set of error detail types
- # in the package `google.rpc` which can be used for common error conditions.
+ # in the package `google.rpc` that can be used for common error conditions.
#
# # Language mapping
#
@@ -341,7 +341,7 @@
# errors.
#
# - Workflow errors. A typical workflow has multiple steps. Each step may
- # have a `Status` message for error reporting purpose.
+ # have a `Status` message for error reporting.
#
# - Batch operations. If a client uses batch request and batch response, the
# `Status` message should be used directly inside batch response, one for