Update generated code (#1815)

update generated code

Author: async-aws-bot

manifest.json

@@ -1,6 +1,6 @@
 {
     "variables": {
-        "${LATEST}": "3.334.2"
+        "${LATEST}": "3.334.4"
     },
     "endpoints": "https://raw.githubusercontent.com/aws/aws-sdk-php/${LATEST}/src/data/endpoints.json",
     "services": {

src/Service/CognitoIdentityProvider/CHANGELOG.md

@@ -2,6 +2,10 @@
 
 ## NOT RELEASED
 
+### Changed
+
+- AWS enhancement: Documentation updates.
+
 ## 1.10.0
 
 ### Added

src/Service/CognitoIdentityProvider/src/CognitoIdentityProviderClient.php

@@ -10,7 +10,7 @@
 final class AdminAddUserToGroupRequest extends Input
 {
     /**
-     * The user pool ID for the user pool.
+     * The ID of the user pool that contains the group that you want to add the user to.
      *
      * @required
      *

src/Service/CognitoIdentityProvider/src/Input/AdminAddUserToGroupRequest.php

@@ -13,7 +13,7 @@
 final class AdminConfirmSignUpRequest extends Input
 {
     /**
-     * The user pool ID for which you want to confirm user registration.
+     * The ID of the user pool where you want to confirm a user's sign-up request.
      *
      * @required
      *
@@ -44,13 +44,13 @@ final class AdminConfirmSignUpRequest extends Input
      * For more information, see Customizing user pool Workflows with Lambda Triggers [^1] in the *Amazon Cognito Developer
      * Guide*.
      *
-     * > When you use the ClientMetadata parameter, remember that Amazon Cognito won't do the following:
+     * > When you use the `ClientMetadata` parameter, note that Amazon Cognito won't do the following:
      * >
-     * > - Store the ClientMetadata value. This data is available only to Lambda triggers that are assigned to a user pool
-     * >   to support custom workflows. If your user pool configuration doesn't include triggers, the ClientMetadata
+     * > - Store the `ClientMetadata` value. This data is available only to Lambda triggers that are assigned to a user pool
+     * >   to support custom workflows. If your user pool configuration doesn't include triggers, the `ClientMetadata`
      * >   parameter serves no purpose.
-     * > - Validate the ClientMetadata value.
-     * > - Encrypt the ClientMetadata value. Don't use Amazon Cognito to provide sensitive information.
+     * > - Validate the `ClientMetadata` value.
+     * > - Encrypt the `ClientMetadata` value. Don't send sensitive information in this parameter.
      * >
      *
      * [^1]: https://docs.aws.amazon.com/cognito/latest/developerguide/cognito-user-identity-pools-working-with-aws-lambda-triggers.html

src/Service/CognitoIdentityProvider/src/Input/AdminConfirmSignUpRequest.php

@@ -16,7 +16,7 @@
 final class AdminCreateUserRequest extends Input
 {
     /**
-     * The user pool ID for the user pool where the user will be created.
+     * The ID of the user pool where you want to create a user.
      *
      * @required
      *
@@ -123,9 +123,9 @@ final class AdminCreateUserRequest extends Input
      * This parameter is used only if the `phone_number_verified` or `email_verified` attribute is set to `True`. Otherwise,
      * it is ignored.
      *
-     * If this parameter is set to `True` and the phone number or email address specified in the UserAttributes parameter
-     * already exists as an alias with a different user, the API call will migrate the alias from the previous user to the
-     * newly created user. The previous user will no longer be able to log in using that alias.
+     * If this parameter is set to `True` and the phone number or email address specified in the `UserAttributes` parameter
+     * already exists as an alias with a different user, this request migrates the alias from the previous user to the
+     * newly-created user. The previous user will no longer be able to log in using that alias.
      *
      * If this parameter is set to `False`, the API throws an `AliasExistsException` error if the alias already exists. The
      * default value is `False`.
@@ -135,16 +135,17 @@ final class AdminCreateUserRequest extends Input
     private $forceAliasCreation;
 
     /**
-     * Set to `RESEND` to resend the invitation message to a user that already exists and reset the expiration limit on the
-     * user's account. Set to `SUPPRESS` to suppress sending the message. You can specify only one value.
+     * Set to `RESEND` to resend the invitation message to a user that already exists, and to reset the temporary-password
+     * duration with a new temporary password. Set to `SUPPRESS` to suppress sending the message. You can specify only one
+     * value.
      *
      * @var MessageActionType::*|null
      */
     private $messageAction;
 
     /**
-     * Specify `"EMAIL"` if email will be used to send the welcome message. Specify `"SMS"` if the phone number will be
-     * used. The default value is `"SMS"`. You can specify more than one value.
+     * Specify `EMAIL` if email will be used to send the welcome message. Specify `SMS` if the phone number will be used.
+     * The default value is `SMS`. You can specify more than one value.
      *
      * @var list<DeliveryMediumType::*>|null
      */
@@ -156,20 +157,20 @@ final class AdminCreateUserRequest extends Input
      * You create custom workflows by assigning Lambda functions to user pool triggers. When you use the AdminCreateUser API
      * action, Amazon Cognito invokes the function that is assigned to the *pre sign-up* trigger. When Amazon Cognito
      * invokes this function, it passes a JSON payload, which the function receives as input. This payload contains a
-     * `clientMetadata` attribute, which provides the data that you assigned to the ClientMetadata parameter in your
+     * `ClientMetadata` attribute, which provides the data that you assigned to the ClientMetadata parameter in your
      * AdminCreateUser request. In your function code in Lambda, you can process the `clientMetadata` value to enhance your
      * workflow for your specific needs.
      *
      * For more information, see Customizing user pool Workflows with Lambda Triggers [^1] in the *Amazon Cognito Developer
      * Guide*.
      *
-     * > When you use the ClientMetadata parameter, remember that Amazon Cognito won't do the following:
+     * > When you use the `ClientMetadata` parameter, note that Amazon Cognito won't do the following:
      * >
-     * > - Store the ClientMetadata value. This data is available only to Lambda triggers that are assigned to a user pool
-     * >   to support custom workflows. If your user pool configuration doesn't include triggers, the ClientMetadata
+     * > - Store the `ClientMetadata` value. This data is available only to Lambda triggers that are assigned to a user pool
+     * >   to support custom workflows. If your user pool configuration doesn't include triggers, the `ClientMetadata`
      * >   parameter serves no purpose.
-     * > - Validate the ClientMetadata value.
-     * > - Encrypt the ClientMetadata value. Don't use Amazon Cognito to provide sensitive information.
+     * > - Validate the `ClientMetadata` value.
+     * > - Encrypt the `ClientMetadata` value. Don't send sensitive information in this parameter.
      * >
      *
      * [^1]: https://docs.aws.amazon.com/cognito/latest/developerguide/cognito-user-identity-pools-working-with-aws-lambda-triggers.html

src/Service/CognitoIdentityProvider/src/Input/AdminCreateUserRequest.php

@@ -13,7 +13,7 @@
 final class AdminDeleteUserRequest extends Input
 {
     /**
-     * The user pool ID for the user pool where you want to delete the user.
+     * The ID of the user pool where you want to delete the user.
      *
      * @required
      *

src/Service/CognitoIdentityProvider/src/Input/AdminDeleteUserRequest.php

@@ -13,7 +13,7 @@
 final class AdminDisableUserRequest extends Input
 {
     /**
-     * The user pool ID for the user pool where you want to disable the user.
+     * The ID of the user pool where you want to disable the user.
      *
      * @required
      *

src/Service/CognitoIdentityProvider/src/Input/AdminDisableUserRequest.php

@@ -13,7 +13,7 @@
 final class AdminEnableUserRequest extends Input
 {
     /**
-     * The user pool ID for the user pool where you want to enable the user.
+     * The ID of the user pool where you want to activate sign-in for the user.
      *
      * @required
      *

src/Service/CognitoIdentityProvider/src/Input/AdminEnableUserRequest.php

@@ -13,7 +13,7 @@
 final class AdminGetUserRequest extends Input
 {
     /**
-     * The user pool ID for the user pool where you want to get information about the user.
+     * The ID of the user pool where you want to get information about the user.
      *
      * @required
      *