chore: Update discovery artifacts

docs/dyn/addressvalidation_v1.v1.html

@@ -270,7 +270,7 @@ <h3>Method Details</h3>
         &quot;globalCode&quot;: &quot;A String&quot;, # Place&#x27;s global (full) code, such as &quot;9FWM33GV+HQ&quot;, representing an 1/8000 by 1/8000 degree area (~14 by 14 meters).
       },
     },
-    &quot;metadata&quot;: { # The metadata for the address. `metadata` is not guaranteed to be fully populated for every address sent to the Address Validation API. # Other information relevant to deliverability. `metadata` is not guaranteed to be fully populated for every address sent to the Address Validation API.
+    &quot;metadata&quot;: { # The metadata for the post-processed address. `metadata` is not guaranteed to be fully populated for every address sent to the Address Validation API. # Other information relevant to deliverability. `metadata` is not guaranteed to be fully populated for every address sent to the Address Validation API.
       &quot;business&quot;: True or False, # Indicates that this is the address of a business. If unset, indicates that the value is unknown.
       &quot;poBox&quot;: True or False, # Indicates that the address of a PO box. If unset, indicates that the value is unknown.
       &quot;residential&quot;: True or False, # Indicates that this is the address of a residence. If unset, indicates that the value is unknown.
@@ -325,13 +325,15 @@ <h3>Method Details</h3>
       &quot;suitelinkFootnote&quot;: &quot;A String&quot;, # Footnotes from matching a street or highrise record to suite information. If business name match is found, the secondary number is returned. * `A`: SuiteLink record match, business address improved. * `00`: No match, business address is not improved.
     },
     &quot;verdict&quot;: { # High level overview of the address validation result and geocode. # Overall verdict flags
-      &quot;addressComplete&quot;: True or False, # The address is considered complete if there are no unresolved tokens, no unexpected or missing address components. If unset, indicates that the value is `false`. See `missing_component_types`, `unresolved_tokens` or `unexpected` fields for more details.
+      &quot;addressComplete&quot;: True or False, # The post-processed address is considered complete if there are no unresolved tokens, no unexpected or missing address components. If unset, indicates that the value is `false`. See `missing_component_types`, `unresolved_tokens` or `unexpected` fields for more details.
       &quot;geocodeGranularity&quot;: &quot;A String&quot;, # Information about the granularity of the `geocode`. This can be understood as the semantic meaning of how coarse or fine the geocoded location is. This can differ from the `validation_granularity` above occasionally. For example, our database might record the existence of an apartment number but do not have a precise location for the apartment within a big apartment complex. In that case, the `validation_granularity` will be `SUB_PREMISE` but the `geocode_granularity` will be `PREMISE`.
       &quot;hasInferredComponents&quot;: True or False, # At least one address component was inferred (added) that wasn&#x27;t in the input, see [google.maps.addressvalidation.v1.Address.address_components] for details.
       &quot;hasReplacedComponents&quot;: True or False, # At least one address component was replaced, see [google.maps.addressvalidation.v1.Address.address_components] for details.
+      &quot;hasSpellCorrectedComponents&quot;: True or False, # At least one address component was spell-corrected, see [google.maps.addressvalidation.v1.Address.address_components] for details.
       &quot;hasUnconfirmedComponents&quot;: True or False, # At least one address component cannot be categorized or validated, see [google.maps.addressvalidation.v1.Address.address_components] for details.
-      &quot;inputGranularity&quot;: &quot;A String&quot;, # The granularity of the **input** address. This is the result of parsing the input address and does not give any validation signals. For validation signals, refer to `validation_granularity` below. For example, if the input address includes a specific apartment number, then the `input_granularity` here will be `SUB_PREMISE`. If we cannot match the apartment number in the databases or the apartment number is invalid, the `validation_granularity` will likely be `PREMISE` or worse.
-      &quot;validationGranularity&quot;: &quot;A String&quot;, # The granularity level that the API can fully **validate** the address to. For example, an `validation_granularity` of `PREMISE` indicates all address components at the level of `PREMISE` or more coarse can be validated. Per address component validation result can be found in [google.maps.addressvalidation.v1.Address.address_components].
+      &quot;inputGranularity&quot;: &quot;A String&quot;, # The granularity of the **input** address. This is the result of parsing the input address and does not give any validation signals. For validation signals, refer to `validation_granularity` below. For example, if the input address includes a specific apartment number, then the `input_granularity` here will be `SUB_PREMISE`. If the address validation service cannot match the apartment number in the databases or the apartment number is invalid, the `validation_granularity` will likely be `PREMISE` or more coarse.
+      &quot;possibleNextAction&quot;: &quot;A String&quot;, # Preview: This feature is in Preview (pre-GA). Pre-GA products and features might have limited support, and changes to pre-GA products and features might not be compatible with other pre-GA versions. Pre-GA Offerings are covered by the [Google Maps Platform Service Specific Terms](https://cloud.google.com/maps-platform/terms/maps-service-terms). For more information, see the [launch stage descriptions](https://developers.google.com/maps/launch-stages). Offers an interpretive summary of the API response, intended to assist in determining a potential subsequent action to take. This field is derived from other fields in the API response and should not be considered as a guarantee of address accuracy or deliverability. See [Build your validation logic](https://developers.google.com/maps/documentation/address-validation/build-validation-logic) for more details.
+      &quot;validationGranularity&quot;: &quot;A String&quot;, # The level of granularity for the post-processed address that the API can fully validate. For example, a `validation_granularity` of `PREMISE` indicates all address components at the level of `PREMISE` or more coarse can be validated. Per address component validation result can be found in [google.maps.addressvalidation.v1.Address.address_components].
     },
   },
 }</pre>

