Clean and regen docs (#401)
diff --git a/docs/dyn/genomics_v1alpha2.operations.html b/docs/dyn/genomics_v1alpha2.operations.html
index 98d2f66..25da44e 100644
--- a/docs/dyn/genomics_v1alpha2.operations.html
+++ b/docs/dyn/genomics_v1alpha2.operations.html
@@ -157,7 +157,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
#
@@ -180,7 +180,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
@@ -218,7 +218,7 @@
<pre>Lists operations that match the specified filter in the request.
Args:
- name: string, The name of the operation collection. (required)
+ name: string, The name of the operation's parent resource. (required)
pageSize: integer, The maximum number of results to return. If unspecified, defaults to
256. The maximum value is 2048.
filter: string, A string for filtering Operations.
@@ -272,7 +272,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
#
@@ -295,7 +295,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