docs(client-rds): Various documentation improvements.

Author: awstools

clients/client-rds/src/models/models_0.ts

@@ -6014,15 +6014,6 @@ export interface CreateDBInstanceMessage {
    *          </p>
    *         <p>Constraint: The <code>AvailabilityZone</code> parameter can't be specified if the DB instance is a Multi-AZ deployment.
    *             The specified Availability Zone must be in the same Amazon Web Services Region as the current endpoint.</p>
-   *         <note>
-   *             <p>If you're creating a DB instance in an RDS on VMware environment,
-   *                 specify the identifier of the custom Availability Zone to create the DB instance
-   *                 in.</p>
-   *             <p>For more information about RDS on VMware, see the
-   *               <a href="https://docs.aws.amazon.com/AmazonRDS/latest/RDSonVMwareUserGuide/rds-on-vmware.html">
-   *                   RDS on VMware User Guide.</a>
-   *             </p>
-   *         </note>
    */
   AvailabilityZone?: string;
 

codegen/sdk-codegen/aws-models/rds.json

@@ -2579,7 +2579,7 @@
         "AvailabilityZone": {
           "target": "com.amazonaws.rds#String",
           "traits": {
-            "smithy.api#documentation": "<p>The Availability Zone (AZ) where the database will be created. For information on\n        Amazon Web Services Regions and Availability Zones, see \n        <a href=\"https://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/Concepts.RegionsAndAvailabilityZones.html\">Regions\n        and Availability Zones</a>.</p>\n        <p>\n            <b>Amazon Aurora</b>\n         </p>\n        <p>Each Aurora DB cluster hosts copies of its storage in three separate Availability Zones. Specify one of these \n            Availability Zones. Aurora automatically chooses an appropriate Availability Zone if you don't specify one.</p>\n        <p>Default: A random, system-chosen Availability Zone in the endpoint's Amazon Web Services Region.</p>\n        <p>Example: <code>us-east-1d</code>\n         </p>\n        <p>Constraint: The <code>AvailabilityZone</code> parameter can't be specified if the DB instance is a Multi-AZ deployment. \n            The specified Availability Zone must be in the same Amazon Web Services Region as the current endpoint.</p>\n        <note>\n            <p>If you're creating a DB instance in an RDS on VMware environment,\n                specify the identifier of the custom Availability Zone to create the DB instance\n                in.</p>\n            <p>For more information about RDS on VMware, see the \n              <a href=\"https://docs.aws.amazon.com/AmazonRDS/latest/RDSonVMwareUserGuide/rds-on-vmware.html\">\n                  RDS on VMware User Guide.</a>\n            </p>\n        </note>"
+            "smithy.api#documentation": "<p>The Availability Zone (AZ) where the database will be created. For information on\n        Amazon Web Services Regions and Availability Zones, see \n        <a href=\"https://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/Concepts.RegionsAndAvailabilityZones.html\">Regions\n        and Availability Zones</a>.</p>\n        <p>\n            <b>Amazon Aurora</b>\n         </p>\n        <p>Each Aurora DB cluster hosts copies of its storage in three separate Availability Zones. Specify one of these \n            Availability Zones. Aurora automatically chooses an appropriate Availability Zone if you don't specify one.</p>\n        <p>Default: A random, system-chosen Availability Zone in the endpoint's Amazon Web Services Region.</p>\n        <p>Example: <code>us-east-1d</code>\n         </p>\n        <p>Constraint: The <code>AvailabilityZone</code> parameter can't be specified if the DB instance is a Multi-AZ deployment. \n            The specified Availability Zone must be in the same Amazon Web Services Region as the current endpoint.</p>"
           }
         },
         "DBSubnetGroupName": {