docs/dyn/admin_reports_v1.activities.html

@@ -122,6 +122,7 @@ <h3>Method Details</h3>
       data_studio - The Data Studio activity reports return information about various types of Data Studio activity events.
       keep - The Keep application&#x27;s activity reports return information about various Google Keep activity events. The Keep activity report is only available for Google Workspace Business and Enterprise customers.
       vault - The Vault activity reports return information about various types of Vault activity events.
+      gemini_in_workspace_apps - The Gemini for Workspace activity reports return information about various types of Gemini activity events performed by users within a Workspace application.
   actorIpAddress: string, The Internet Protocol (IP) Address of host where the event was performed. This is an additional way to filter a report&#x27;s summary using the IP address of the user whose activity is being reported. This IP address may or may not reflect the user&#x27;s physical location. For example, the IP address can be the user&#x27;s proxy server&#x27;s address or a virtual private network (VPN) address. This parameter supports both IPv4 and IPv6 address versions.
   customerId: string, The unique ID of the customer to retrieve data for.
   endTime: string, Sets the end of the range of time shown in the report. The date is in the RFC 3339 format, for example 2010-10-28T10:26:35.000Z. The default value is the approximate time of the API request. An API report has three basic time concepts: - *Date of the API&#x27;s request for a report*: When the API created and retrieved the report. - *Report&#x27;s start time*: The beginning of the timespan shown in the report. The `startTime` must be before the `endTime` (if specified) and the current time when the request is made, or the API returns an error. - *Report&#x27;s end time*: The end of the timespan shown in the report. For example, the timespan of events summarized in a report can start in April and end in May. The report itself can be requested in August. If the `endTime` is not specified, the report returns all activities from the `startTime` until the current time or the most recent 180 days if the `startTime` is more than 180 days in the past.

docs/dyn/adsenseplatform_v1alpha.accounts.platforms.childAccounts.sites.html

@@ -123,7 +123,7 @@ <h3>Method Details</h3>
 Args:
   parent: string, Required. The name of the child account under the given platform which owns the platform child sites. Format: accounts/{account}/platforms/{platform}/childAccounts/{child_account} (required)
   pageSize: integer, Optional. The maximum number of children to include in the response, used for paging. If unspecified, at most 10000 platforms will be returned. The maximum value is 10000; values above 10000 will be coerced to 10000.
-  pageToken: string, Optional. A page token, received from a previous `ListPlatformChildren` call. Provide this to retrieve the subsequent page. When paginating, all other parameters provided to `ListPlatformChildren` must match the call that provided the page token.
+  pageToken: string, Optional. A page token, received from a previous `ListPlatformChildSites` call. Provide this to retrieve the subsequent page. When paginating, all other parameters provided to `ListPlatformChildSites` must match the call that provided the page token.
   x__xgafv: string, V1 error format.
     Allowed values
       1 - v1 error format