Regen all docs. (#700)

* Stop recursing if discovery == {}

* Generate docs with 'make docs'.
diff --git a/docs/dyn/spanner_v1.projects.instances.databases.operations.html b/docs/dyn/spanner_v1.projects.instances.databases.operations.html
index 10a68a8..6a97795 100644
--- a/docs/dyn/spanner_v1.projects.instances.databases.operations.html
+++ b/docs/dyn/spanner_v1.projects.instances.databases.operations.html
@@ -84,7 +84,7 @@
   <code><a href="#get">get(name, x__xgafv=None)</a></code></p>
 <p class="firstline">Gets the latest state of a long-running operation.  Clients can use this</p>
 <p class="toc_element">
-  <code><a href="#list">list(name, pageSize=None, filter=None, pageToken=None, x__xgafv=None)</a></code></p>
+  <code><a href="#list">list(name, pageToken=None, x__xgafv=None, pageSize=None, filter=None)</a></code></p>
 <p class="firstline">Lists operations that match the specified filter in the request. If the</p>
 <p class="toc_element">
   <code><a href="#list_next">list_next(previous_request, previous_response)</a></code></p>
@@ -178,40 +178,24 @@
         # long-running operation should document the metadata type, if any.
       "a_key": "", # Properties of the object. Contains field @type with type URL.
     },
-    "done": True or False, # If the value is `false`, it means the operation is still in progress.
-        # If true, the operation is completed, and either `error` or `response` is
-        # available.
-    "response": { # The normal response of the operation in case of success.  If the original
-        # method returns no data on success, such as `Delete`, the response is
-        # `google.protobuf.Empty`.  If the original method is standard
-        # `Get`/`Create`/`Update`, the response should be the resource.  For other
-        # methods, the response should have the type `XxxResponse`, where `Xxx`
-        # is the original method name.  For example, if the original method name
-        # is `TakeSnapshot()`, the inferred response type is
-        # `TakeSnapshotResponse`.
-      "a_key": "", # Properties of the object. Contains field @type with type URL.
-    },
-    "name": "A String", # The server-assigned name, which is only unique within the same service that
-        # originally returns it. If you use the default HTTP mapping, the
-        # `name` should have the format of `operations/some/unique/name`.
-    "error": { # The `Status` type defines a logical error model that is suitable for different # The error result of the operation in case of failure or cancellation.
-        # programming environments, including REST APIs and RPC APIs. It is used by
-        # [gRPC](https://github.com/grpc). The error model is designed to be:
+    "error": { # The `Status` type defines a logical error model that is suitable for # The error result of the operation in case of failure or cancellation.
+        # different programming environments, including REST APIs and RPC APIs. It is
+        # used by [gRPC](https://github.com/grpc). The error model is designed to be:
         #
         # - Simple to use and understand for most users
         # - Flexible enough to meet unexpected needs
         #
         # # Overview
         #
-        # The `Status` message contains three pieces of data: error code, error message,
-        # and error details. The error code should be an enum value of
+        # The `Status` message contains three pieces of data: error code, error
+        # message, and error details. The error code should be an enum value of
         # google.rpc.Code, but it may accept additional error codes if needed.  The
         # error message should be a developer-facing English message that helps
         # developers *understand* and *resolve* the error. If a localized user-facing
         # 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
         #
@@ -234,7 +218,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
@@ -250,33 +234,54 @@
           # user-facing error message should be localized and sent in the
           # google.rpc.Status.details field, or localized by the client.
       "code": 42, # The status code, which should be an enum value of google.rpc.Code.
-      "details": [ # A list of messages that carry the error details.  There will be a
-          # common set of message types for APIs to use.
+      "details": [ # A list of messages that carry the error details.  There is a common set of
+          # message types for APIs to use.
         {
           "a_key": "", # Properties of the object. Contains field @type with type URL.
         },
       ],
     },
+    "done": True or False, # If the value is `false`, it means the operation is still in progress.
+        # If `true`, the operation is completed, and either `error` or `response` is
+        # available.
+    "response": { # The normal response of the operation in case of success.  If the original
+        # method returns no data on success, such as `Delete`, the response is
+        # `google.protobuf.Empty`.  If the original method is standard
+        # `Get`/`Create`/`Update`, the response should be the resource.  For other
+        # methods, the response should have the type `XxxResponse`, where `Xxx`
+        # is the original method name.  For example, if the original method name
+        # is `TakeSnapshot()`, the inferred response type is
+        # `TakeSnapshotResponse`.
+      "a_key": "", # Properties of the object. Contains field @type with type URL.
+    },
+    "name": "A String", # The server-assigned name, which is only unique within the same service that
+        # originally returns it. If you use the default HTTP mapping, the
+        # `name` should be a resource name ending with `operations/{unique_id}`.
   }</pre>
 </div>
 
 <div class="method">
-    <code class="details" id="list">list(name, pageSize=None, filter=None, pageToken=None, x__xgafv=None)</code>
+    <code class="details" id="list">list(name, pageToken=None, x__xgafv=None, pageSize=None, filter=None)</code>
   <pre>Lists operations that match the specified filter in the request. If the
 server doesn't support this method, it returns `UNIMPLEMENTED`.
 
-NOTE: the `name` binding below allows API services to override the binding
-to use different resource name schemes, such as `users/*/operations`.
+NOTE: the `name` binding allows API services to override the binding
+to use different resource name schemes, such as `users/*/operations`. To
+override the binding, API services can add a binding such as
+`"/v1/{name=users/*}/operations"` to their service configuration.
+For backwards compatibility, the default name includes the operations
+collection id, however overriding users must ensure the name binding
+is the parent resource, without the operations collection id.
 
 Args:
-  name: string, The name of the operation collection. (required)
-  pageSize: integer, The standard list page size.
-  filter: string, The standard list filter.
+  name: string, The name of the operation's parent resource. (required)
   pageToken: string, The standard list page token.
   x__xgafv: string, V1 error format.
     Allowed values
       1 - v1 error format
       2 - v2 error format
+  pageSize: integer, The standard list page size.
+  filter: string, The standard list filter.
 
 Returns:
   An object of the form:
@@ -291,40 +296,24 @@
             # long-running operation should document the metadata type, if any.
           "a_key": "", # Properties of the object. Contains field @type with type URL.
         },
