Regen docs (#373)

diff --git a/docs/dyn/servicemanagement_v1.services.rollouts.html b/docs/dyn/servicemanagement_v1.services.rollouts.html
index d183d56..7bf92d0 100644
--- a/docs/dyn/servicemanagement_v1.services.rollouts.html
+++ b/docs/dyn/servicemanagement_v1.services.rollouts.html
@@ -112,6 +112,14 @@
     "status": "A String", # The status of this rollout. Readonly. In case of a failed rollout,
         # the system will automatically rollback to the current Rollout
         # version. Readonly.
+    "rolloutId": "A String", # Optional unique identifier of this Rollout. Only lower case letters, digits
+        #  and '-' are allowed.
+        # 
+        # If not specified by client, the server will generate one. The generated id
+        # will have the form of <date><revision number>, where "date" is the create
+        # date in ISO 8601 format.  "revision number" is a monotonically increasing
+        # positive number that is reset every day for each service.
+        # An example of the generated rollout_id is '2016-02-16r1'
     "trafficPercentStrategy": { # Strategy that specifies how Google Service Control should select # Google Service Control selects service configurations based on
         # traffic percentage.
         # different
@@ -148,20 +156,12 @@
         "a_key": 3.14,
       },
     },
-    "rolloutId": "A String", # Optional unique identifier of this Rollout. Only lower case letters, digits
-        #  and '-' are allowed.
-        # 
-        # If not specified by client, the server will generate one. The generated id
-        # will have the form of <date><revision number>, where "date" is the create
-        # date in ISO 8601 format.  "revision number" is a monotonically increasing
-        # positive number that is reset every day for each service.
-        # An example of the generated rollout_id is '2016-02-16r1'
-    "serviceName": "A String", # The name of the service associated with this Rollout.
     "createdBy": "A String", # The user who created the Rollout. Readonly.
     "deleteServiceStrategy": { # Strategy used to delete a service. This strategy is a placeholder only # The strategy associated with a rollout to delete a `ManagedService`.
         # Readonly.
         # used by the system generated rollout to delete a service.
     },
+    "serviceName": "A String", # The name of the service associated with this Rollout.
     "createTime": "A String", # Creation time of the rollout. Readonly.
   }
 
@@ -285,6 +285,14 @@
       "status": "A String", # The status of this rollout. Readonly. In case of a failed rollout,
           # the system will automatically rollback to the current Rollout
           # version. Readonly.
+      "rolloutId": "A String", # Optional unique identifier of this Rollout. Only lower case letters, digits
+          #  and '-' are allowed.
+          #
+          # If not specified by client, the server will generate one. The generated id
+          # will have the form of <date><revision number>, where "date" is the create
+          # date in ISO 8601 format.  "revision number" is a monotonically increasing
+          # positive number that is reset every day for each service.
+          # An example of the generated rollout_id is '2016-02-16r1'
       "trafficPercentStrategy": { # Strategy that specifies how Google Service Control should select # Google Service Control selects service configurations based on
           # traffic percentage.
           # different
@@ -321,20 +329,12 @@
           "a_key": 3.14,
         },
       },
-      "rolloutId": "A String", # Optional unique identifier of this Rollout. Only lower case letters, digits
-          #  and '-' are allowed.
-          #
-          # If not specified by client, the server will generate one. The generated id
-          # will have the form of <date><revision number>, where "date" is the create
-          # date in ISO 8601 format.  "revision number" is a monotonically increasing
-          # positive number that is reset every day for each service.
-          # An example of the generated rollout_id is '2016-02-16r1'
-      "serviceName": "A String", # The name of the service associated with this Rollout.
       "createdBy": "A String", # The user who created the Rollout. Readonly.
       "deleteServiceStrategy": { # Strategy used to delete a service. This strategy is a placeholder only # The strategy associated with a rollout to delete a `ManagedService`.
           # Readonly.
           # used by the system generated rollout to delete a service.
       },
+      "serviceName": "A String", # The name of the service associated with this Rollout.
       "createTime": "A String", # Creation time of the rollout. Readonly.
     }</pre>
 </div>
@@ -366,6 +366,14 @@
           "status": "A String", # The status of this rollout. Readonly. In case of a failed rollout,
               # the system will automatically rollback to the current Rollout
               # version. Readonly.
+          "rolloutId": "A String", # Optional unique identifier of this Rollout. Only lower case letters, digits
+              #  and '-' are allowed.
+              #
+              # If not specified by client, the server will generate one. The generated id
+              # will have the form of <date><revision number>, where "date" is the create
+              # date in ISO 8601 format.  "revision number" is a monotonically increasing
+              # positive number that is reset every day for each service.
+              # An example of the generated rollout_id is '2016-02-16r1'
           "trafficPercentStrategy": { # Strategy that specifies how Google Service Control should select # Google Service Control selects service configurations based on
               # traffic percentage.
               # different
@@ -402,20 +410,12 @@
               "a_key": 3.14,
             },
           },
-          "rolloutId": "A String", # Optional unique identifier of this Rollout. Only lower case letters, digits
-              #  and '-' are allowed.
-              #
-              # If not specified by client, the server will generate one. The generated id
-              # will have the form of <date><revision number>, where "date" is the create
-              # date in ISO 8601 format.  "revision number" is a monotonically increasing
-              # positive number that is reset every day for each service.
-              # An example of the generated rollout_id is '2016-02-16r1'
-          "serviceName": "A String", # The name of the service associated with this Rollout.
           "createdBy": "A String", # The user who created the Rollout. Readonly.
           "deleteServiceStrategy": { # Strategy used to delete a service. This strategy is a placeholder only # The strategy associated with a rollout to delete a `ManagedService`.
               # Readonly.
               # used by the system generated rollout to delete a service.
           },
+          "serviceName": "A String", # The name of the service associated with this Rollout.
           "createTime": "A String", # Creation time of the rollout. Readonly.
         },
     ],