Update generated code (#1690)

update generated code

Author: async-aws-bot

src/ValueObject/RollbackConfiguration.php

@@ -42,7 +42,7 @@ final class RollbackConfiguration
      * If you specify a monitoring period but don't specify any rollback triggers, CloudFormation still waits the specified
      * period of time before cleaning up old resources after update operations. You can use this monitoring period to
      * perform any manual stack validation desired, and manually cancel the stack creation or update (using
-     * `CancelUpdateStack` [^1], for example) as necessary.
+     * CancelUpdateStack [^1], for example) as necessary.
      *
      * If you specify 0 for this parameter, CloudFormation still monitors the specified rollback triggers during stack
      * creation and update operations. Then, for update operations, it begins disposing of old resources immediately once

src/ValueObject/RollbackTrigger.php

@@ -21,8 +21,8 @@ final class RollbackTrigger
     private $arn;
 
     /**
-     * The resource type of the rollback trigger. Specify either `AWS::CloudWatch::Alarm` [^1] or
-     * `AWS::CloudWatch::CompositeAlarm` [^2] resource types.
+     * The resource type of the rollback trigger. Specify either AWS::CloudWatch::Alarm [^1] or
+     * AWS::CloudWatch::CompositeAlarm [^2] resource types.
      *
      * [^1]: https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/aws-properties-cw-alarm.html
      * [^2]: https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/aws-resource-cloudwatch-compositealarm.html