-        "done": True or False, # If the value is `false`, it means the operation is still in progress.
-            # If true, the operation is completed, and either `error` or `response` is
-            # available.
-        "response": { # The normal response of the operation in case of success.  If the original
-            # method returns no data on success, such as `Delete`, the response is
-            # `google.protobuf.Empty`.  If the original method is standard
-            # `Get`/`Create`/`Update`, the response should be the resource.  For other
-            # methods, the response should have the type `XxxResponse`, where `Xxx`
-            # is the original method name.  For example, if the original method name
-            # is `TakeSnapshot()`, the inferred response type is
-            # `TakeSnapshotResponse`.
-          "a_key": "", # Properties of the object. Contains field @type with type URL.
-        },
-        "name": "A String", # The server-assigned name, which is only unique within the same service that
-            # originally returns it. If you use the default HTTP mapping, the
-            # `name` should have the format of `operations/some/unique/name`.
-        "error": { # The `Status` type defines a logical error model that is suitable for different # The error result of the operation in case of failure or cancellation.
-            # programming environments, including REST APIs and RPC APIs. It is used by
-            # [gRPC](https://github.com/grpc). The error model is designed to be:
+        "error": { # The `Status` type defines a logical error model that is suitable for # The error result of the operation in case of failure or cancellation.
+            # different programming environments, including REST APIs and RPC APIs. It is
+            # used by [gRPC](https://github.com/grpc). The error model is designed to be:
             #
             # - Simple to use and understand for most users
             # - Flexible enough to meet unexpected needs
             #
             # # Overview
             #
-            # The `Status` message contains three pieces of data: error code, error message,
-            # and error details. The error code should be an enum value of
+            # The `Status` message contains three pieces of data: error code, error
+            # message, and error details. The error code should be an enum value of
             # google.rpc.Code, but it may accept additional error codes if needed.  The
             # error message should be a developer-facing English message that helps
             # developers *understand* and *resolve* the error. If a localized user-facing
             # 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
             #
@@ -347,7 +336,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
@@ -363,13 +352,29 @@
               # user-facing error message should be localized and sent in the
               # google.rpc.Status.details field, or localized by the client.
           "code": 42, # The status code, which should be an enum value of google.rpc.Code.
-          "details": [ # A list of messages that carry the error details.  There will be a
-              # common set of message types for APIs to use.
+          "details": [ # A list of messages that carry the error details.  There is a common set of
+              # message types for APIs to use.
             {
               "a_key": "", # Properties of the object. Contains field @type with type URL.
             },
           ],
         },
+        "done": True or False, # If the value is `false`, it means the operation is still in progress.
+            # If `true`, the operation is completed, and either `error` or `response` is
+            # available.
+        "response": { # The normal response of the operation in case of success.  If the original
+            # method returns no data on success, such as `Delete`, the response is
+            # `google.protobuf.Empty`.  If the original method is standard
+            # `Get`/`Create`/`Update`, the response should be the resource.  For other
+            # methods, the response should have the type `XxxResponse`, where `Xxx`
+            # is the original method name.  For example, if the original method name
+            # is `TakeSnapshot()`, the inferred response type is
+            # `TakeSnapshotResponse`.
+          "a_key": "", # Properties of the object. Contains field @type with type URL.
+        },
+        "name": "A String", # The server-assigned name, which is only unique within the same service that
+            # originally returns it. If you use the default HTTP mapping, the
+            # `name` should be a resource name ending with `operations/{unique_id}`.
       },
     ],
     "nextPageToken": "A String", # The standard List next-page token.