@aws-sdk/client-ecs 3.40.0 → 3.41.0

package/dist-types/models/models_0.d.ts

@@ -1,6 +1,6 @@
 import { MetadataBearer as $MetadataBearer, SmithyException as __SmithyException } from "@aws-sdk/types";
 /**
- * <p>You do not have authorization to perform the requested action.</p>
+ * <p>You don't have authorization to perform the requested action.</p>
  */
 export interface AccessDeniedException extends __SmithyException, $MetadataBearer {
     name: "AccessDeniedException";
@@ -22,9 +22,9 @@ export declare enum AgentUpdateStatus {
     UPDATING = "UPDATING"
 }
 /**
- * <p>These errors are usually caused by a client action, such as using an action or
- * 			resource on behalf of a user that doesn't have permissions to use the action or
- * 			resource, or specifying an identifier that is not valid.</p>
+ * <p>These errors are usually caused by a client action. This client action might be using
+ * 			an action or resource on behalf of a user that doesn't have permissions to use the
+ * 			action or resource,. Or, it might be specifying an identifier that isn't valid.</p>
  */
 export interface ClientException extends __SmithyException, $MetadataBearer {
     name: "ClientException";
@@ -44,31 +44,31 @@ export declare enum ManagedScalingStatus {
 /**
  * <p>The managed scaling settings for the Auto Scaling group capacity provider.</p>
  * 		       <p>When managed scaling is enabled, Amazon ECS manages the scale-in and scale-out actions of
- * 			the Auto Scaling group. Amazon ECS manages a target tracking scaling policy using an
- * 			Amazon ECS-managed CloudWatch metric with the specified <code>targetCapacity</code> value as the
- * 			target value for the metric. For more information, see <a href="https://docs.aws.amazon.com/AmazonECS/latest/developerguide/asg-capacity-providers.html#asg-capacity-providers-managed-scaling">Using Managed Scaling</a> in the <i>Amazon Elastic Container Service Developer Guide</i>.</p>
+ * 			the Auto Scaling group. Amazon ECS manages a target tracking scaling policy using an Amazon ECS
+ * 			managed CloudWatch metric with the specified <code>targetCapacity</code> value as the target
+ * 			value for the metric. For more information, see <a href="https://docs.aws.amazon.com/AmazonECS/latest/developerguide/asg-capacity-providers.html#asg-capacity-providers-managed-scaling">Using Managed Scaling</a> in the <i>Amazon Elastic Container Service Developer Guide</i>.</p>
  * 		       <p>If managed scaling is disabled, the user must manage the scaling of the Auto Scaling
  * 			group.</p>
  */
 export interface ManagedScaling {
     /**
-     * <p>Whether or not to enable managed scaling for the capacity provider.</p>
+     * <p>Determines whether to enable managed scaling for the capacity provider.</p>
      */
     status?: ManagedScalingStatus | string;
     /**
      * <p>The target capacity value for the capacity provider. The specified value must be
      * 			greater than <code>0</code> and less than or equal to <code>100</code>. A value of
-     * 				<code>100</code> will result in the Amazon EC2 instances in your Auto Scaling group being
-     * 			completely utilized.</p>
+     * 				<code>100</code> results in the Amazon EC2 instances in your Auto Scaling group being
+     * 			completely used.</p>
      */
     targetCapacity?: number;
     /**
-     * <p>The minimum number of container instances that Amazon ECS will scale in or scale out at one
+     * <p>The minimum number of container instances that Amazon ECS scales in or scales out at one
      * 			time. If this parameter is omitted, the default value of <code>1</code> is used.</p>
      */
     minimumScalingStepSize?: number;
     /**
-     * <p>The maximum number of container instances that Amazon ECS will scale in or scale out at one
+     * <p>The maximum number of container instances that Amazon ECS scales in or scales out at one
      * 			time. If this parameter is omitted, the default value of <code>10000</code> is
      * 			used.</p>
      */
@@ -108,14 +108,14 @@ export interface AutoScalingGroupProvider {
      * 			protection.</p>
      * 		       <important>
      * 			         <p>When using managed termination protection, managed scaling must also be used
-     * 				otherwise managed termination protection will not work.</p>
+     * 				otherwise managed termination protection doesn't work.</p>
      * 		       </important>
      * 		       <p>When managed termination protection is enabled, Amazon ECS prevents the Amazon EC2 instances in
      * 			an Auto Scaling group that contain tasks from being terminated during a scale-in action.
      * 			The Auto Scaling group and each instance in the Auto Scaling group must have instance
      * 			protection from scale-in actions enabled as well. For more information, see <a href="https://docs.aws.amazon.com/autoscaling/ec2/userguide/as-instance-termination.html#instance-protection">Instance Protection</a> in the <i>Auto Scaling User Guide</i>.</p>
-     * 		       <p>When managed termination protection is disabled, your Amazon EC2 instances are not
-     * 			protected from termination when the Auto Scaling group scales in.</p>
+     * 		       <p>When managed termination protection is disabled, your Amazon EC2 instances aren't protected
+     * 			from termination when the Auto Scaling group scales in.</p>
      */
     managedTerminationProtection?: ManagedTerminationProtection | string;
 }
@@ -127,7 +127,7 @@ export declare namespace AutoScalingGroupProvider {
 }
 /**
  * <p>The metadata that you apply to a resource to help you categorize and organize them.
- * 			Each tag consists of a key and an optional value, both of which you define.</p>
+ * 			Each tag consists of a key and an optional value. You define them.</p>
  * 		       <p>The following basic restrictions apply to tags:</p>
  *         <ul>
  *             <li>
@@ -180,9 +180,10 @@ export declare namespace Tag {
 }
 export interface CreateCapacityProviderRequest {
     /**
-     * <p>The name of the capacity provider. Up to 255 characters are allowed, including letters
-     * 			(upper and lowercase), numbers, underscores, and hyphens. The name cannot be prefixed
-     * 			with "<code>aws</code>", "<code>ecs</code>", or "<code>fargate</code>".</p>
+     * <p>The name of the capacity provider. Up to 255 characters are allowed. They include
+     * 			letters (both upper and lowercase letters), numbers, underscores (_), and hyphens (-).
+     * 			The name can't be prefixed with "<code>aws</code>", "<code>ecs</code>", or
+     * 				"<code>fargate</code>".</p>
      */
     name: string | undefined;
     /**
@@ -190,10 +191,10 @@ export interface CreateCapacityProviderRequest {
      */
     autoScalingGroupProvider: AutoScalingGroupProvider | undefined;
     /**
-     * <p>The metadata that you apply to the capacity provider to help you categorize and
-     * 			organize them. Each tag consists of a key and an optional value, both of which you
-     * 			define.</p>
-     *          <p>The following basic restrictions apply to tags:</p>
+     * <p>The metadata that you apply to the capacity provider to categorize and organize them
+     * 			more conveniently. Each tag consists of a key and an optional value. You define both of
+     * 			them.</p>
+     * 		       <p>The following basic restrictions apply to tags:</p>
      *         <ul>
      *             <li>
      *                 <p>Maximum number of tags per resource - 50</p>
@@ -246,7 +247,7 @@ export declare enum CapacityProviderUpdateStatus {
     UPDATE_IN_PROGRESS = "UPDATE_IN_PROGRESS"
 }
 /**
- * <p>The details of a capacity provider.</p>
+ * <p>The details for a capacity provider.</p>
  */
 export interface CapacityProvider {
     /**
@@ -260,7 +261,7 @@ export interface CapacityProvider {
     /**
      * <p>The current status of the capacity provider. Only capacity providers in an
      * 				<code>ACTIVE</code> state can be used in a cluster. When a capacity provider is
-     * 			successfully deleted, it will have an <code>INACTIVE</code> status.</p>
+     * 			successfully deleted, it has an <code>INACTIVE</code> status.</p>
      */
     status?: CapacityProviderStatus | string;
     /**
@@ -269,7 +270,7 @@ export interface CapacityProvider {
     autoScalingGroupProvider?: AutoScalingGroupProvider;
     /**
      * <p>The update status of the capacity provider. The following are the possible states that
-     * 			will be returned.</p>
+     * 			is returned.</p>
      * 		       <dl>
      *             <dt>DELETE_IN_PROGRESS</dt>
      *             <dd>
@@ -277,13 +278,13 @@ export interface CapacityProvider {
      * 				        </dd>
      *             <dt>DELETE_COMPLETE</dt>
      *             <dd>
-     * 					          <p>The capacity provider has been successfully deleted and will have an
+     * 					          <p>The capacity provider was successfully deleted and has an
      * 							<code>INACTIVE</code> status.</p>
      * 				        </dd>
      *             <dt>DELETE_FAILED</dt>
      *             <dd>
-     * 					          <p>The capacity provider was unable to be deleted. The update status reason
-     * 						will provide further details about why the delete failed.</p>
+     * 					          <p>The capacity provider can't be deleted. The update status reason provides
+     * 						further details about why the delete failed.</p>
      * 				        </dd>
      *          </dl>
      */
@@ -295,9 +296,8 @@ export interface CapacityProvider {
     updateStatusReason?: string;
     /**
      * <p>The metadata that you apply to the capacity provider to help you categorize and
-     * 			organize it. Each tag consists of a key and an optional value, both of which you
-     * 			define.</p>
-     *          <p>The following basic restrictions apply to tags:</p>
+     * 			organize it. Each tag consists of a key and an optional value. You define both.</p>
+     * 		       <p>The following basic restrictions apply to tags:</p>
      *         <ul>
      *             <li>
      *                 <p>Maximum number of tags per resource - 50</p>
@@ -350,7 +350,7 @@ export declare namespace CreateCapacityProviderResponse {
     const filterSensitiveLog: (obj: CreateCapacityProviderResponse) => any;
 }
 /**
- * <p>The specified parameter is invalid. Review the available parameters for the API
+ * <p>The specified parameter isn't valid. Review the available parameters for the API
  * 			request.</p>
  */
 export interface InvalidParameterException extends __SmithyException, $MetadataBearer {
@@ -365,7 +365,7 @@ export declare namespace InvalidParameterException {
     const filterSensitiveLog: (obj: InvalidParameterException) => any;
 }
 /**
- * <p>The limit for the resource has been exceeded.</p>
+ * <p>The limit for the resource was exceeded.</p>
  */
 export interface LimitExceededException extends __SmithyException, $MetadataBearer {
     name: "LimitExceededException";
@@ -393,8 +393,8 @@ export declare namespace ServerException {
     const filterSensitiveLog: (obj: ServerException) => any;
 }
 /**
- * <p>There is already a current Amazon ECS container agent update in progress on the specified
- * 			container instance. If the container agent becomes disconnected while it is in a
+ * <p>There's already a current Amazon ECS container agent update in progress on the container
+ * 			instance that's specified. If the container agent becomes disconnected while it's in a
  * 			transitional stage, such as <code>PENDING</code> or <code>STAGING</code>, the update
  * 			process can get stuck in that state. However, when the agent reconnects, it resumes
  * 			where it stopped previously.</p>
@@ -423,7 +423,7 @@ export interface ExecuteCommandLogConfiguration {
      */
     cloudWatchLogGroupName?: string;
     /**
-     * <p>Whether or not to enable encryption on the CloudWatch logs. If not specified,
+     * <p>Determines whether to enable encryption on the CloudWatch logs. If not specified,
      * 			encryption will be disabled.</p>
      */
     cloudWatchEncryptionEnabled?: boolean;
@@ -435,8 +435,8 @@ export interface ExecuteCommandLogConfiguration {
      */
     s3BucketName?: string;
     /**
-     * <p>Whether or not to use encryption on the S3 logs. If not specified,
-     * 			encryption is not used.</p>
+     * <p>Determines whether to use encryption on the S3 logs. If not specified, encryption is
+     * 			not used.</p>
      */
     s3EncryptionEnabled?: boolean;
     /**
@@ -531,7 +531,7 @@ export declare namespace ClusterConfiguration {
  * 				<code>FARGATE_SPOT</code> capacity providers. The Fargate capacity providers are
  * 			available to all accounts and only need to be associated with a cluster to be used in a
  * 			capacity provider strategy.</p>
- *          <p>A capacity provider strategy may contain a maximum of 6 capacity providers.</p>
+ * 		       <p>A capacity provider strategy may contain a maximum of 6 capacity providers.</p>
  */
 export interface CapacityProviderStrategyItem {
     /**
@@ -546,16 +546,16 @@ export interface CapacityProviderStrategyItem {
      * 		       <p>If no <code>weight</code> value is specified, the default value of <code>0</code> is
      * 			used. When multiple capacity providers are specified within a capacity provider
      * 			strategy, at least one of the capacity providers must have a weight value greater than
-     * 			zero and any capacity providers with a weight of <code>0</code> will not be used to
-     * 			place tasks. If you specify multiple capacity providers in a strategy that all have a
-     * 			weight of <code>0</code>, any <code>RunTask</code> or <code>CreateService</code> actions
-     * 			using the capacity provider strategy will fail.</p>
+     * 			zero and any capacity providers with a weight of <code>0</code> can't be used to place
+     * 			tasks. If you specify multiple capacity providers in a strategy that all have a weight
+     * 			of <code>0</code>, any <code>RunTask</code> or <code>CreateService</code> actions using
+     * 			the capacity provider strategy will fail.</p>
      * 		       <p>An example scenario for using weights is defining a strategy that contains two
      * 			capacity providers and both have a weight of <code>1</code>, then when the
      * 				<code>base</code> is satisfied, the tasks will be split evenly across the two
      * 			capacity providers. Using that same logic, if you specify a weight of <code>1</code> for
      * 				<i>capacityProviderA</i> and a weight of <code>4</code> for
-     * 				<i>capacityProviderB</i>, then for every one task that is run using
+     * 				<i>capacityProviderB</i>, then for every one task that's run using
      * 				<i>capacityProviderA</i>, four tasks would use
      * 				<i>capacityProviderB</i>.</p>
      */
@@ -605,13 +605,13 @@ export declare namespace ClusterSetting {
 }
 export interface CreateClusterRequest {
     /**
-     * <p>The name of your cluster. If you do not specify a name for your cluster, you create a
-     * 			cluster named <code>default</code>. Up to 255 letters (uppercase and lowercase), numbers, underscores, and hyphens are allowed. </p>
+     * <p>The name of your cluster. If you don't specify a name for your cluster, you create a
+     * 			cluster that's named <code>default</code>. Up to 255 letters (uppercase and lowercase), numbers, underscores, and hyphens are allowed. </p>
      */
     clusterName?: string;
     /**
      * <p>The metadata that you apply to the cluster to help you categorize and organize them.
-     * 			Each tag consists of a key and an optional value, both of which you define.</p>
+     * 			Each tag consists of a key and an optional value. You define both.</p>
      * 		       <p>The following basic restrictions apply to tags:</p>
      *         <ul>
      *             <li>
@@ -647,13 +647,14 @@ export interface CreateClusterRequest {
     tags?: Tag[];
     /**
      * <p>The setting to use when creating a cluster. This parameter is used to enable CloudWatch
-     * 			Container Insights for a cluster. If this value is specified, it will override the
+     * 			Container Insights for a cluster. If this value is specified, it overrides the
      * 				<code>containerInsights</code> value set with <a>PutAccountSetting</a> or
      * 				<a>PutAccountSettingDefault</a>.</p>
      */
     settings?: ClusterSetting[];
     /**
-     * <p>The execute command configuration for the cluster.</p>
+     * <p>The
+     * 			execute command configuration for the cluster.</p>
      */
     configuration?: ClusterConfiguration;
     /**
@@ -663,8 +664,9 @@ export interface CreateClusterRequest {
      * 			strategy when calling the <a>CreateService</a> or <a>RunTask</a>
      * 			actions.</p>
      * 		       <p>If specifying a capacity provider that uses an Auto Scaling group, the capacity
-     * 			provider must already be created and not already associated with another cluster. New
-     * 			Auto Scaling group capacity providers can be created with the <a>CreateCapacityProvider</a> API operation.</p>
+     * 			provider must be created but not associated with another cluster. New Auto Scaling group
+     * 			capacity providers can be created with the <a>CreateCapacityProvider</a> API
+     * 			operation.</p>
      * 		       <p>To use a Fargate capacity provider, specify either the <code>FARGATE</code> or
      * 				<code>FARGATE_SPOT</code> capacity providers. The Fargate capacity providers are
      * 			available to all accounts and only need to be associated with a cluster to be
@@ -674,13 +676,13 @@ export interface CreateClusterRequest {
      */
     capacityProviders?: string[];
     /**
-     * <p>The capacity provider strategy to set as the default for the cluster. When a default
-     * 			capacity provider strategy is set for a cluster, when calling the <a>RunTask</a> or <a>CreateService</a> APIs with no capacity
+     * <p>The capacity provider strategy to set as the default for the cluster. After a default
+     * 			capacity provider strategy is set for a cluster, when you call the <a>RunTask</a> or <a>CreateService</a> APIs with no capacity
      * 			provider strategy or launch type specified, the default capacity provider strategy for
      * 			the cluster is used.</p>
-     * 		       <p>If a default capacity provider strategy is not defined for a cluster during creation,
-     * 			it can be defined later with the <a>PutClusterCapacityProviders</a> API
-     * 			operation.</p>
+     * 		       <p>If a default capacity provider strategy isn't defined for a cluster when it was
+     * 			created, it can be defined later with the <a>PutClusterCapacityProviders</a>
+     * 			API operation.</p>
      */
     defaultCapacityProviderStrategy?: CapacityProviderStrategyItem[];
 }
@@ -742,7 +744,7 @@ export declare namespace Attachment {
     const filterSensitiveLog: (obj: Attachment) => any;
 }
 /**
- * <p>A regional grouping of one or more container instances on which you can run task
+ * <p>A regional grouping of one or more container instances where you can run task
  * 			requests. Each account receives a default cluster the first time you use the Amazon ECS
  * 			service, but you may also create other clusters. Clusters may contain more than one
  * 			instance type simultaneously.</p>
@@ -761,7 +763,7 @@ export interface Cluster {
      */
     configuration?: ClusterConfiguration;
     /**
-     * <p>The status of the cluster. The following are the possible states that will be
+     * <p>The status of the cluster. The following are the possible states that are
      * 			returned.</p>
      * 		       <dl>
      *             <dt>ACTIVE</dt>
@@ -771,25 +773,25 @@ export interface Cluster {
      * 				        </dd>
      *             <dt>PROVISIONING</dt>
      *             <dd>
-     * 					          <p>The cluster has capacity providers associated with it and the resources
-     * 						needed for the capacity provider are being created.</p>
+     * 					          <p>The cluster has capacity providers that are associated with it and the
+     * 						resources needed for the capacity provider are being created.</p>
      * 				        </dd>
      *             <dt>DEPROVISIONING</dt>
      *             <dd>
-     * 					          <p>The cluster has capacity providers associated with it and the resources
-     * 						needed for the capacity provider are being deleted.</p>
+     * 					          <p>The cluster has capacity providers that are associated with it and the
+     * 						resources needed for the capacity provider are being deleted.</p>
      * 				        </dd>
      *             <dt>FAILED</dt>
      *             <dd>
-     * 					          <p>The cluster has capacity providers associated with it and the resources
-     * 						needed for the capacity provider have failed to create.</p>
+     * 					          <p>The cluster has capacity providers that are associated with it and the
+     * 						resources needed for the capacity provider have failed to create.</p>
      * 				        </dd>
      *             <dt>INACTIVE</dt>
      *             <dd>
      * 					          <p>The cluster has been deleted. Clusters with an <code>INACTIVE</code>
      * 						status may remain discoverable in your account for a period of time.
-     * 						However, this behavior is subject to change in the future, so you should not
-     * 						rely on <code>INACTIVE</code> clusters persisting.</p>
+     * 						However, this behavior is subject to change in the future. We don't
+     * 						recommend that you rely on <code>INACTIVE</code> clusters persisting.</p>
      * 				        </dd>
      *          </dl>
      */
@@ -813,8 +815,8 @@ export interface Cluster {
      */
     activeServicesCount?: number;
     /**
-     * <p>Additional information about your clusters that are separated by launch type,
-     * 			including:</p>
+     * <p>Additional information about your clusters that are separated by launch type. They
+     * 			include the following:</p>
      * 		       <ul>
      *             <li>
      * 				           <p>runningEC2TasksCount</p>
@@ -845,7 +847,7 @@ export interface Cluster {
     statistics?: KeyValuePair[];
     /**
      * <p>The metadata that you apply to the cluster to help you categorize and organize them.
-     * 			Each tag consists of a key and an optional value, both of which you define.</p>
+     * 			Each tag consists of a key and an optional value. You define both.</p>
      * 		       <p>The following basic restrictions apply to tags:</p>
      *         <ul>
      *             <li>
@@ -896,12 +898,12 @@ export interface Cluster {
     defaultCapacityProviderStrategy?: CapacityProviderStrategyItem[];
     /**
      * <p>The resources attached to a cluster. When using a capacity provider with a cluster,
-     * 			the Auto Scaling plan that is created will be returned as a cluster attachment.</p>
+     * 			the Auto Scaling plan that's created is returned as a cluster attachment.</p>
      */
     attachments?: Attachment[];
     /**
      * <p>The status of the capacity providers associated with the cluster. The following are
-     * 			the states that will be returned:</p>
+     * 			the states that are returned.</p>
      * 		       <dl>
      *             <dt>UPDATE_IN_PROGRESS</dt>
      *             <dd>
@@ -939,8 +941,7 @@ export declare namespace CreateClusterResponse {
     const filterSensitiveLog: (obj: CreateClusterResponse) => any;
 }
 /**
- * <p>The specified cluster could not be found. You can view your available clusters with
- * 				<a>ListClusters</a>. Amazon ECS clusters are Region-specific.</p>
+ * <p>The specified cluster wasn't found. You can view your available clusters with <a>ListClusters</a>. Amazon ECS clusters are Region specific.</p>
  */
 export interface ClusterNotFoundException extends __SmithyException, $MetadataBearer {
     name: "ClusterNotFoundException";
@@ -956,7 +957,7 @@ export declare namespace ClusterNotFoundException {
 /**
  * <note>
  * 			         <p>The deployment circuit breaker can only be used for services using the rolling
- * 				update (<code>ECS</code>) deployment type that are not behind a Classic Load Balancer.</p>
+ * 				update (<code>ECS</code>) deployment type that aren't behind a Classic Load Balancer.</p>
  * 		       </note>
  * 		       <p>The <b>deployment circuit breaker</b> determines whether a
  * 			service deployment will fail if the service can't reach a steady state. If enabled, a
@@ -967,13 +968,14 @@ export declare namespace ClusterNotFoundException {
  */
 export interface DeploymentCircuitBreaker {
     /**
-     * <p>Whether to enable the deployment circuit breaker logic for the service.</p>
+     * <p>Determines whether to enable the deployment circuit breaker logic for the
+     * 			service.</p>
      */
     enable: boolean | undefined;
     /**
-     * <p>Whether to enable Amazon ECS to roll back the service if a service deployment fails. If
-     * 			rollback is enabled, when a service deployment fails, the service is rolled back to the
-     * 			last deployment that completed successfully.</p>
+     * <p>Determines whether to enable Amazon ECS to roll back the service if a service deployment
+     * 			fails. If rollback is enabled, when a service deployment fails, the service is rolled
+     * 			back to the last deployment that completed successfully.</p>
      */
     rollback: boolean | undefined;
 }
@@ -1033,10 +1035,10 @@ export interface DeploymentConfiguration {
      * 			if your service has a desired number of four tasks and a minimum healthy percent of 50%,
      * 			the scheduler may stop two existing tasks to free up cluster capacity before starting
      * 			two new tasks. Tasks for services that <i>do not</i> use a load balancer
-     * 			are considered healthy if they are in the <code>RUNNING</code> state; tasks for services
-     * 			that <i>do</i> use a load balancer are considered healthy if they are in
-     * 			the <code>RUNNING</code> state and they are reported as healthy by the load balancer.
-     * 			The default value for minimum healthy percent is 100%.</p>
+     * 			are considered healthy if they're in the <code>RUNNING</code> state; tasks for services
+     * 			that <i>do</i> use a load balancer are considered healthy if they're in
+     * 			the <code>RUNNING</code> state and they're reported as healthy by the load balancer. The
+     * 			default value for minimum healthy percent is 100%.</p>
      * 		       <p>If a service is using the blue/green (<code>CODE_DEPLOY</code>) or
      * 				<code>EXTERNAL</code> deployment types and tasks that use the EC2
      * 			launch type, the <b>minimum healthy percent</b> value is set
@@ -1111,21 +1113,21 @@ export interface LoadBalancer {
     /**
      * <p>The full Amazon Resource Name (ARN) of the Elastic Load Balancing target group or groups associated with a service or
      * 			task set.</p>
-     * 		       <p>A target group ARN is only specified when using an Application Load Balancer or Network Load Balancer. If you are using a
-     * 			Classic Load Balancer the target group ARN should be omitted.</p>
+     * 		       <p>A target group ARN is only specified when using an Application Load Balancer or Network Load Balancer. If you're using a
+     * 			Classic Load Balancer, omit the target group ARN.</p>
      * 		       <p>For services using the <code>ECS</code> deployment controller, you can specify one or
      * 			multiple target groups. For more information, see <a href="https://docs.aws.amazon.com/AmazonECS/latest/developerguide/register-multiple-targetgroups.html">Registering Multiple Target Groups with a Service</a> in
      * 			the <i>Amazon Elastic Container Service Developer Guide</i>.</p>
-     * 		       <p>For services using the <code>CODE_DEPLOY</code> deployment controller, you are
-     * 			required to define two target groups for the load balancer. For more information, see
-     * 				<a href="https://docs.aws.amazon.com/AmazonECS/latest/developerguide/deployment-type-bluegreen.html">Blue/Green Deployment with CodeDeploy</a> in the
+     * 		       <p>For services using the <code>CODE_DEPLOY</code> deployment controller, you're required
+     * 			to define two target groups for the load balancer. For more information, see <a href="https://docs.aws.amazon.com/AmazonECS/latest/developerguide/deployment-type-bluegreen.html">Blue/Green Deployment with CodeDeploy</a> in the
      * 				<i>Amazon Elastic Container Service Developer Guide</i>.</p>
      * 		       <important>
-     * 			         <p>If your service's task definition uses the <code>awsvpc</code> network mode (which
-     * 				is required for the Fargate launch type), you must choose
-     * 					<code>ip</code> as the target type, not <code>instance</code>, when creating
-     * 				your target groups because tasks that use the <code>awsvpc</code> network mode are
-     * 				associated with an elastic network interface, not an Amazon EC2 instance.</p>
+     * 			         <p>If your service's task definition uses the <code>awsvpc</code> network mode, you
+     * 				must choose <code>ip</code> as the target type, not <code>instance</code>. Do this
+     * 				when creating your target groups because tasks that use the <code>awsvpc</code>
+     * 				network mode are associated with an elastic network interface, not an Amazon EC2
+     * 				instance. This network mode is required for the Fargate launch
+     * 				type.</p>
      * 		       </important>
      */
     targetGroupArn?: string;
@@ -1144,7 +1146,7 @@ export interface LoadBalancer {
      * <p>The port on the container to associate with the load balancer. This port must
      * 			correspond to a <code>containerPort</code> in the task definition the tasks in the
      * 			service are using. For tasks that use the EC2 launch type, the container
-     * 			instance they are launched on must allow ingress traffic on the <code>hostPort</code> of
+     * 			instance they're launched on must allow ingress traffic on the <code>hostPort</code> of
      * 			the port mapping.</p>
      */
     containerPort?: number;
@@ -1164,7 +1166,7 @@ export declare enum AssignPublicIp {
  */
 export interface AwsVpcConfiguration {
     /**
-     * <p>The IDs of the subnets associated with the task or service. There is a limit of 16
+     * <p>The IDs of the subnets associated with the task or service. There's a limit of 16
      * 			subnets that can be specified per <code>AwsVpcConfiguration</code>.</p>
      *
      * 		       <note>
@@ -1173,8 +1175,8 @@ export interface AwsVpcConfiguration {
      */
     subnets: string[] | undefined;
     /**
-     * <p>The IDs of the security groups associated with the task or service. If you do not
-     * 			specify a security group, the default security group for the VPC is used. There is a
+     * <p>The IDs of the security groups associated with the task or service. If you don't
+     * 			specify a security group, the default security group for the VPC is used. There's a
      * 			limit of 5 security groups that can be specified per
      * 			<code>AwsVpcConfiguration</code>.</p>
      *
@@ -1200,7 +1202,7 @@ export declare namespace AwsVpcConfiguration {
  */
 export interface NetworkConfiguration {
     /**
-     * <p>The VPC subnets and security groups associated with a task.</p>
+     * <p>The VPC subnets and security groups that are associated with a task.</p>
      * 		       <note>
      * 			         <p>All specified subnets and security groups must be from the same VPC.</p>
      * 		       </note>
@@ -1222,8 +1224,8 @@ export declare enum PlacementConstraintType {
  * 				<a href="https://docs.aws.amazon.com/AmazonECS/latest/developerguide/task-placement-constraints.html">Task Placement Constraints</a> in the
  * 				<i>Amazon Elastic Container Service Developer Guide</i>.</p>
  * 		       <note>
- * 			         <p>If you are using the Fargate launch type, task placement constraints
- * 				are not supported.</p>
+ * 			         <p>If you're using the Fargate launch type, task placement constraints
+ * 				aren't supported.</p>
  * 		       </note>
  */
 export interface PlacementConstraint {
@@ -1263,15 +1265,15 @@ export interface PlacementStrategy {
      * 			places tasks on available candidates. The <code>spread</code> placement strategy spreads
      * 			placement across available candidates evenly based on the <code>field</code> parameter.
      * 			The <code>binpack</code> strategy places tasks on available candidates that have the
-     * 			least available amount of the resource that is specified with the <code>field</code>
+     * 			least available amount of the resource that's specified with the <code>field</code>
      * 			parameter. For example, if you binpack on memory, a task is placed on the instance with
-     * 			the least amount of remaining memory (but still enough to run the task).</p>
+     * 			the least amount of remaining memory but still enough to run the task.</p>
      */
     type?: PlacementStrategyType | string;
     /**
      * <p>The field to apply the placement strategy against. For the <code>spread</code>
      * 			placement strategy, valid values are <code>instanceId</code> (or <code>host</code>,
-     * 			which has the same effect), or any platform or custom attribute that is applied to a
+     * 			which has the same effect), or any platform or custom attribute that's applied to a
      * 			container instance, such as <code>attribute:ecs.availability-zone</code>. For the
      * 				<code>binpack</code> placement strategy, valid values are <code>cpu</code> and
      * 				<code>memory</code>. For the <code>random</code> placement strategy, this field is
@@ -1294,7 +1296,7 @@ export declare enum SchedulingStrategy {
     REPLICA = "REPLICA"
 }
 /**
- * <p>Details of the service registry.</p>
+ * <p>The details for the service registry.</p>
  */
 export interface ServiceRegistry {
     /**
@@ -1304,30 +1306,30 @@ export interface ServiceRegistry {
     registryArn?: string;
     /**
      * <p>The port value used if your service discovery service specified an SRV record. This
-     * 			field may be used if both the <code>awsvpc</code> network mode and SRV records are
+     * 			field might be used if both the <code>awsvpc</code> network mode and SRV records are
      * 			used.</p>
      */
     port?: number;
     /**
-     * <p>The container name value, already specified in the task definition, to be used for
-     * 			your service discovery service. If the task definition that your service task specifies
-     * 			uses the <code>bridge</code> or <code>host</code> network mode, you must specify a
-     * 				<code>containerName</code> and <code>containerPort</code> combination from the task
-     * 			definition. If the task definition that your service task specifies uses the
+     * <p>The container name value to be used for your service discovery service. It's already
+     * 			specified in the task definition. If the task definition that your service task
+     * 			specifies uses the <code>bridge</code> or <code>host</code> network mode, you must
+     * 			specify a <code>containerName</code> and <code>containerPort</code> combination from the
+     * 			task definition. If the task definition that your service task specifies uses the
      * 				<code>awsvpc</code> network mode and a type SRV DNS record is used, you must specify
      * 			either a <code>containerName</code> and <code>containerPort</code> combination or a
-     * 				<code>port</code> value, but not both.</p>
+     * 				<code>port</code> value. However, you can't specify both.</p>
      */
     containerName?: string;
     /**
-     * <p>The port value, already specified in the task definition, to be used for your service
-     * 			discovery service. If the task definition your service task specifies uses the
+     * <p>The port value to be used for your service discovery service. It's already specified
+     * 			in the task definition. If the task definition your service task specifies uses the
      * 				<code>bridge</code> or <code>host</code> network mode, you must specify a
      * 				<code>containerName</code> and <code>containerPort</code> combination from the task
      * 			definition. If the task definition your service task specifies uses the
      * 				<code>awsvpc</code> network mode and a type SRV DNS record is used, you must specify
      * 			either a <code>containerName</code> and <code>containerPort</code> combination or a
-     * 				<code>port</code> value, but not both.</p>
+     * 				<code>port</code> value. However, you can't specify both.</p>
      */
     containerPort?: number;
 }
@@ -1339,7 +1341,7 @@ export declare namespace ServiceRegistry {
 }
 export interface CreateServiceRequest {
     /**
-     * <p>The short name or full Amazon Resource Name (ARN) of the cluster on which to run your service.
+     * <p>The short name or full Amazon Resource Name (ARN) of the cluster that you run your service on.
      * 			If you do not specify a cluster, the default cluster is assumed.</p>
      */
     cluster?: string;
@@ -1351,50 +1353,51 @@ export interface CreateServiceRequest {
     serviceName: string | undefined;
     /**
      * <p>The <code>family</code> and <code>revision</code> (<code>family:revision</code>) or
-     * 			full ARN of the task definition to run in your service. If a <code>revision</code> is
-     * 			not specified, the latest <code>ACTIVE</code> revision is used.</p>
-     * 		       <p>A task definition must be specified if the service is using either the
-     * 				<code>ECS</code> or <code>CODE_DEPLOY</code> deployment controllers.</p>
+     * 			full ARN of the task definition to run in your service. If a <code>revision</code>
+     * 			isn't specified, the latest <code>ACTIVE</code> revision is used.</p>
+     * 		       <p>A task definition must be specified if the service uses either the <code>ECS</code> or
+     * 				<code>CODE_DEPLOY</code> deployment controllers.</p>
      */
     taskDefinition?: string;
     /**
      * <p>A load balancer object representing the load balancers to use with your service. For
      * 			more information, see <a href="https://docs.aws.amazon.com/AmazonECS/latest/developerguide/service-load-balancing.html">Service Load Balancing</a> in the
      * 				<i>Amazon Elastic Container Service Developer Guide</i>.</p>
-     * 		       <p>If the service is using the rolling update (<code>ECS</code>) deployment controller
-     * 			and using either an Application Load Balancer or Network Load Balancer, you must specify one or more target group ARNs to
-     * 			attach to the service. The service-linked role is required for services that make use of
-     * 			multiple target groups. For more information, see <a href="https://docs.aws.amazon.com/AmazonECS/latest/developerguide/using-service-linked-roles.html">Using service-linked roles for Amazon ECS</a> in the
+     * 		       <p>If the service uses the rolling update (<code>ECS</code>) deployment controller and
+     * 			using either an Application Load Balancer or Network Load Balancer, you must specify one or more target group ARNs to attach
+     * 			to the service. The service-linked role is required for services that use multiple
+     * 			target groups. For more information, see <a href="https://docs.aws.amazon.com/AmazonECS/latest/developerguide/using-service-linked-roles.html">Using service-linked roles for Amazon ECS</a> in the
      * 				<i>Amazon Elastic Container Service Developer Guide</i>.</p>
-     * 		       <p>If the service is using the <code>CODE_DEPLOY</code> deployment controller, the
-     * 			service is required to use either an Application Load Balancer or Network Load Balancer. When creating an CodeDeploy deployment
-     * 			group, you specify two target groups (referred to as a <code>targetGroupPair</code>).
-     * 			During a deployment, CodeDeploy determines which task set in your service has the status
-     * 				<code>PRIMARY</code> and associates one target group with it, and then associates
-     * 			the other target group with the replacement task set. The load balancer can also have up
-     * 			to two listeners: a required listener for production traffic and an optional listener
-     * 			that allows you perform validation tests with Lambda functions before routing production
-     * 			traffic to it.</p>
+     * 		       <p>If the service uses the <code>CODE_DEPLOY</code> deployment controller, the service is
+     * 			required to use either an Application Load Balancer or Network Load Balancer. When creating an CodeDeploy deployment group, you
+     * 			specify two target groups (referred to as a <code>targetGroupPair</code>). During a
+     * 			deployment, CodeDeploy determines which task set in your service has the status
+     * 				<code>PRIMARY</code>, and it associates one target group with it. Then, it also
+     * 			associates the other target group with the replacement task set. The load balancer can
+     * 			also have up to two listeners: a required listener for production traffic and an
+     * 			optional listener that you can use to perform validation tests with Lambda functions
+     * 			before routing production traffic to it.</p>
      * 		       <p>After you create a service using the <code>ECS</code> deployment controller, the load
-     * 			balancer name or target group ARN, container name, and container port specified in the
-     * 			service definition are immutable. If you are using the <code>CODE_DEPLOY</code>
+     * 			balancer name or target group ARN, container name, and container port that's specified
+     * 			in the service definition are immutable. If you use the <code>CODE_DEPLOY</code>
      * 			deployment controller, these values can be changed when updating the service.</p>
      * 		       <p>For Application Load Balancers and Network Load Balancers, this object must contain the load balancer target group ARN,
-     * 			the container name (as it appears in a container definition), and the container port to
-     * 			access from the load balancer. The load balancer name parameter must be omitted. When a
-     * 			task from this service is placed on a container instance, the container instance and
-     * 			port combination is registered as a target in the target group specified here.</p>
-     * 		       <p>For Classic Load Balancers, this object must contain the load balancer name, the container name (as it
-     * 			appears in a container definition), and the container port to access from the load
-     * 			balancer. The target group ARN parameter must be omitted. When a task from this service
-     * 			is placed on a container instance, the container instance is registered with the load
-     * 			balancer specified here.</p>
+     * 			the container name, and the container port to access from the load balancer. The
+     * 			container name must be as it appears in a container definition. The load balancer name
+     * 			parameter must be omitted. When a task from this service is placed on a container
+     * 			instance, the container instance and port combination is registered as a target in the
+     * 			target group that's specified here.</p>
+     * 		       <p>For Classic Load Balancers, this object must contain the load balancer name, the container name , and
+     * 			the container port to access from the load balancer. The container name must be as it
+     * 			appears in a container definition. The target group ARN parameter must be omitted. When
+     * 			a task from this service is placed on a container instance, the container instance is
+     * 			registered with the load balancer that's specified here.</p>
      * 		       <p>Services with tasks that use the <code>awsvpc</code> network mode (for example, those
-     * 			with the Fargate launch type) only support Application Load Balancers and Network Load Balancers. Classic Load Balancers are
-     * 			not supported. Also, when you create any target groups for these services, you must
-     * 			choose <code>ip</code> as the target type, not <code>instance</code>, because tasks that
-     * 			use the <code>awsvpc</code> network mode are associated with an elastic network
-     * 			interface, not an Amazon EC2 instance.</p>
+     * 			with the Fargate launch type) only support Application Load Balancers and Network Load Balancers. Classic Load Balancers
+     * 			aren't supported. Also, when you create any target groups for these services, you must
+     * 			choose <code>ip</code> as the target type, not <code>instance</code>. This is because
+     * 			tasks that use the <code>awsvpc</code> network mode are associated with an elastic
+     * 			network interface, not an Amazon EC2 instance.</p>
      */
     loadBalancers?: LoadBalancer[];
     /**
@@ -1403,25 +1406,25 @@ export interface CreateServiceRequest {
      * 				discovery</a>.</p>
      * 		       <note>
      * 			         <p>Each service may be associated with one service registry. Multiple service
-     * 				registries per service isn't supported.</p>
+     * 				registries for each service isn't supported.</p>
      * 		       </note>
      */
     serviceRegistries?: ServiceRegistry[];
     /**
      * <p>The number of instantiations of the specified task definition to place and keep
      * 			running on your cluster.</p>
-     * 		       <p>This is required if <code>schedulingStrategy</code> is <code>REPLICA</code> or is not
-     * 			specified. If <code>schedulingStrategy</code> is <code>DAEMON</code> then this is not
+     * 		       <p>This is required if <code>schedulingStrategy</code> is <code>REPLICA</code> or isn't
+     * 			specified. If <code>schedulingStrategy</code> is <code>DAEMON</code> then this isn't
      * 			required.</p>
      */
     desiredCount?: number;
     /**
-     * <p>Unique, case-sensitive identifier that you provide to ensure the idempotency of the
-     * 			request. Up to 32 ASCII characters are allowed.</p>
+     * <p>An identifier that you provide to ensure the idempotency of the request. It must be
+     * 			unique and is case sensitive. Up to 32 ASCII characters are allowed.</p>
      */
     clientToken?: string;
     /**
-     * <p>The infrastructure on which to run your service. For more information, see <a href="https://docs.aws.amazon.com/AmazonECS/latest/developerguide/launch_types.html">Amazon ECS
+     * <p>The infrastructure that you run your service on. For more information, see <a href="https://docs.aws.amazon.com/AmazonECS/latest/developerguide/launch_types.html">Amazon ECS
      * 				launch types</a> in the <i>Amazon Elastic Container Service Developer Guide</i>.</p>
      * 		       <p>The <code>FARGATE</code> launch type runs your tasks on Fargate On-Demand
      * 			infrastructure.</p>
@@ -1432,7 +1435,7 @@ export interface CreateServiceRequest {
      * 		       </note>
      * 		       <p>The <code>EC2</code> launch type runs your tasks on Amazon EC2 instances registered to your
      * 			cluster.</p>
-     * 		       <p>The <code>EXTERNAL</code> launch type runs your tasks on your on-premise server or
+     * 		       <p>The <code>EXTERNAL</code> launch type runs your tasks on your on-premises server or
      * 			virtual machine (VM) capacity registered to your cluster.</p>
      * 		       <p>A service can use either a launch type or a capacity provider strategy. If a
      * 				<code>launchType</code> is specified, the <code>capacityProviderStrategy</code>
@@ -1451,24 +1454,24 @@ export interface CreateServiceRequest {
     /**
      * <p>The platform version that your tasks in the service are running on. A platform version
      * 			is specified only for tasks using the Fargate launch type. If one isn't
-     * 			specified, the <code>LATEST</code> platform version is used by default. For more
-     * 			information, see <a href="https://docs.aws.amazon.com/AmazonECS/latest/developerguide/platform_versions.html">Fargate platform
+     * 			specified, the <code>LATEST</code> platform version is used. For more information, see
+     * 				<a href="https://docs.aws.amazon.com/AmazonECS/latest/developerguide/platform_versions.html">Fargate platform
      * 				versions</a> in the <i>Amazon Elastic Container Service Developer Guide</i>.</p>
      */
     platformVersion?: string;
     /**
      * <p>The name or full Amazon Resource Name (ARN) of the IAM role that allows Amazon ECS to make calls to your
      * 			load balancer on your behalf. This parameter is only permitted if you are using a load
-     * 			balancer with your service and your task definition does not use the <code>awsvpc</code>
+     * 			balancer with your service and your task definition doesn't use the <code>awsvpc</code>
      * 			network mode. If you specify the <code>role</code> parameter, you must also specify a
      * 			load balancer object with the <code>loadBalancers</code> parameter.</p>
      * 		       <important>
      * 			         <p>If your account has already created the Amazon ECS service-linked role, that role is
-     * 				used by default for your service unless you specify a role here. The service-linked
-     * 				role is required if your task definition uses the <code>awsvpc</code> network mode
-     * 				or if the service is configured to use service discovery, an external deployment
-     * 				controller, multiple target groups, or Elastic Inference accelerators in which case
-     * 				you should not specify a role here. For more information, see <a href="https://docs.aws.amazon.com/AmazonECS/latest/developerguide/using-service-linked-roles.html">Using
+     * 				used for your service unless you specify a role here. The service-linked role is
+     * 				required if your task definition uses the <code>awsvpc</code> network mode or if the
+     * 				service is configured to use service discovery, an external deployment controller,
+     * 				multiple target groups, or Elastic Inference accelerators in which case you don't
+     * 				specify a role here. For more information, see <a href="https://docs.aws.amazon.com/AmazonECS/latest/developerguide/using-service-linked-roles.html">Using
      * 					service-linked roles for Amazon ECS</a> in the
      * 					<i>Amazon Elastic Container Service Developer Guide</i>.</p>
      * 		       </important>
@@ -1486,34 +1489,36 @@ export interface CreateServiceRequest {
     deploymentConfiguration?: DeploymentConfiguration;
     /**
      * <p>An array of placement constraint objects to use for tasks in your service. You can
-     * 			specify a maximum of 10 constraints per task (this limit includes constraints in the
-     * 			task definition and those specified at runtime).</p>
+     * 			specify a maximum of 10 constraints for each task. This limit includes constraints in
+     * 			the task definition and those specified at runtime.</p>
      */
     placementConstraints?: PlacementConstraint[];
     /**
      * <p>The placement strategy objects to use for tasks in your service. You can specify a
-     * 			maximum of 5 strategy rules per service.</p>
+     * 			maximum of 5 strategy rules for each service.</p>
      */
     placementStrategy?: PlacementStrategy[];
     /**
      * <p>The network configuration for the service. This parameter is required for task
      * 			definitions that use the <code>awsvpc</code> network mode to receive their own elastic
-     * 			network interface, and it is not supported for other network modes. For more
-     * 			information, see <a href="https://docs.aws.amazon.com/AmazonECS/latest/developerguide/task-networking.html">Task networking</a>
+     * 			network interface, and it isn't supported for other network modes. For more information,
+     * 			see <a href="https://docs.aws.amazon.com/AmazonECS/latest/developerguide/task-networking.html">Task networking</a>
      * 			in the <i>Amazon Elastic Container Service Developer Guide</i>.</p>
      */
     networkConfiguration?: NetworkConfiguration;
     /**
-     * <p>The period of time, in seconds, that the Amazon ECS service scheduler should ignore
-     * 			unhealthy Elastic Load Balancing target health checks after a task has first started. This is only used
-     * 			when your service is configured to use a load balancer. If your service has a load
-     * 			balancer defined and you don't specify a health check grace period value, the default
-     * 			value of <code>0</code> is used.</p>
+     * <p>The period of time, in seconds, that the Amazon ECS service scheduler ignores unhealthy
+     * 			Elastic Load Balancing target health checks after a task has first started. This is only used when your
+     * 			service is configured to use a load balancer. If your service has a load balancer
+     * 			defined and you don't specify a health check grace period value, the default value of
+     * 				<code>0</code> is used.</p>
      * 		       <p>If your service's tasks take a while to start and respond to Elastic Load Balancing health checks, you
-     * 			can specify a health check grace period of up to 2,147,483,647 seconds. During that
-     * 			time, the Amazon ECS service scheduler ignores health check status. This grace period can
-     * 			prevent the service scheduler from marking tasks as unhealthy and stopping them before
-     * 			they have time to come up.</p>
+     * 			can specify a health check grace period of up to
+     * 			2,147,483,647
+     * 			seconds (about 69 years). During that time, the Amazon ECS service
+     * 			scheduler ignores health check status. This grace period can prevent the service
+     * 			scheduler from marking tasks as unhealthy and stopping them before they have time to
+     * 			come up.</p>
      */
     healthCheckGracePeriodSeconds?: number;
     /**
@@ -1526,9 +1531,8 @@ export interface CreateServiceRequest {
      * 					maintains the desired number of tasks across your cluster. By default, the
      * 					service scheduler spreads tasks across Availability Zones. You can use task
      * 					placement strategies and constraints to customize task placement decisions. This
-     * 					scheduler strategy is required if the service is using the
-     * 						<code>CODE_DEPLOY</code> or <code>EXTERNAL</code> deployment controller
-     * 					types.</p>
+     * 					scheduler strategy is required if the service uses the <code>CODE_DEPLOY</code>
+     * 					or <code>EXTERNAL</code> deployment controller types.</p>
      * 			         </li>
      *             <li>
      * 				           <p>
@@ -1536,7 +1540,7 @@ export interface CreateServiceRequest {
      * 					task on each active container instance that meets all of the task placement
      * 					constraints that you specify in your cluster. The service scheduler also
      * 					evaluates the task placement constraints for running tasks and will stop tasks
-     * 					that do not meet the placement constraints. When you're using this strategy, you
+     * 					that don't meet the placement constraints. When you're using this strategy, you
      * 					don't need to specify a desired number of tasks, a task placement strategy, or
      * 					use Service Auto Scaling policies.</p>
      * 				           <note>
@@ -1557,7 +1561,7 @@ export interface CreateServiceRequest {
      * <p>The metadata that you apply to the service to help you categorize and organize them.
      * 			Each tag consists of a key and an optional value, both of which you define. When a
      * 			service is deleted, the tags are deleted as well.</p>
-     *          <p>The following basic restrictions apply to tags:</p>
+     * 		       <p>The following basic restrictions apply to tags:</p>
      *         <ul>
      *             <li>
      *                 <p>Maximum number of tags per resource - 50</p>
@@ -1598,14 +1602,14 @@ export interface CreateServiceRequest {
     enableECSManagedTags?: boolean;
     /**
      * <p>Specifies whether to propagate the tags from the task definition or the service to the
-     * 			tasks in the service. If no value is specified, the tags are not propagated. Tags can
+     * 			tasks in the service. If no value is specified, the tags aren't propagated. Tags can
      * 			only be propagated to the tasks within the service during service creation. To add tags
-     * 			to a task after service creation or task creation, use the <a>TagResource</a> API
-     * 			action.</p>
+     * 			to a task after service creation or task creation, use the <a>TagResource</a>
+     * 			API action.</p>
      */
     propagateTags?: PropagateTags | string;
     /**
-     * <p>Whether or not the execute command functionality is enabled for the service. If
+     * <p>Determines whether the execute command functionality is enabled for the service. If
      * 				<code>true</code>, this enables execute command functionality on all containers in
      * 			the service tasks.</p>
      */
@@ -1632,7 +1636,7 @@ export interface Deployment {
      */
     id?: string;
     /**
-     * <p>The status of the deployment. The following describes each state:</p>
+     * <p>The status of the deployment. The following describes each state.</p>
      * 		       <dl>
      *             <dt>PRIMARY</dt>
      *             <dd>
@@ -1682,11 +1686,11 @@ export interface Deployment {
      */
     failedTasks?: number;
     /**
-     * <p>The Unix timestamp for when the service deployment was created.</p>
+     * <p>The Unix timestamp for the time when the service deployment was created.</p>
      */
     createdAt?: Date;
     /**
-     * <p>The Unix timestamp for when the service deployment was last updated.</p>
+     * <p>The Unix timestamp for the time when the service deployment was last updated.</p>
      */
     updatedAt?: Date;
     /**
@@ -1699,16 +1703,18 @@ export interface Deployment {
      */
     launchType?: LaunchType | string;
     /**
-     * <p>The platform version on which your tasks in the service are running. A platform
-     * 			version is only specified for tasks using the Fargate launch type. If one
-     * 			is not specified, the <code>LATEST</code> platform version is used by default. For more
-     * 			information, see <a href="https://docs.aws.amazon.com/AmazonECS/latest/developerguide/platform_versions.html">Fargate Platform
-     * 				Versions</a> in the <i>Amazon Elastic Container Service Developer Guide</i>.</p>
+     * <p>The platform version that your tasks in the service run on. A platform version is only
+     * 			specified for tasks using the Fargate launch type. If one isn't specified,
+     * 			the <code>LATEST</code> platform version is used. For more information, see <a href="https://docs.aws.amazon.com/AmazonECS/latest/developerguide/platform_versions.html">Fargate Platform Versions</a> in the
+     * 			<i>Amazon Elastic Container Service Developer Guide</i>.</p>
      */
     platformVersion?: string;
     /**
-     * <p>The operating system  that your tasks in the service, or tasks are running on. A platform family is specified only for tasks using the Fargate launch type. </p>
-     * 		       <p> All tasks that run as part of this service must use the same <code>platformFamily</code> value as the service, for example, <code> LINUX.</code>.</p>
+     * <p>The operating system that your tasks in the service, or tasks are running on. A
+     * 			platform family is specified only for tasks using the Fargate launch type. </p>
+     * 		       <p> All tasks that run as part of this service must use the same
+     * 				<code>platformFamily</code> value as the service, for example, <code>
+     * 			LINUX.</code>.</p>
      */
     platformFamily?: string;
     /**
@@ -1719,15 +1725,15 @@ export interface Deployment {
     /**
      * <note>
      * 			         <p>The <code>rolloutState</code> of a service is only returned for services that use
-     * 				the rolling update (<code>ECS</code>) deployment type that are not behind a
+     * 				the rolling update (<code>ECS</code>) deployment type that aren't behind a
      * 				Classic Load Balancer.</p>
      * 		       </note>
      * 		       <p>The rollout state of the deployment. When a service deployment is started, it begins
      * 			in an <code>IN_PROGRESS</code> state. When the service reaches a steady state, the
-     * 			deployment will transition to a <code>COMPLETED</code> state. If the service fails to
-     * 			reach a steady state and circuit breaker is enabled, the deployment will transition to a
-     * 				<code>FAILED</code> state. A deployment in <code>FAILED</code> state will launch no
-     * 			new tasks. For more information, see <a>DeploymentCircuitBreaker</a>.</p>
+     * 			deployment transitions to a <code>COMPLETED</code> state. If the service fails to reach
+     * 			a steady state and circuit breaker is enabled, the deployment transitions to a
+     * 				<code>FAILED</code> state. A deployment in <code>FAILED</code> state doesn't launch
+     * 			any new tasks. For more information, see <a>DeploymentCircuitBreaker</a>.</p>
      */
     rolloutState?: DeploymentRolloutState | string;
     /**
@@ -1742,15 +1748,15 @@ export declare namespace Deployment {
     const filterSensitiveLog: (obj: Deployment) => any;
 }
 /**
- * <p>Details on an event associated with a service.</p>
+ * <p>The details for an event that's associated with a service.</p>
  */
 export interface ServiceEvent {
     /**
-     * <p>The ID string of the event.</p>
+     * <p>The ID string for the event.</p>
      */
     id?: string;
     /**
-     * <p>The Unix timestamp for when the event was triggered.</p>
+     * <p>The Unix timestamp for the time when the event was triggered.</p>
      */
     createdAt?: Date;
     /**
@@ -1816,14 +1822,14 @@ export interface TaskSet {
      */
     clusterArn?: string;
     /**
-     * <p>The tag specified when a task set is started. If the task set is created by an CodeDeploy
-     * 			deployment, the <code>startedBy</code> parameter is <code>CODE_DEPLOY</code>. For a task
-     * 			set created for an external deployment, the startedBy field isn't used.</p>
+     * <p>The tag specified when a task set is started. If an CodeDeploy deployment created the task
+     * 			set, the <code>startedBy</code> parameter is <code>CODE_DEPLOY</code>. If an external
+     * 			deployment created the task set, the startedBy field isn't used.</p>
      */
     startedBy?: string;
     /**
      * <p>The external ID associated with the task set.</p>
-     * 		       <p>If a task set is created by an CodeDeploy deployment, the <code>externalId</code> parameter
+     * 		       <p>If an CodeDeploy deployment created a task set, the <code>externalId</code> parameter
      * 			contains the CodeDeploy deployment ID.</p>
      * 		       <p>If a task set is created for an external deployment and is associated with a service
      * 			discovery registry, the <code>externalId</code> parameter contains the
@@ -1831,7 +1837,7 @@ export interface TaskSet {
      */
     externalId?: string;
     /**
-     * <p>The status of the task set. The following describes each state:</p>
+     * <p>The status of the task set. The following describes each state.</p>
      * 		       <dl>
      *             <dt>PRIMARY</dt>
      *             <dd>
@@ -1839,18 +1845,18 @@ export interface TaskSet {
      * 				        </dd>
      *             <dt>ACTIVE</dt>
      *             <dd>
-     * 					          <p>The task set is not serving production traffic.</p>
+     * 					          <p>The task set isn't serving production traffic.</p>
      * 				        </dd>
      *             <dt>DRAINING</dt>
      *             <dd>
-     * 					          <p>The tasks in the task set are being stopped and their corresponding
+     * 					          <p>The tasks in the task set are being stopped, and their corresponding
      * 						targets are being deregistered from their target group.</p>
      * 				        </dd>
      *          </dl>
      */
     status?: string;
     /**
-     * <p>The task definition the task set is using.</p>
+     * <p>The task definition that the task set is using.</p>
      */
     taskDefinition?: string;
     /**
@@ -1864,7 +1870,7 @@ export interface TaskSet {
      * <p>The number of tasks in the task set that are in the <code>PENDING</code> status during
      * 			a deployment. A task in the <code>PENDING</code> state is preparing to enter the
      * 				<code>RUNNING</code> state. A task set enters the <code>PENDING</code> status when
-     * 			it launches for the first time or when it is restarted after being in the
+     * 			it launches for the first time or when it's restarted after being in the
      * 				<code>STOPPED</code> state.</p>
      */
     pendingCount?: number;
@@ -1875,11 +1881,11 @@ export interface TaskSet {
      */
     runningCount?: number;
     /**
-     * <p>The Unix timestamp for when the task set was created.</p>
+     * <p>The Unix timestamp for the time when the task set was created.</p>
      */
     createdAt?: Date;
     /**
-     * <p>The Unix timestamp for when the task set was last updated.</p>
+     * <p>The Unix timestamp for the time when the task set was last updated.</p>
      */
     updatedAt?: Date;
     /**
@@ -1888,18 +1894,18 @@ export interface TaskSet {
      */
     launchType?: LaunchType | string;
     /**
-     * <p>The capacity provider strategy associated with the task set.</p>
+     * <p>The capacity provider strategy that are associated with the task set.</p>
      */
     capacityProviderStrategy?: CapacityProviderStrategyItem[];
     /**
-     * <p>The Fargate platform version on which the tasks in the task set are running. A
-     * 			platform version is only specified for tasks run on Fargate. For more information, see
-     * 				<a href="https://docs.aws.amazon.com/AmazonECS/latest/developerguide/platform_versions.html">Fargate platform
-     * 				versions</a> in the <i>Amazon Elastic Container Service Developer Guide</i>.</p>
+     * <p>The Fargate platform version where the tasks in the task set are running. A platform
+     * 			version is only specified for tasks run on Fargate. For more information, see <a href="https://docs.aws.amazon.com/AmazonECS/latest/developerguide/platform_versions.html">Fargate platform versions</a> in the
+     * 			<i>Amazon Elastic Container Service Developer Guide</i>.</p>
      */
     platformVersion?: string;
     /**
-     * <p>The operating system  that your tasks in the set are running on. A platform family is specified only for tasks using the Fargate launch type. </p>
+     * <p>The operating system that your tasks in the set are running on. A platform family is
+     * 			specified only for tasks that use the Fargate launch type. </p>
      * 		       <p> All tasks in the set must have the same value.</p>
      */
     platformFamily?: string;
@@ -1908,23 +1914,23 @@ export interface TaskSet {
      */
     networkConfiguration?: NetworkConfiguration;
     /**
-     * <p>Details on a load balancer that is used with a task set.</p>
+     * <p>Details on a load balancer that are used with a task set.</p>
      */
     loadBalancers?: LoadBalancer[];
     /**
-     * <p>The details of the service discovery registries to assign to this task set. For more
+     * <p>The details for the service discovery registries to assign to this task set. For more
      * 			information, see <a href="https://docs.aws.amazon.com/AmazonECS/latest/developerguide/service-discovery.html">Service
      * 				discovery</a>.</p>
      */
     serviceRegistries?: ServiceRegistry[];
     /**
-     * <p>A floating-point percentage of the desired number of tasks to place and keep running
+     * <p>A floating-point percentage of your desired number of tasks to place and keep running
      * 			in the task set.</p>
      */
     scale?: Scale;
     /**
-     * <p>The stability status, which indicates whether the task set has reached a steady state.
-     * 			If the following conditions are met, the task set will be in
+     * <p>The stability status. This indicates whether the task set has reached a steady state.
+     * 			If the following conditions are met, the task set sre in
      * 			<code>STEADY_STATE</code>:</p>
      * 		       <ul>
      *             <li>
@@ -1935,25 +1941,26 @@ export interface TaskSet {
      * 				           <p>The <code>pendingCount</code> is <code>0</code>.</p>
      * 			         </li>
      *             <li>
-     * 				           <p>There are no tasks running on container instances in the <code>DRAINING</code>
-     * 					status.</p>
+     * 				           <p>There are no tasks that are running on container instances in the
+     * 						<code>DRAINING</code> status.</p>
      * 			         </li>
      *             <li>
      * 				           <p>All tasks are reporting a healthy status from the load balancers, service
      * 					discovery, and container health checks.</p>
      * 			         </li>
      *          </ul>
-     * 		       <p>If any of those conditions are not met, the stability status returns
+     * 		       <p>If any of those conditions aren't met, the stability status returns
      * 				<code>STABILIZING</code>.</p>
      */
     stabilityStatus?: StabilityStatus | string;
     /**
-     * <p>The Unix timestamp for when the task set stability status was retrieved.</p>
+     * <p>The Unix timestamp for the time when the task set stability status was
+     * 			retrieved.</p>
      */
     stabilityStatusAt?: Date;
     /**
      * <p>The metadata that you apply to the task set to help you categorize and organize them.
-     * 			Each tag consists of a key and an optional value, both of which you define.</p>
+     * 			Each tag consists of a key and an optional value. You define both.</p>
      * 		       <p>The following basic restrictions apply to tags:</p>
      *         <ul>
      *             <li>
@@ -2004,7 +2011,7 @@ export interface Service {
     serviceArn?: string;
     /**
      * <p>The name of your service. Up to 255 letters (uppercase and lowercase), numbers, underscores, and hyphens are allowed. Service names must be unique within
-     * 			a cluster, but you can have similarly named services in multiple clusters within a
+     * 			a cluster. However, you can have similarly named services in multiple clusters within a
      * 			Region or across multiple Regions.</p>
      */
     serviceName?: string;
@@ -2013,13 +2020,13 @@ export interface Service {
      */
     clusterArn?: string;
     /**
-     * <p>A list of Elastic Load Balancing load balancer objects, containing the load balancer name, the
-     * 			container name (as it appears in a container definition), and the container port to
-     * 			access from the load balancer.</p>
+     * <p>A list of Elastic Load Balancing load balancer objects. It contains the load balancer name, the
+     * 			container name, and the container port to access from the load balancer. The container
+     * 			name is as it appears in a container definition.</p>
      */
     loadBalancers?: LoadBalancer[];
     /**
-     * <p>The details of the service discovery registries to assign to this service. For more
+     * <p>The details for the service discovery registries to assign to this service. For more
      * 			information, see <a href="https://docs.aws.amazon.com/AmazonECS/latest/developerguide/service-discovery.html">Service
      * 				Discovery</a>.</p>
      */
@@ -2048,21 +2055,23 @@ export interface Service {
      */
     launchType?: LaunchType | string;
     /**
-     * <p>The capacity provider strategy the service is using. When using the DescribeServices
-     * 			API, this field is omitted if the service was created using a launch type.</p>
+     * <p>The capacity provider strategy the service uses. When using the DescribeServices API,
+     * 			this field is omitted if the service was created using a launch type.</p>
      */
     capacityProviderStrategy?: CapacityProviderStrategyItem[];
     /**
-     * <p>The platform version on which to run your service. A platform version is only
-     * 			specified for tasks hosted on Fargate. If one is not specified, the
-     * 				<code>LATEST</code> platform version is used by default. For more information, see
-     * 				<a href="https://docs.aws.amazon.com/AmazonECS/latest/developerguide/platform_versions.html">Fargate Platform
+     * <p>The platform version to run your service on. A platform version is only specified for
+     * 			tasks that are hosted on Fargate. If one isn't specified, the <code>LATEST</code>
+     * 			platform version is used. For more information, see <a href="https://docs.aws.amazon.com/AmazonECS/latest/developerguide/platform_versions.html">Fargate Platform
      * 				Versions</a> in the <i>Amazon Elastic Container Service Developer Guide</i>.</p>
      */
     platformVersion?: string;
     /**
-     * <p>The operating system  that your tasks in the service are running on. A platform family is specified only for tasks using the Fargate launch type. </p>
-     * 		       <p> All tasks that run as part of this service must use the same <code>platformFamily</code> value as the service, for example, <code>LINUX</code>.</p>
+     * <p>The operating system that your tasks in the service run on. A platform family is
+     * 			specified only for tasks using the Fargate launch type. </p>
+     * 		       <p> All tasks that run as part of this service must use the same
+     * 				<code>platformFamily</code> value as the service (for example,
+     * 			<code>LINUX</code>).</p>
      */
     platformFamily?: string;
     /**
@@ -2087,8 +2096,8 @@ export interface Service {
      */
     deployments?: Deployment[];
     /**
-     * <p>The ARN of the IAM role associated with the service that allows the Amazon ECS container
-     * 			agent to register container instances with an Elastic Load Balancing load balancer.</p>
+     * <p>The ARN of the IAM role that's associated with the service. It allows the Amazon ECS
+     * 			container agent to register container instances with an Elastic Load Balancing load balancer.</p>
      */
     roleArn?: string;
     /**
@@ -2097,7 +2106,7 @@ export interface Service {
      */
     events?: ServiceEvent[];
     /**
-     * <p>The Unix timestamp for when the service was created.</p>
+     * <p>The Unix timestamp for the time when the service was created.</p>
      */
     createdAt?: Date;
     /**
@@ -2120,7 +2129,7 @@ export interface Service {
     healthCheckGracePeriodSeconds?: number;
     /**
      * <p>The scheduling strategy to use for the service. For more information, see <a href="https://docs.aws.amazon.com/AmazonECS/latest/developerguide/ecs_services.html">Services</a>.</p>
-     * 		       <p>There are two service scheduler strategies available:</p>
+     * 		       <p>There are two service scheduler strategies available.</p>
      * 		       <ul>
      *             <li>
      * 				           <p>
@@ -2133,12 +2142,14 @@ export interface Service {
      *             <li>
      * 				           <p>
      *                   <code>DAEMON</code>-The daemon scheduling strategy deploys exactly one
-     * 					task on each active container instance that meets all of the task placement
-     * 					constraints that you specify in your cluster. The service scheduler also
-     * 					evaluates the task placement constraints for running tasks and will stop tasks
-     * 					that do not meet the placement constraints.</p>
+     * 					task on each active container
+     * 					instance.
+     * 					This taskmeets all of the task placement constraints that you
+     * 					specify in your cluster. The service scheduler also evaluates the task placement
+     * 					constraints for running tasks. It stop tasks that don't meet the placement
+     * 					constraints.</p>
      * 				           <note>
-     * 					             <p>Fargate tasks do not support the <code>DAEMON</code>
+     * 					             <p>Fargate tasks don't support the <code>DAEMON</code>
      * 						scheduling strategy.</p>
      * 				           </note>
      * 			         </li>
@@ -2147,13 +2158,14 @@ export interface Service {
     schedulingStrategy?: SchedulingStrategy | string;
     /**
      * <p>The deployment controller type the service is using. When using the DescribeServices
-     * 			API, this field is omitted if the service is using the <code>ECS</code> deployment
+     * 			API, this field is omitted if the service uses the <code>ECS</code> deployment
      * 			controller type.</p>
      */
     deploymentController?: DeploymentController;
     /**
      * <p>The metadata that you apply to the service to help you categorize and organize them.
-     * 			Each tag consists of a key and an optional value, both of which you define.</p>
+     * 			Each tag consists of a key and an optional value. You define bot the key and
+     * 			value.</p>
      * 		       <p>The following basic restrictions apply to tags:</p>
      *         <ul>
      *             <li>
@@ -2192,18 +2204,18 @@ export interface Service {
      */
     createdBy?: string;
     /**
-     * <p>Specifies whether to enable Amazon ECS managed tags for the tasks in the service. For more
+     * <p>Determines whether to enable Amazon ECS managed tags for the tasks in the service. For more
      * 			information, see <a href="https://docs.aws.amazon.com/AmazonECS/latest/developerguide/ecs-using-tags.html">Tagging Your Amazon ECS
      * 				Resources</a> in the <i>Amazon Elastic Container Service Developer Guide</i>.</p>
      */
     enableECSManagedTags?: boolean;
     /**
-     * <p>Specifies whether to propagate the tags from the task definition or the service to the
-     * 			task. If no value is specified, the tags are not propagated.</p>
+     * <p>Determines whether to propagate the tags from the task definition or the service to
+     * 			the task. If no value is specified, the tags aren't propagated.</p>
      */
     propagateTags?: PropagateTags | string;
     /**
-     * <p>Whether or not the execute command functionality is enabled for the service. If
+     * <p>Determines whether the execute command functionality is enabled for the service. If
      * 				<code>true</code>, the execute command functionality is enabled for all containers
      * 			in tasks as part of the service.</p>
      */
@@ -2219,12 +2231,12 @@ export interface CreateServiceResponse {
     /**
      * <p>The full description of your service following the create call.</p>
      * 		       <p>A service will return either a <code>capacityProviderStrategy</code> or
-     * 				<code>launchType</code> parameter, but not both, depending on which one was
-     * 			specified during creation.</p>
+     * 				<code>launchType</code> parameter, but not both, depending where one was specified
+     * 			when it was created.</p>
      * 		       <p>If a service is using the <code>ECS</code> deployment controller, the
      * 				<code>deploymentController</code> and <code>taskSets</code> parameters will not be
      * 			returned.</p>
-     * 		       <p>If the service is using the <code>CODE_DEPLOY</code> deployment controller, the
+     * 		       <p>if the service uses the <code>CODE_DEPLOY</code> deployment controller, the
      * 				<code>deploymentController</code>, <code>taskSets</code> and
      * 				<code>deployments</code> parameters will be returned, however the
      * 				<code>deployments</code> parameter will be an empty list.</p>
@@ -2238,8 +2250,8 @@ export declare namespace CreateServiceResponse {
     const filterSensitiveLog: (obj: CreateServiceResponse) => any;
 }
 /**
- * <p>The specified platform version does not satisfy the task definition's required
- * 			capabilities.</p>
+ * <p>The specified platform version doesn't satisfy the required capabilities of the task
+ * 			definition.</p>
  */
 export interface PlatformTaskDefinitionIncompatibilityException extends __SmithyException, $MetadataBearer {
     name: "PlatformTaskDefinitionIncompatibilityException";
@@ -2253,7 +2265,7 @@ export declare namespace PlatformTaskDefinitionIncompatibilityException {
     const filterSensitiveLog: (obj: PlatformTaskDefinitionIncompatibilityException) => any;
 }
 /**
- * <p>The specified platform version does not exist.</p>
+ * <p>The specified platform version doesn't exist.</p>
  */
 export interface PlatformUnknownException extends __SmithyException, $MetadataBearer {
     name: "PlatformUnknownException";
@@ -2267,7 +2279,7 @@ export declare namespace PlatformUnknownException {
     const filterSensitiveLog: (obj: PlatformUnknownException) => any;
 }
 /**
- * <p>The specified task is not supported in this Region.</p>
+ * <p>The specified task isn't supported in this Region.</p>
  */
 export interface UnsupportedFeatureException extends __SmithyException, $MetadataBearer {
     name: "UnsupportedFeatureException";
@@ -2317,8 +2329,8 @@ export interface CreateTaskSetRequest {
      */
     serviceRegistries?: ServiceRegistry[];
     /**
-     * <p>The launch type that new tasks in the task set will use. For more information, see
-     * 				<a href="https://docs.aws.amazon.com/AmazonECS/latest/developerguide/launch_types.html">Amazon ECS Launch Types</a> in the <i>Amazon Elastic Container Service Developer Guide</i>.</p>
+     * <p>The launch type that new tasks in the task set uses. For more information, see <a href="https://docs.aws.amazon.com/AmazonECS/latest/developerguide/launch_types.html">Amazon ECS
+     * 				Launch Types</a> in the <i>Amazon Elastic Container Service Developer Guide</i>.</p>
      * 		       <p>If a <code>launchType</code> is specified, the <code>capacityProviderStrategy</code>
      * 			parameter must be omitted.</p>
      */
@@ -2346,9 +2358,9 @@ export interface CreateTaskSetRequest {
      */
     capacityProviderStrategy?: CapacityProviderStrategyItem[];
     /**
-     * <p>The platform version that the tasks in the task set should use. A platform version is
+     * <p>The platform version that the tasks in the task set uses. A platform version is
      * 			specified only for tasks using the Fargate launch type. If one isn't
-     * 			specified, the <code>LATEST</code> platform version is used by default.</p>
+     * 			specified, the <code>LATEST</code> platform version is used.</p>
      */
     platformVersion?: string;
     /**
@@ -2357,15 +2369,15 @@ export interface CreateTaskSetRequest {
      */
     scale?: Scale;
     /**
-     * <p>Unique, case-sensitive identifier that you provide to ensure the idempotency of the
-     * 			request. Up to 32 ASCII characters are allowed.</p>
+     * <p>The identifier that you provide to ensure the idempotency of the request. It's case
+     * 			sensitive and must be unique. It can be up to 32 ASCII characters are allowed.</p>
      */
     clientToken?: string;
     /**
      * <p>The metadata that you apply to the task set to help you categorize and organize them.
-     * 			Each tag consists of a key and an optional value, both of which you define. When a
-     * 			service is deleted, the tags are deleted as well.</p>
-     *          <p>The following basic restrictions apply to tags:</p>
+     * 			Each tag consists of a key and an optional value. You define both. When a service is
+     * 			deleted, the tags are deleted.</p>
+     * 		       <p>The following basic restrictions apply to tags:</p>
      *         <ul>
      *             <li>
      *                 <p>Maximum number of tags per resource - 50</p>
@@ -2421,8 +2433,8 @@ export declare namespace CreateTaskSetResponse {
     const filterSensitiveLog: (obj: CreateTaskSetResponse) => any;
 }
 /**
- * <p>The specified service is not active. You can't update a service that is inactive. If
- * 			you have previously deleted a service, you can re-create it with <a>CreateService</a>.</p>
+ * <p>The specified service isn't active. You can't update a service that's inactive. If you
+ * 			have previously deleted a service, you can re-create it with <a>CreateService</a>.</p>
  */
 export interface ServiceNotActiveException extends __SmithyException, $MetadataBearer {
     name: "ServiceNotActiveException";
@@ -2436,9 +2448,8 @@ export declare namespace ServiceNotActiveException {
     const filterSensitiveLog: (obj: ServiceNotActiveException) => any;
 }
 /**
- * <p>The specified service could not be found. You can view your available services with
- * 				<a>ListServices</a>. Amazon ECS services are cluster-specific and
- * 			Region-specific.</p>
+ * <p>The specified service wasn't found. You can view your available services with <a>ListServices</a>. Amazon ECS services are cluster specific and Region
+ * 			specific.</p>
  */
 export interface ServiceNotFoundException extends __SmithyException, $MetadataBearer {
     name: "ServiceNotFoundException";
@@ -2460,7 +2471,7 @@ export declare enum SettingName {
 }
 export interface DeleteAccountSettingRequest {
     /**
-     * <p>The resource name for which to disable the account setting. If
+     * <p>The resource name to disable the account setting for. If
      * 				<code>serviceLongArnFormat</code> is specified, the ARN for your Amazon ECS services is
      * 			affected. If <code>taskLongArnFormat</code> is specified, the ARN and resource ID for
      * 			your Amazon ECS tasks is affected. If <code>containerInstanceLongArnFormat</code> is
@@ -2470,11 +2481,11 @@ export interface DeleteAccountSettingRequest {
      */
     name: SettingName | string | undefined;
     /**
-     * <p>The ARN of the principal, which can be an IAM user, IAM role, or the root user. If you
-     * 			specify the root user, it disables the account setting for all IAM users, IAM roles, and
-     * 			the root user of the account unless an IAM user or role explicitly overrides these
-     * 			settings. If this field is omitted, the setting is changed only for the authenticated
-     * 			user.</p>
+     * <p>The Amazon Resource Name (ARN) of the principal. It can be an IAM user, IAM role, or
+     * 			the root user. If you specify the root user, it disables the account setting for all IAM
+     * 			users, IAM roles, and the root user of the account unless an IAM user or role explicitly
+     * 			overrides these settings. If this field is omitted, the setting is changed only for the
+     * 			authenticated user.</p>
      */
     principalArn?: string;
 }
@@ -2493,12 +2504,13 @@ export interface Setting {
      */
     name?: SettingName | string;
     /**
-     * <p>Whether the account setting is enabled or disabled for the specified resource.</p>
+     * <p>Determines whether the account setting is enabled or disabled for the specified
+     * 			resource.</p>
      */
     value?: string;
     /**
-     * <p>The ARN of the principal, which can be an IAM user, IAM role, or the root user. If
-     * 			this field is omitted, the authenticated user is assumed.</p>
+     * <p>The ARN of the principal. It can be an IAM user, IAM role, or the root user. If this
+     * 			field is omitted, the authenticated user is assumed.</p>
      */
     principalArn?: string;
 }
@@ -2524,27 +2536,27 @@ export declare enum TargetType {
     CONTAINER_INSTANCE = "container-instance"
 }
 /**
- * <p>An attribute is a name-value pair associated with an Amazon ECS object. Attributes enable
- * 			you to extend the Amazon ECS data model by adding custom metadata to your resources. For more
- * 			information, see <a href="https://docs.aws.amazon.com/AmazonECS/latest/developerguide/task-placement-constraints.html#attributes">Attributes</a> in the <i>Amazon Elastic Container Service Developer Guide</i>.</p>
+ * <p>An attribute is a name-value pair that's associated with an Amazon ECS object. Attributes
+ * 			enable you to extend the Amazon ECS data model by adding custom metadata to your resources.
+ * 			For more information, see <a href="https://docs.aws.amazon.com/AmazonECS/latest/developerguide/task-placement-constraints.html#attributes">Attributes</a> in the <i>Amazon Elastic Container Service Developer Guide</i>.</p>
  */
 export interface Attribute {
     /**
      * <p>The name of the attribute. The <code>name</code> must contain between 1 and 128
-     * 			characters and name may contain letters (uppercase and lowercase), numbers, hyphens,
-     * 			underscores, forward slashes, back slashes, or periods.</p>
+     * 			characters. The name may contain letters (uppercase and lowercase), numbers, hyphens
+     * 			(-), underscores (_), forward slashes (/), back slashes (\), or periods (.).</p>
      */
     name: string | undefined;
     /**
      * <p>The value of the attribute. The <code>value</code> must contain between 1 and 128
-     * 			characters and may contain letters (uppercase and lowercase), numbers, hyphens,
-     * 			underscores, periods, at signs (@), forward slashes, back slashes, colons, or spaces.
-     * 			The value cannot contain any leading or trailing whitespace.</p>
+     * 			characters. It can contain letters (uppercase and lowercase), numbers, hyphens (-),
+     * 			underscores (_), periods (.), at signs (@), forward slashes (/), back slashes (\),
+     * 			colons (:), or spaces. The value can't can't start or end with a space.</p>
      */
     value?: string;
     /**
-     * <p>The type of the target with which to attach the attribute. This parameter is required
-     * 			if you use the short form ID for a resource instead of the full ARN.</p>
+     * <p>The type of the target to attach the attribute with. This parameter is required if you
+     * 			use the short form ID for a resource instead of the full ARN.</p>
      */
     targetType?: TargetType | string;
     /**
@@ -2566,8 +2578,8 @@ export interface DeleteAttributesRequest {
      */
     cluster?: string;
     /**
-     * <p>The attributes to delete from your resource. You can specify up to 10 attributes per
-     * 			request. For custom attributes, specify the attribute name and target ID, but do not
+     * <p>The attributes to delete from your resource. You can specify up to 10 attributes for
+     * 			each request. For custom attributes, specify the attribute name and target ID, but don't
      * 			specify the value. If you specify the target ID using the short form, you must also
      * 			specify the target type.</p>
      */
@@ -2592,8 +2604,8 @@ export declare namespace DeleteAttributesResponse {
     const filterSensitiveLog: (obj: DeleteAttributesResponse) => any;
 }
 /**
- * <p>The specified target could not be found. You can view your available container
- * 			instances with <a>ListContainerInstances</a>. Amazon ECS container instances are
+ * <p>The specified target wasn't found. You can view your available container instances
+ * 			with <a>ListContainerInstances</a>. Amazon ECS container instances are
  * 			cluster-specific and Region-specific.</p>
  */
 export interface TargetNotFoundException extends __SmithyException, $MetadataBearer {
@@ -2632,7 +2644,7 @@ export declare namespace DeleteCapacityProviderResponse {
     const filterSensitiveLog: (obj: DeleteCapacityProviderResponse) => any;
 }
 /**
- * <p>You cannot delete a cluster that has registered container instances. First, deregister
+ * <p>You can't delete a cluster that has registered container instances. First, deregister
  * 			the container instances before you can delete the cluster. For more information, see
  * 				<a>DeregisterContainerInstance</a>.</p>
  */
@@ -2648,9 +2660,9 @@ export declare namespace ClusterContainsContainerInstancesException {
     const filterSensitiveLog: (obj: ClusterContainsContainerInstancesException) => any;
 }
 /**
- * <p>You cannot delete a cluster that contains services. First, update the service to
- * 			reduce its desired task count to 0 and then delete the service. For more information,
- * 			see <a>UpdateService</a> and <a>DeleteService</a>.</p>
+ * <p>You can't delete a cluster that contains services. First, update the service to reduce
+ * 			its desired task count to 0, and then delete the service. For more information, see
+ * 				<a>UpdateService</a> and <a>DeleteService</a>.</p>
  */
 export interface ClusterContainsServicesException extends __SmithyException, $MetadataBearer {
     name: "ClusterContainsServicesException";
@@ -2664,7 +2676,7 @@ export declare namespace ClusterContainsServicesException {
     const filterSensitiveLog: (obj: ClusterContainsServicesException) => any;
 }
 /**
- * <p>You cannot delete a cluster that has active tasks.</p>
+ * <p>You can't delete a cluster that has active tasks.</p>
  */
 export interface ClusterContainsTasksException extends __SmithyException, $MetadataBearer {
     name: "ClusterContainsTasksException";
@@ -2712,9 +2724,9 @@ export interface DeleteServiceRequest {
      */
     service: string | undefined;
     /**
-     * <p>If <code>true</code>, allows you to delete a service even if it has not been scaled
-     * 			down to zero tasks. It is only necessary to use this if the service is using the
-     * 				<code>REPLICA</code> scheduling strategy.</p>
+     * <p>If <code>true</code>, allows you to delete a service even if it wasn't scaled down to
+     * 			zero tasks. It's only necessary to use this if the service uses the <code>REPLICA</code>
+     * 			scheduling strategy.</p>
      */
     force?: boolean;
 }
@@ -2739,7 +2751,7 @@ export declare namespace DeleteServiceResponse {
 export interface DeleteTaskSetRequest {
     /**
      * <p>The short name or full Amazon Resource Name (ARN) of the cluster that hosts the service that the task
-     * 			set exists in to delete.</p>
+     * 			set found in to delete.</p>
      */
     cluster: string | undefined;
     /**
@@ -2752,8 +2764,8 @@ export interface DeleteTaskSetRequest {
      */
     taskSet: string | undefined;
     /**
-     * <p>If <code>true</code>, this allows you to delete a task set even if it hasn't been
-     * 			scaled down to zero.</p>
+     * <p>If <code>true</code>, you can delete a task set even if it hasn't been scaled down to
+     * 			zero.</p>
      */
     force?: boolean;
 }
@@ -2776,9 +2788,8 @@ export declare namespace DeleteTaskSetResponse {
     const filterSensitiveLog: (obj: DeleteTaskSetResponse) => any;
 }
 /**
- * <p>The specified task set could not be found. You can view your available task sets with
- * 				<a>DescribeTaskSets</a>. Task sets are specific to each cluster, service
- * 			and Region.</p>
+ * <p>The specified task set wasn't found. You can view your available task sets with <a>DescribeTaskSets</a>. Task sets are specific to each cluster, service and
+ * 			Region.</p>
  */
 export interface TaskSetNotFoundException extends __SmithyException, $MetadataBearer {
     name: "TaskSetNotFoundException";
@@ -2803,12 +2814,12 @@ export interface DeregisterContainerInstanceRequest {
      */
     containerInstance: string | undefined;
     /**
-     * <p>Forces the deregistration of the container instance. If you have tasks running on the
+     * <p>Forces the container instance to be deregistered. If you have tasks running on the
      * 			container instance when you deregister it with the <code>force</code> option, these
      * 			tasks remain running until you terminate the instance or the tasks stop through some
-     * 			other means, but they are orphaned (no longer monitored or accounted for by Amazon ECS). If
-     * 			an orphaned task on your container instance is part of an Amazon ECS service, then the
-     * 			service scheduler starts another copy of that task, on a different container instance if
+     * 			other means, but they're orphaned (no longer monitored or accounted for by Amazon ECS). If an
+     * 			orphaned task on your container instance is part of an Amazon ECS service, then the service
+     * 			scheduler starts another copy of that task, on a different container instance if
      * 			possible. </p>
      * 		       <p>Any containers in orphaned service tasks that are registered with a Classic Load Balancer or an Application Load Balancer
      * 			target group are deregistered. They begin connection draining according to the settings
@@ -2822,6 +2833,64 @@ export declare namespace DeregisterContainerInstanceRequest {
      */
     const filterSensitiveLog: (obj: DeregisterContainerInstanceRequest) => any;
 }
+export declare enum InstanceHealthCheckState {
+    IMPAIRED = "IMPAIRED",
+    INITIALIZING = "INITIALIZING",
+    INSUFFICIENT_DATA = "INSUFFICIENT_DATA",
+    OK = "OK"
+}
+export declare enum InstanceHealthCheckType {
+    CONTAINER_RUNTIME = "CONTAINER_RUNTIME"
+}
+/**
+ * <p>An object representing the result of a container instance health status check.</p>
+ */
+export interface InstanceHealthCheckResult {
+    /**
+     * <p>The type of container instance health status that was verified.</p>
+     */
+    type?: InstanceHealthCheckType | string;
+    /**
+     * <p>The container instance health status.</p>
+     */
+    status?: InstanceHealthCheckState | string;
+    /**
+     * <p>The Unix timestamp for when the container instance health status was last
+     * 			updated.</p>
+     */
+    lastUpdated?: Date;
+    /**
+     * <p>The Unix timestamp for when the container instance health status last changed.</p>
+     */
+    lastStatusChange?: Date;
+}
+export declare namespace InstanceHealthCheckResult {
+    /**
+     * @internal
+     */
+    const filterSensitiveLog: (obj: InstanceHealthCheckResult) => any;
+}
+/**
+ * <p>An object representing the health status of the container instance.</p>
+ */
+export interface ContainerInstanceHealthStatus {
+    /**
+     * <p>The overall health status of the container instance. This is an aggregate status of
+     * 			all container instance health checks.</p>
+     */
+    overallStatus?: InstanceHealthCheckState | string;
+    /**
+     * <p>An array of objects representing the details of the container instance health
+     * 			status.</p>
+     */
+    details?: InstanceHealthCheckResult[];
+}
+export declare namespace ContainerInstanceHealthStatus {
+    /**
+     * @internal
+     */
+    const filterSensitiveLog: (obj: ContainerInstanceHealthStatus) => any;
+}
 /**
  * <p>Describes the resources available for a container instance.</p>
  */
@@ -2832,7 +2901,7 @@ export interface Resource {
      */
     name?: string;
     /**
-     * <p>The type of the resource, such as <code>INTEGER</code>, <code>DOUBLE</code>,
+     * <p>The type of the resource. Valid values: <code>INTEGER</code>, <code>DOUBLE</code>,
      * 				<code>LONG</code>, or <code>STRINGSET</code>.</p>
      */
     type?: string;
@@ -2878,7 +2947,7 @@ export interface VersionInfo {
      */
     agentHash?: string;
     /**
-     * <p>The Docker version running on the container instance.</p>
+     * <p>The Docker version that's running on the container instance.</p>
      */
     dockerVersion?: string;
 }
@@ -2889,7 +2958,7 @@ export declare namespace VersionInfo {
     const filterSensitiveLog: (obj: VersionInfo) => any;
 }
 /**
- * <p>An EC2 instance that is running the Amazon ECS agent and has been registered with a
+ * <p>An EC2 instance that's running the Amazon ECS agent and has been registered with a
  * 			cluster.</p>
  */
 export interface ContainerInstance {
@@ -2903,13 +2972,13 @@ export interface ContainerInstance {
      */
     ec2InstanceId?: string;
     /**
-     * <p>The capacity provider associated with the container instance.</p>
+     * <p>The capacity provider that's associated with the container instance.</p>
      */
     capacityProviderName?: string;
     /**
      * <p>The version counter for the container instance. Every time a container instance
      * 			experiences a change that triggers a CloudWatch event, the version counter is
-     * 			incremented. If you are replicating your Amazon ECS container instance state with CloudWatch
+     * 			incremented. If you're replicating your Amazon ECS container instance state with CloudWatch
      * 			Events, you can compare the version of a container instance reported by the Amazon ECS APIs
      * 			with the version reported in CloudWatch Events for the container instance (inside the
      * 				<code>detail</code> object) to verify that the version in your event stream is
@@ -2923,12 +2992,11 @@ export interface ContainerInstance {
     versionInfo?: VersionInfo;
     /**
      * <p>For CPU and memory resource types, this parameter describes the remaining CPU and
-     * 			memory that has not already been allocated to tasks and is therefore available for new
-     * 			tasks. For port resource types, this parameter describes the ports that were reserved by
-     * 			the Amazon ECS container agent (at instance registration time) and any task containers that
-     * 			have reserved port mappings on the host (with the <code>host</code> or
-     * 				<code>bridge</code> network mode). Any port that is not specified here is available
-     * 			for new tasks.</p>
+     * 			memory that wasn't already allocated to tasks and is therefore available for new tasks.
+     * 			For port resource types, this parameter describes the ports that were reserved by the
+     * 			Amazon ECS container agent (at instance registration time) and any task containers that have
+     * 			reserved port mappings on the host (with the <code>host</code> or <code>bridge</code>
+     * 			network mode). Any port that's not specified here is available for new tasks.</p>
      */
     remainingResources?: Resource[];
     /**
@@ -2954,7 +3022,7 @@ export interface ContainerInstance {
      * 			network interface is deprovisioned. The instance then transitions to an
      * 				<code>INACTIVE</code> status.</p>
      * 		       <p>The <code>ACTIVE</code> status indicates that the container instance can accept tasks.
-     * 			The <code>DRAINING</code> indicates that new tasks are not placed on the container
+     * 			The <code>DRAINING</code> indicates that new tasks aren't placed on the container
      * 			instance and any service tasks running on the container instance are removed if
      * 			possible. For more information, see <a href="https://docs.aws.amazon.com/AmazonECS/latest/developerguide/container-instance-draining.html">Container Instance Draining</a> in the
      * 				<i>Amazon Elastic Container Service Developer Guide</i>.</p>
@@ -2982,8 +3050,8 @@ export interface ContainerInstance {
      */
     pendingTasksCount?: number;
     /**
-     * <p>The status of the most recent agent update. If an update has never been requested,
-     * 			this value is <code>NULL</code>.</p>
+     * <p>The status of the most recent agent update. If an update wasn't ever requested, this
+     * 			value is <code>NULL</code>.</p>
      */
     agentUpdateStatus?: AgentUpdateStatus | string;
     /**
@@ -2993,7 +3061,7 @@ export interface ContainerInstance {
      */
     attributes?: Attribute[];
     /**
-     * <p>The Unix timestamp for when the container instance was registered.</p>
+     * <p>The Unix timestamp for the time when the container instance was registered.</p>
      */
     registeredAt?: Date;
     /**
@@ -3003,9 +3071,8 @@ export interface ContainerInstance {
     attachments?: Attachment[];
     /**
      * <p>The metadata that you apply to the container instance to help you categorize and
-     * 			organize them. Each tag consists of a key and an optional value, both of which you
-     * 			define.</p>
-     *          <p>The following basic restrictions apply to tags:</p>
+     * 			organize them. Each tag consists of a key and an optional value. You define both.</p>
+     * 		       <p>The following basic restrictions apply to tags:</p>
      *         <ul>
      *             <li>
      *                 <p>Maximum number of tags per resource - 50</p>
@@ -3038,6 +3105,10 @@ export interface ContainerInstance {
      *          </ul>
      */
     tags?: Tag[];
+    /**
+     * <p>An object representing the health status of the container instance.</p>
+     */
+    healthStatus?: ContainerInstanceHealthStatus;
 }
 export declare namespace ContainerInstance {
     /**
@@ -3090,21 +3161,20 @@ export declare enum ContainerCondition {
  * 			to enable container dependencies. However, we recommend using the latest container agent
  * 			version. For information about checking your agent version and updating to the latest
  * 			version, see <a href="https://docs.aws.amazon.com/AmazonECS/latest/developerguide/ecs-agent-update.html">Updating the Amazon ECS
- * 				Container Agent</a> in the <i>Amazon Elastic Container Service Developer Guide</i>. If you are
- * 			using an Amazon ECS-optimized Linux AMI, your instance needs at least version 1.26.0-1 of the
+ * 				Container Agent</a> in the <i>Amazon Elastic Container Service Developer Guide</i>. If you're using
+ * 			an Amazon ECS-optimized Linux AMI, your instance needs at least version 1.26.0-1 of the
  * 				<code>ecs-init</code> package. If your container instances are launched from version
  * 				<code>20190301</code> or later, then they contain the required versions of the
  * 			container agent and <code>ecs-init</code>. For more information, see <a href="https://docs.aws.amazon.com/AmazonECS/latest/developerguide/ecs-optimized_AMI.html">Amazon ECS-optimized Linux AMI</a> in the <i>Amazon Elastic Container Service Developer Guide</i>.</p>
  * 		       <note>
- * 			         <p>For tasks using the Fargate launch type, the task or service requires the followiwng platforms:</p>
+ * 			         <p>For tasks that use the Fargate launch type, the task or service
+ * 				requires the following platforms:</p>
  * 			         <ul>
  *                <li>
- * 					             <p>Linux platform
- * 						version <code>1.3.0</code> or later.</p>
+ * 					             <p>Linux platform version <code>1.3.0</code> or later.</p>
  * 				           </li>
  *                <li>
- * 					             <p>Windows platform
- * 						version <code>1.0.0</code> or later.</p>
+ * 					             <p>Windows platform version <code>1.0.0</code> or later.</p>
  * 				           </li>
  *             </ul>
  * 		       </note>
@@ -3129,13 +3199,13 @@ export interface ContainerDependency {
      *                   <code>COMPLETE</code> - This condition validates that a dependent
      * 					container runs to completion (exits) before permitting other containers to
      * 					start. This can be useful for nonessential containers that run a script and then
-     * 					exit. This condition cannot be set on an essential container.</p>
+     * 					exit. This condition can't be set on an essential container.</p>
      * 			         </li>
      *             <li>
      * 				           <p>
      *                   <code>SUCCESS</code> - This condition is the same as
      * 						<code>COMPLETE</code>, but it also requires that the container exits with a
-     * 						<code>zero</code> status. This condition cannot be set on an essential
+     * 						<code>zero</code> status. This condition can't be set on an essential
      * 					container.</p>
      * 			         </li>
      *             <li>
@@ -3163,24 +3233,23 @@ export declare enum EnvironmentFileType {
  * 			specify up to ten environment files. The file must have a <code>.env</code> file
  * 			extension. Each line in an environment file should contain an environment variable in
  * 				<code>VARIABLE=VALUE</code> format. Lines beginning with <code>#</code> are treated
- * 			as comments and are ignored. For more information on the environment variable file
+ * 			as comments and are ignored. For more information about the environment variable file
  * 			syntax, see <a href="https://docs.docker.com/compose/env-file/">Declare default
  * 				environment variables in file</a>.</p>
  * 		       <p>If there are environment variables specified using the <code>environment</code>
  * 			parameter in a container definition, they take precedence over the variables contained
  * 			within an environment file. If multiple environment files are specified that contain the
- * 			same variable, they are processed from the top down. It is recommended to use unique
+ * 			same variable, they're processed from the top down. We recommend that you use unique
  * 			variable names. For more information, see <a href="https://docs.aws.amazon.com/AmazonECS/latest/developerguide/taskdef-envfiles.html">Specifying environment
  * 				variables</a> in the <i>Amazon Elastic Container Service Developer Guide</i>.</p>
- * 		       <p>This parameter is only supported for tasks hosted on Fargate using the following platform versions:</p>
+ * 		       <p>This parameter is only supported for tasks hosted on Fargate using the
+ * 			following platform versions:</p>
  * 		       <ul>
  *             <li>
- * 				           <p>Linux platform
- * 					version <code>1.4.0</code> or later.</p>
+ * 				           <p>Linux platform version <code>1.4.0</code> or later.</p>
  * 			         </li>
  *             <li>
- * 				           <p>Windows platform
- * 					version <code>1.0.0</code> or later.</p>
+ * 				           <p>Windows platform version <code>1.0.0</code> or later.</p>
  * 			         </li>
  *          </ul>
  */
@@ -3282,7 +3351,7 @@ export declare namespace FirelensConfiguration {
  *             <li>
  * 				           <p>
  *                   <code>UNKNOWN</code>-The container health check is being evaluated or
- * 					there is no container health check defined.</p>
+ * 					there's no container health check defined.</p>
  * 			         </li>
  *          </ul>
  * 		       <p>The following describes the possible <code>healthStatus</code> values for a task. The
@@ -3318,13 +3387,13 @@ export declare namespace FirelensConfiguration {
  * 						Amazon ECS Container Agent</a>.</p>
  * 			         </li>
  *             <li>
- * 				           <p>Container health checks are supported for Fargate tasks if you
- * 					are using platform version 1.1.0 or greater. For more information, see <a href="https://docs.aws.amazon.com/AmazonECS/latest/developerguide/platform_versions.html">Fargate
+ * 				           <p>Container health checks are supported for Fargate tasks if
+ * 					you're using platform version 1.1.0 or greater. For more information, see <a href="https://docs.aws.amazon.com/AmazonECS/latest/developerguide/platform_versions.html">Fargate
  * 						Platform Versions</a>.</p>
  * 			         </li>
  *             <li>
- * 				           <p>Container health checks are not supported for tasks that are part of a service
- * 					that is configured to use a Classic Load Balancer.</p>
+ * 				           <p>Container health checks aren't supported for tasks that are part of a service
+ * 					that's configured to use a Classic Load Balancer.</p>
  * 			         </li>
  *          </ul>
  */
@@ -3334,11 +3403,12 @@ export interface HealthCheck {
      * 			healthy. The string array must start with <code>CMD</code> to execute the command
      * 			arguments directly, or <code>CMD-SHELL</code> to run the command with the container's
      * 			default shell. </p>
-     * 		       <p> When you use the Amazon Web Services Management Console JSON panel, the Command Line Interface, or the APIs, you should enclose the list of commands in brackets, as shown below.</p>
+     * 		       <p> When you use the Amazon Web Services Management Console JSON panel, the Command Line Interface, or the APIs, enclose the list
+     * 			of commands in brackets.</p>
      * 		       <p>
      * 			         <code>[ "CMD-SHELL", "curl -f http://localhost/ || exit 1" ]</code>
      * 		       </p>
-     * 		       <p>You do not need to include the brackets when you use the Amazon Web Services Management Consoleas shown below.</p>
+     * 		       <p>You don't need to include the brackets when you use the Amazon Web Services Management Console.</p>
      * 		       <p>
      * 			         <code> "CMD-SHELL", "curl -f http://localhost/ || exit 1" </code>
      * 		       </p>
@@ -3364,9 +3434,9 @@ export interface HealthCheck {
      */
     retries?: number;
     /**
-     * <p>The optional grace period within which to provide containers time to bootstrap before
-     * 			failed health checks count towards the maximum number of retries. You may specify
-     * 			between 0 and 300 seconds. The <code>startPeriod</code> is disabled by default.</p>
+     * <p>The optional grace period to provide containers time to bootstrap before failed health
+     * 			checks count towards the maximum number of retries. You can specify between 0 and 300
+     * 			seconds. By default, the <code>startPeriod</code> is disabled.</p>
      * 		       <note>
      * 			         <p>If a health check succeeds within the <code>startPeriod</code>, then the container
      * 				is considered healthy and any subsequent failures count toward the maximum number of
@@ -3383,10 +3453,10 @@ export declare namespace HealthCheck {
 }
 /**
  * <p>The Linux capabilities for the container that are added to or dropped from the default
- * 			configuration provided by Docker. For more information on the default capabilities and
- * 			the non-default available capabilities, see <a href="https://docs.docker.com/engine/reference/run/#runtime-privilege-and-linux-capabilities">Runtime privilege and Linux capabilities</a> in the <i>Docker run
- * 				reference</i>. For more detailed information on these Linux capabilities, see
- * 			the <a href="http://man7.org/linux/man-pages/man7/capabilities.7.html">capabilities(7)</a> Linux manual page.</p>
+ * 			configuration provided by Docker. For more information about the default capabilities
+ * 			and the non-default available capabilities, see <a href="https://docs.docker.com/engine/reference/run/#runtime-privilege-and-linux-capabilities">Runtime privilege and Linux capabilities</a> in the <i>Docker run
+ * 				reference</i>. For more detailed information about these Linux capabilities,
+ * 			see the <a href="http://man7.org/linux/man-pages/man7/capabilities.7.html">capabilities(7)</a> Linux manual page.</p>
  */
 export interface KernelCapabilities {
     /**
@@ -3514,8 +3584,8 @@ export interface LinuxParameters {
      * 				<code>Devices</code> in the <a href="https://docs.docker.com/engine/api/v1.35/#operation/ContainerCreate">Create a container</a> section of the
      * 			<a href="https://docs.docker.com/engine/api/v1.35/">Docker Remote API</a> and the <code>--device</code> option to <a href="https://docs.docker.com/engine/reference/run/#security-configuration">docker run</a>.</p>
      * 		       <note>
-     * 			         <p>If you are using tasks that use the Fargate launch type, the
-     * 					<code>devices</code> parameter is not supported.</p>
+     * 			         <p>If you're using tasks that use the Fargate launch type, the
+     * 					<code>devices</code> parameter isn't supported.</p>
      * 		       </note>
      */
     devices?: Device[];
@@ -3539,8 +3609,8 @@ export interface LinuxParameters {
      * <p>The container path, mount options, and size (in MiB) of the tmpfs mount. This
      * 			parameter maps to the <code>--tmpfs</code> option to <a href="https://docs.docker.com/engine/reference/run/#security-configuration">docker run</a>.</p>
      * 		       <note>
-     * 			         <p>If you are using tasks that use the Fargate launch type, the
-     * 					<code>tmpfs</code> parameter is not supported.</p>
+     * 			         <p>If you're using tasks that use the Fargate launch type, the
+     * 					<code>tmpfs</code> parameter isn't supported.</p>
      * 		       </note>
      */
     tmpfs?: Tmpfs[];
@@ -3554,8 +3624,8 @@ export interface LinuxParameters {
      * 			configuration for the container instance it is running on. A <code>maxSwap</code> value
      * 			must be set for the <code>swappiness</code> parameter to be used.</p>
      * 		       <note>
-     * 			         <p>If you are using tasks that use the Fargate launch type, the
-     * 					<code>maxSwap</code> parameter is not supported.</p>
+     * 			         <p>If you're using tasks that use the Fargate launch type, the
+     * 					<code>maxSwap</code> parameter isn't supported.</p>
      * 		       </note>
      */
     maxSwap?: number;
@@ -3569,8 +3639,8 @@ export interface LinuxParameters {
      * 				<code>maxSwap</code> then this parameter is ignored. This parameter maps to the
      * 				<code>--memory-swappiness</code> option to <a href="https://docs.docker.com/engine/reference/run/#security-configuration">docker run</a>.</p>
      * 		       <note>
-     * 			         <p>If you are using tasks that use the Fargate launch type, the
-     * 					<code>swappiness</code> parameter is not supported.</p>
+     * 			         <p>If you're using tasks that use the Fargate launch type, the
+     * 					<code>swappiness</code> parameter isn't supported.</p>
      * 		       </note>
      */
     swappiness?: number;
@@ -3616,9 +3686,10 @@ export interface Secret {
      * <p>The secret to expose to the container. The supported values are either the full ARN of
      * 			the Secrets Manager secret or the full ARN of the parameter in the SSM Parameter Store.</p>
      * 		       <note>
-     * 			         <p>If the SSM Parameter Store parameter exists in the same Region as the task you
-     * 				are launching, then you can use either the full ARN or name of the parameter. If the
-     * 				parameter exists in a different Region, then the full ARN must be specified.</p>
+     * 			         <p>If the SSM Parameter Store parameter exists in the same Region as the task
+     * 				you're launching, then you can use either the full ARN or name of the parameter. If
+     * 				the parameter exists in a different Region, then the full ARN must be
+     * 				specified.</p>
      * 		       </note>
      */
     valueFrom: string | undefined;
@@ -3636,13 +3707,13 @@ export declare namespace Secret {
  *                <code>docker
  * 					run</code>
  *             </a>.</p>
- * 		       <p>By default, containers use the same logging driver that the Docker daemon uses;
- * 			however the container may use a different logging driver than the Docker daemon by
+ * 		       <p>By default, containers use the same logging driver that the Docker daemon uses.
+ * 			However, the container might use a different logging driver than the Docker daemon by
  * 			specifying a log driver configuration in the container definition. For more information
- * 			on the options for different supported log drivers, see <a href="https://docs.docker.com/engine/admin/logging/overview/">Configure logging
+ * 			about the options for different supported log drivers, see <a href="https://docs.docker.com/engine/admin/logging/overview/">Configure logging
  * 				drivers</a> in the Docker documentation.</p>
- * 		       <p>The following should be noted when specifying a log configuration for your
- * 			containers:</p>
+ * 		       <p>Understand the following when specifying a log configuration for your
+ * 			containers.</p>
  * 		       <ul>
  *             <li>
  * 				           <p>Amazon ECS currently supports a subset of the logging drivers available to the
@@ -3654,17 +3725,17 @@ export declare namespace Secret {
  * 					your container instance.</p>
  * 			         </li>
  *             <li>
- * 				           <p>For tasks hosted on Amazon EC2 instances, the Amazon ECS container agent must register
- * 					the available logging drivers with the
+ * 				           <p>For tasks that are hosted on Amazon EC2 instances, the Amazon ECS container agent must
+ * 					register the available logging drivers with the
  * 						<code>ECS_AVAILABLE_LOGGING_DRIVERS</code> environment variable before
  * 					containers placed on that instance can use these log configuration options. For
  * 					more information, see <a href="https://docs.aws.amazon.com/AmazonECS/latest/developerguide/ecs-agent-config.html">Amazon ECS container agent configuration</a> in the
  * 						<i>Amazon Elastic Container Service Developer Guide</i>.</p>
  * 			         </li>
  *             <li>
- * 				           <p>For tasks on Fargate, because you do not have access to the underlying
- * 					infrastructure your tasks are hosted on, any additional software needed will
- * 					have to be installed outside of the task. For example, the Fluentd output
+ * 				           <p>For tasks that are on Fargate, because you don't have access to the
+ * 					underlying infrastructure your tasks are hosted on, any additional software
+ * 					needed must be installed outside of the task. For example, the Fluentd output
  * 					aggregators or a remote host running Logstash to send Gelf logs to.</p>
  * 			         </li>
  *          </ul>
@@ -3683,12 +3754,11 @@ export interface LogConfiguration {
      * 				the awslogs log driver</a> in the <i>Amazon Elastic Container Service Developer Guide</i>.</p>
      * 		       <p>For more information about using the <code>awsfirelens</code> log driver, see <a href="https://docs.aws.amazon.com/AmazonECS/latest/developerguide/using_firelens.html">Custom log routing</a> in the <i>Amazon Elastic Container Service Developer Guide</i>.</p>
      * 		       <note>
-     * 			         <p>If you have a custom driver that is not listed, you can fork the Amazon ECS container
-     * 				agent project that is <a href="https://github.com/aws/amazon-ecs-agent">available
+     * 			         <p>If you have a custom driver that isn't listed, you can fork the Amazon ECS container
+     * 				agent project that's <a href="https://github.com/aws/amazon-ecs-agent">available
      * 					on GitHub</a> and customize it to work with that driver. We encourage you to
      * 				submit pull requests for changes that you would like to have included. However, we
-     * 				do not currently provide support for running modified copies of this
-     * 				software.</p>
+     * 				don't currently provide support for running modified copies of this software.</p>
      * 		       </note>
      */
     logDriver: LogDriver | string | undefined;
@@ -3712,7 +3782,7 @@ export declare namespace LogConfiguration {
     const filterSensitiveLog: (obj: LogConfiguration) => any;
 }
 /**
- * <p>Details on a volume mount point that is used in a container definition.</p>
+ * <p>Details for a volume mount point that's used in a container definition.</p>
  */
 export interface MountPoint {
     /**
@@ -3745,13 +3815,13 @@ export declare enum TransportProtocol {
  * <p>Port mappings allow containers to access ports on the host container instance to send
  * 			or receive traffic. Port mappings are specified as part of the container
  * 			definition.</p>
- * 		       <p>If you are using containers in a task with the <code>awsvpc</code> or
- * 				<code>host</code> network mode, exposed ports should be specified using
- * 				<code>containerPort</code>. The <code>hostPort</code> can be left blank or it must
- * 			be the same value as the <code>containerPort</code>.</p>
+ * 		       <p>If you use containers in a task with the <code>awsvpc</code> or <code>host</code>
+ * 			network mode, specify the exposed ports using <code>containerPort</code>. The
+ * 				<code>hostPort</code> can be left blank or it must be the same value as the
+ * 				<code>containerPort</code>.</p>
  * 		       <note>
- * 			         <p>You cannot expose the same container port for multiple protocols. An error will be
- * 				returned if this is attempted</p>
+ * 			         <p>You can't expose the same container port for multiple protocols. If you attempt
+ * 				this, an error is returned.</p>
  * 		       </note>
  * 		       <p>After a task reaches the <code>RUNNING</code> status, manual and automatic host and
  * 			container port assignments are visible in the <code>networkBindings</code> section of
@@ -3759,26 +3829,25 @@ export declare enum TransportProtocol {
  */
 export interface PortMapping {
     /**
-     * <p>The port number on the container that is bound to the user-specified or automatically
+     * <p>The port number on the container that's bound to the user-specified or automatically
      * 			assigned host port.</p>
-     * 		       <p>If you are using containers in a task with the <code>awsvpc</code> or
-     * 				<code>host</code> network mode, exposed ports should be specified using
-     * 				<code>containerPort</code>.</p>
-     * 		       <p>If you are using containers in a task with the <code>bridge</code> network mode and
-     * 			you specify a container port and not a host port, your container automatically receives
-     * 			a host port in the ephemeral port range. For more information, see
-     * 			<code>hostPort</code>. Port mappings that are automatically assigned in this way do not
-     * 			count toward the 100 reserved ports limit of a container instance.</p>
+     * 		       <p>If you use containers in a task with the <code>awsvpc</code> or <code>host</code>
+     * 			network mode, specify the exposed ports using <code>containerPort</code>.</p>
+     * 		       <p>If you use containers in a task with the <code>bridge</code> network mode and you
+     * 			specify a container port and not a host port, your container automatically receives a
+     * 			host port in the ephemeral port range. For more information, see <code>hostPort</code>.
+     * 			Port mappings that are automatically assigned in this way do not count toward the 100
+     * 			reserved ports limit of a container instance.</p>
      */
     containerPort?: number;
     /**
      * <p>The port number on the container instance to reserve for your container.</p>
-     * 		       <p>If you are using containers in a task with the <code>awsvpc</code> or
-     * 				<code>host</code> network mode, the <code>hostPort</code> can either be left blank
-     * 			or set to the same value as the <code>containerPort</code>.</p>
-     * 		       <p>If you are using containers in a task with the <code>bridge</code> network mode, you
-     * 			can specify a non-reserved host port for your container port mapping, or you can omit
-     * 			the <code>hostPort</code> (or set it to <code>0</code>) while specifying a
+     * 		       <p>If you use containers in a task with the <code>awsvpc</code> or <code>host</code>
+     * 			network mode, the <code>hostPort</code> can either be left blank or set to the same
+     * 			value as the <code>containerPort</code>.</p>
+     * 		       <p>If you use containers in a task with the <code>bridge</code> network mode, you can
+     * 			specify a non-reserved host port for your container port mapping, or you can omit the
+     * 				<code>hostPort</code> (or set it to <code>0</code>) while specifying a
      * 				<code>containerPort</code> and your container automatically receives a port in the
      * 			ephemeral port range for your container instance operating system and Docker
      * 			version.</p>
@@ -3794,12 +3863,12 @@ export interface PortMapping {
      * 		       </note>
      * 		       <p>The default reserved ports are 22 for SSH, the Docker ports 2375 and 2376, and the
      * 			Amazon ECS container agent ports 51678-51680. Any host port that was previously specified in
-     * 			a running task is also reserved while the task is running (after a task stops, the host
-     * 			port is released). The current reserved ports are displayed in the
+     * 			a running task is also reserved while the task is running. That is, after a task stops,
+     * 			the host port is released. The current reserved ports are displayed in the
      * 				<code>remainingResources</code> of <a>DescribeContainerInstances</a>
-     * 			output. A container instance can have up to 100 reserved ports at a time, including the
-     * 			default reserved ports. Automatically assigned ports don't count toward the 100 reserved
-     * 			ports limit.</p>
+     * 			output. A container instance can have up to 100 reserved ports at a time. This number
+     * 			includes the default reserved ports. Automatically assigned ports aren't included in the
+     * 			100 reserved ports quota.</p>
      */
     hostPort?: number;
     /**
@@ -3822,10 +3891,10 @@ export interface RepositoryCredentials {
      * <p>The Amazon Resource Name (ARN) of the secret containing the private repository
      * 			credentials.</p>
      * 		       <note>
-     * 			         <p>When you are using the Amazon ECS API, CLI, or Amazon Web Services SDK, if the secret exists in the
-     * 				same Region as the task that you are launching then you can use either the full ARN
-     * 				or the name of the secret. When you are using the Amazon Web Services Management Console, you must specify the
-     * 				full ARN of the secret.</p>
+     * 			         <p>When you use the Amazon ECS API, CLI, or Amazon Web Services SDK, if the secret exists in the same
+     * 				Region as the task that you're launching then you can use either the full ARN or the
+     * 				name of the secret. When you use the Amazon Web Services Management Console, you must specify the full ARN of the
+     * 				secret.</p>
      * 		       </note>
      */
     credentialsParameter: string | undefined;
@@ -3843,7 +3912,8 @@ export declare enum ResourceType {
 /**
  * <p>The type and amount of a resource to assign to a container. The supported resource
  * 			types are GPUs and Elastic Inference accelerators. For more information, see <a href="https://docs.aws.amazon.com/AmazonECS/latest/developerguide/ecs-gpu.html">Working with
- * 				GPUs on Amazon ECS</a> or <a href="https://docs.aws.amazon.com/AmazonECS/latest/developerguide/ecs-inference.html">Working with Amazon Elastic Inference on Amazon ECS</a> in the
+ * 				GPUs on Amazon ECS</a> or <a href="https://docs.aws.amazon.com/AmazonECS/latest/developerguide/ecs-inference.html">Working with
+ * 				Amazon Elastic Inference on Amazon ECS</a> in the
  * 				<i>Amazon Elastic Container Service Developer Guide</i>
  *          </p>
  */
@@ -3851,12 +3921,12 @@ export interface ResourceRequirement {
     /**
      * <p>The value for the specified resource type.</p>
      * 		       <p>If the <code>GPU</code> type is used, the value is the number of physical
-     * 				<code>GPUs</code> the Amazon ECS container agent will reserve for the container. The
-     * 			number of GPUs reserved for all containers in a task should not exceed the number of
-     * 			available GPUs on the container instance the task is launched on.</p>
-     * 		       <p>If the <code>InferenceAccelerator</code> type is used, the <code>value</code> should
-     * 			match the <code>deviceName</code> for an <a>InferenceAccelerator</a>
-     * 			specified in a task definition.</p>
+     * 				<code>GPUs</code> the Amazon ECS container agent reserves for the container. The number
+     * 			of GPUs that's reserved for all containers in a task can't exceed the number of
+     * 			available GPUs on the container instance that the task is launched on.</p>
+     * 		       <p>If the <code>InferenceAccelerator</code> type is used, the <code>value</code> matches
+     * 			the <code>deviceName</code> for an <a>InferenceAccelerator</a> specified in a
+     * 			task definition.</p>
      */
     value: string | undefined;
     /**
@@ -3875,34 +3945,34 @@ export declare namespace ResourceRequirement {
  * <p>A list of namespaced kernel parameters to set in the container. This parameter maps to
  * 				<code>Sysctls</code> in the <a href="https://docs.docker.com/engine/api/v1.35/#operation/ContainerCreate">Create a container</a> section of the
  * 			<a href="https://docs.docker.com/engine/api/v1.35/">Docker Remote API</a> and the <code>--sysctl</code> option to <a href="https://docs.docker.com/engine/reference/run/#security-configuration">docker run</a>.</p>
- * 		       <p>It is not recommended that you specify network-related <code>systemControls</code>
- * 			parameters for multiple containers in a single task that also uses either the
- * 				<code>awsvpc</code> or <code>host</code> network mode for the following
- * 			reasons:</p>
+ * 		       <p>We don't recommend that you specify network-related <code>systemControls</code>
+ * 			parameters for multiple containers in a single task. This task also uses either the
+ * 				<code>awsvpc</code> or <code>host</code> network mode. It does it for the following
+ * 			reasons.</p>
  * 		       <ul>
  *             <li>
  * 				           <p>For tasks that use the <code>awsvpc</code> network mode, if you set
  * 						<code>systemControls</code> for any container, it applies to all containers
  * 					in the task. If you set different <code>systemControls</code> for multiple
- * 					containers in a single task, the container that is started last determines which
+ * 					containers in a single task, the container that's started last determines which
  * 						<code>systemControls</code> take effect.</p>
  * 			         </li>
  *             <li>
  * 				           <p>For tasks that use the <code>host</code> network mode, the
  * 						<code>systemControls</code> parameter applies to the container instance's
- * 					kernel parameter as well as that of all containers of any tasks running on that
+ * 					kernel parameter and that of all containers of any tasks running on that
  * 					container instance.</p>
  * 			         </li>
  *          </ul>
  */
 export interface SystemControl {
     /**
-     * <p>The namespaced kernel parameter for which to set a <code>value</code>.</p>
+     * <p>The namespaced kernel parameter to set a <code>value</code> for.</p>
      */
     namespace?: string;
     /**
-     * <p>The value for the namespaced kernel parameter specified in
-     * 			<code>namespace</code>.</p>
+     * <p>The value for the namespaced kernel parameter that's specified in
+     * 				<code>namespace</code>.</p>
      */
     value?: string;
 }
@@ -3964,8 +4034,8 @@ export declare namespace Ulimit {
  */
 export interface VolumeFrom {
     /**
-     * <p>The name of another container within the same task definition from which to mount
-     * 			volumes.</p>
+     * <p>The name of another container within the same task definition to mount volumes
+     * 			from.</p>
      */
     sourceContainer?: string;
     /**
@@ -3987,7 +4057,7 @@ export declare namespace VolumeFrom {
  */
 export interface ContainerDefinition {
     /**
-     * <p>The name of a container. If you are linking multiple containers together in a task
+     * <p>The name of a container. If you're linking multiple containers together in a task
      * 			definition, the <code>name</code> of one container can be entered in the
      * 				<code>links</code> of another container to connect the containers.
      * 			Up to 255 letters (uppercase and lowercase), numbers, underscores, and hyphens are allowed. This parameter maps to <code>name</code> in the
@@ -3998,7 +4068,7 @@ export interface ContainerDefinition {
     name?: string;
     /**
      * <p>The image used to start a container. This string is passed directly to the Docker
-     * 			daemon. Images in the Docker Hub registry are available by default. Other repositories
+     * 			daemon. By default, images in the Docker Hub registry are available. Other repositories
      * 			are specified with either <code>
      * 				           <i>repository-url</i>/<i>image</i>:<i>tag</i>
      * 			         </code> or <code>
@@ -4011,8 +4081,7 @@ export interface ContainerDefinition {
      *             <li>
      * 				           <p>When a new task starts, the Amazon ECS container agent pulls the latest version of
      * 					the specified image and tag for the container to use. However, subsequent
-     * 					updates to a repository image are not propagated to already running
-     * 					tasks.</p>
+     * 					updates to a repository image aren't propagated to already running tasks.</p>
      * 			         </li>
      *             <li>
      * 				           <p>Images in Amazon ECR repositories can be specified by either using the full
@@ -4057,17 +4126,17 @@ export interface ContainerDefinition {
      * 		       <p>Linux containers share unallocated CPU units with other containers on the container
      * 			instance with the same ratio as their allocated amount. For example, if you run a
      * 			single-container task on a single-core instance type with 512 CPU units specified for
-     * 			that container, and that is the only task running on the container instance, that
+     * 			that container, and that's the only task running on the container instance, that
      * 			container could use the full 1,024 CPU unit share at any given time. However, if you
-     * 			launched another copy of the same task on that container instance, each task would be
-     * 			guaranteed a minimum of 512 CPU units when needed, and each container could float to
-     * 			higher CPU usage if the other container was not using it, but if both tasks were 100%
+     * 			launched another copy of the same task on that container instance, each task is
+     * 			guaranteed a minimum of 512 CPU units when needed. Moreover, each container could float
+     * 			to higher CPU usage if the other container was not using it. If both tasks were 100%
      * 			active all of the time, they would be limited to 512 CPU units.</p>
      * 		       <p>On Linux container instances, the Docker daemon on the container instance uses the CPU
      * 			value to calculate the relative CPU share ratios for running containers. For more
      * 			information, see <a href="https://docs.docker.com/engine/reference/run/#cpu-share-constraint">CPU share
      * 				constraint</a> in the Docker documentation. The minimum valid CPU share value
-     * 			that the Linux kernel allows is 2. However, the CPU parameter is not required, and you
+     * 			that the Linux kernel allows is 2. However, the CPU parameter isn't required, and you
      * 			can use CPU values below 2 in your container definitions. For CPU values below 2
      * 			(including null), the behavior varies based on your Amazon ECS container agent
      * 			version:</p>
@@ -4086,7 +4155,7 @@ export interface ContainerDefinition {
      * 			         </li>
      *          </ul>
      * 		       <p>On Windows container instances, the CPU limit is enforced as an absolute limit, or a
-     * 			quota. Windows containers only have access to the specified amount of CPU that is
+     * 			quota. Windows containers only have access to the specified amount of CPU that's
      * 			described in the task definition. A null or zero CPU value is passed to Docker as
      * 				<code>0</code>, which Windows interprets as 1% of one CPU.</p>
      */
@@ -4104,10 +4173,10 @@ export interface ContainerDefinition {
      * 				<code>memory</code> and <code>memoryReservation</code> value, <code>memory</code>
      * 			must be greater than <code>memoryReservation</code>. If you specify
      * 				<code>memoryReservation</code>, then that value is subtracted from the available
-     * 			memory resources for the container instance on which the container is placed. Otherwise,
+     * 			memory resources for the container instance where the container is placed. Otherwise,
      * 			the value of <code>memory</code> is used.</p>
-     * 		       <p>The Docker daemon reserves a minimum of 4 MiB of memory for a container, so you should
-     * 			not specify fewer than 4 MiB of memory for your containers.</p>
+     * 		       <p>The Docker daemon reserves a minimum of 4 MiB of memory for a container. Therefore, we
+     * 			recommend that you specify fewer than 4 MiB of memory for your containers.</p>
      */
     memory?: number;
     /**
@@ -4123,7 +4192,7 @@ export interface ContainerDefinition {
      * 			definition. If you specify both, <code>memory</code> must be greater than
      * 				<code>memoryReservation</code>. If you specify <code>memoryReservation</code>, then
      * 			that value is subtracted from the available memory resources for the container instance
-     * 			on which the container is placed. Otherwise, the value of <code>memory</code> is
+     * 			where the container is placed. Otherwise, the value of <code>memory</code> is
      * 			used.</p>
      * 		       <p>For example, if your container normally uses 128 MiB of memory, but occasionally
      * 			bursts to 256 MiB of memory for short periods of time, you can set a
@@ -4131,8 +4200,8 @@ export interface ContainerDefinition {
      * 			300 MiB. This configuration would allow the container to only reserve 128 MiB of memory
      * 			from the remaining resources on the container instance, but also allow the container to
      * 			consume more memory resources when needed.</p>
-     * 		       <p>The Docker daemon reserves a minimum of 4 MiB of memory for a container, so you should
-     * 			not specify fewer than 4 MiB of memory for your containers. </p>
+     * 		       <p>The Docker daemon reserves a minimum of 4 MiB of memory for a container. Therefore, we
+     * 			recommend that you specify fewer than 4 MiB of memory for your containers. </p>
      */
     memoryReservation?: number;
     /**
@@ -4146,10 +4215,10 @@ export interface ContainerDefinition {
      * 			<a href="https://docs.docker.com/engine/api/v1.35/#operation/ContainerCreate">Create a container</a> section of the <a href="https://docs.docker.com/engine/api/v1.35/">Docker Remote API</a> and the
      * 				<code>--link</code> option to <a href="https://docs.docker.com/engine/reference/run/#security-configuration">docker
      * 			run</a>.</p>
-     *          <note>
+     * 		       <note>
      *                         <p>This parameter is not supported for Windows containers.</p>
      *                      </note>
-     *          <important>
+     * 		       <important>
      * 			         <p>Containers that are collocated on a single container instance may be able to
      * 				communicate with each other without requiring links or host port mappings. Network
      * 				isolation is achieved on the container instance using security groups and VPC
@@ -4160,12 +4229,12 @@ export interface ContainerDefinition {
     /**
      * <p>The list of port mappings for the container. Port mappings allow containers to access
      * 			ports on the host container instance to send or receive traffic.</p>
-     * 		       <p>For task definitions that use the <code>awsvpc</code> network mode, you should only
-     * 			specify the <code>containerPort</code>. The <code>hostPort</code> can be left blank or
-     * 			it must be the same value as the <code>containerPort</code>.</p>
+     * 		       <p>For task definitions that use the <code>awsvpc</code> network mode, only specify the
+     * 				<code>containerPort</code>. The <code>hostPort</code> can be left blank or it must
+     * 			be the same value as the <code>containerPort</code>.</p>
      * 		       <p>Port mappings on Windows use the <code>NetNAT</code> gateway address rather than
-     * 				<code>localhost</code>. There is no loopback for port mappings on Windows, so you
-     * 			cannot access a container's mapped port from the host itself. </p>
+     * 				<code>localhost</code>. There's no loopback for port mappings on Windows, so you
+     * 			can't access a container's mapped port from the host itself. </p>
      * 		       <p>This parameter maps to <code>PortBindings</code> in the
      * 			<a href="https://docs.docker.com/engine/api/v1.35/#operation/ContainerCreate">Create a container</a> section of the <a href="https://docs.docker.com/engine/api/v1.35/">Docker Remote API</a> and the
      * 				<code>--publish</code> option to <a href="https://docs.docker.com/engine/reference/run/#security-configuration">docker
@@ -4187,33 +4256,33 @@ export interface ContainerDefinition {
      * <p>If the <code>essential</code> parameter of a container is marked as <code>true</code>,
      * 			and that container fails or stops for any reason, all other containers that are part of
      * 			the task are stopped. If the <code>essential</code> parameter of a container is marked
-     * 			as <code>false</code>, then its failure does not affect the rest of the containers in a
-     * 			task. If this parameter is omitted, a container is assumed to be essential.</p>
-     * 		       <p>All tasks must have at least one essential container. If you have an application that
-     * 			is composed of multiple containers, you should group containers that are used for a
-     * 			common purpose into components, and separate the different components into multiple task
+     * 			as <code>false</code>, its failure doesn't affect the rest of the containers in a task.
+     * 			If this parameter is omitted, a container is assumed to be essential.</p>
+     * 		       <p>All tasks must have at least one essential container. If you have an application
+     * 			that's composed of multiple containers, group containers that are used for a common
+     * 			purpose into components, and separate the different components into multiple task
      * 			definitions. For more information, see <a href="https://docs.aws.amazon.com/AmazonECS/latest/developerguide/application_architecture.html">Application
      * 				Architecture</a> in the <i>Amazon Elastic Container Service Developer Guide</i>.</p>
      */
     essential?: boolean;
     /**
      * <important>
-     * 			         <p>Early versions of the Amazon ECS container agent do not properly handle
+     * 			         <p>Early versions of the Amazon ECS container agent don't properly handle
      * 					<code>entryPoint</code> parameters. If you have problems using
      * 					<code>entryPoint</code>, update your container agent or enter your commands and
      * 				arguments as <code>command</code> array items instead.</p>
      * 		       </important>
-     * 		       <p>The entry point that is passed to the container. This parameter maps to
+     * 		       <p>The entry point that's passed to the container. This parameter maps to
      * 				<code>Entrypoint</code> in the <a href="https://docs.docker.com/engine/api/v1.35/#operation/ContainerCreate">Create a container</a> section of the
      * 			<a href="https://docs.docker.com/engine/api/v1.35/">Docker Remote API</a> and the <code>--entrypoint</code> option to <a href="https://docs.docker.com/engine/reference/run/#security-configuration">docker run</a>. For more information, see <a href="https://docs.docker.com/engine/reference/builder/#entrypoint">https://docs.docker.com/engine/reference/builder/#entrypoint</a>.</p>
      */
     entryPoint?: string[];
     /**
-     * <p>The command that is passed to the container. This parameter maps to <code>Cmd</code>
-     * 			in the <a href="https://docs.docker.com/engine/api/v1.35/#operation/ContainerCreate">Create a container</a> section of the <a href="https://docs.docker.com/engine/api/v1.35/">Docker Remote API</a> and the
+     * <p>The command that's passed to the container. This parameter maps to <code>Cmd</code> in
+     * 			the <a href="https://docs.docker.com/engine/api/v1.35/#operation/ContainerCreate">Create a container</a> section of the <a href="https://docs.docker.com/engine/api/v1.35/">Docker Remote API</a> and the
      * 				<code>COMMAND</code> parameter to <a href="https://docs.docker.com/engine/reference/run/#security-configuration">docker
      * 				run</a>. For more information, see <a href="https://docs.docker.com/engine/reference/builder/#cmd">https://docs.docker.com/engine/reference/builder/#cmd</a>. If there are multiple arguments, each
-     * 			argument should be a separated string in the array.</p>
+     * 			argument is a separated string in the array.</p>
      */
     command?: string[];
     /**
@@ -4221,7 +4290,7 @@ export interface ContainerDefinition {
      * 				<code>Env</code> in the <a href="https://docs.docker.com/engine/api/v1.35/#operation/ContainerCreate">Create a container</a> section of the
      * 			<a href="https://docs.docker.com/engine/api/v1.35/">Docker Remote API</a> and the <code>--env</code> option to <a href="https://docs.docker.com/engine/reference/run/#security-configuration">docker run</a>.</p>
      * 		       <important>
-     * 			         <p>We do not recommend using plaintext environment variables for sensitive
+     * 			         <p>We don't recommend that you use plaintext environment variables for sensitive
      * 				information, such as credential data.</p>
      * 		       </important>
      */
@@ -4230,15 +4299,15 @@ export interface ContainerDefinition {
      * <p>A list of files containing the environment variables to pass to a container. This
      * 			parameter maps to the <code>--env-file</code> option to <a href="https://docs.docker.com/engine/reference/run/#security-configuration">docker run</a>.</p>
      * 		       <p>You can specify up to ten environment files. The file must have a <code>.env</code>
-     * 			file extension. Each line in an environment file should contain an environment variable
-     * 			in <code>VARIABLE=VALUE</code> format. Lines beginning with <code>#</code> are treated
-     * 			as comments and are ignored. For more information on the environment variable file
+     * 			file extension. Each line in an environment file contains an environment variable in
+     * 				<code>VARIABLE=VALUE</code> format. Lines beginning with <code>#</code> are treated
+     * 			as comments and are ignored. For more information about the environment variable file
      * 			syntax, see <a href="https://docs.docker.com/compose/env-file/">Declare default
      * 				environment variables in file</a>.</p>
      * 		       <p>If there are environment variables specified using the <code>environment</code>
      * 			parameter in a container definition, they take precedence over the variables contained
      * 			within an environment file. If multiple environment files are specified that contain the
-     * 			same variable, they are processed from the top down. It is recommended to use unique
+     * 			same variable, they're processed from the top down. We recommend that you use unique
      * 			variable names. For more information, see <a href="https://docs.aws.amazon.com/AmazonECS/latest/developerguide/taskdef-envfiles.html">Specifying Environment
      * 				Variables</a> in the <i>Amazon Elastic Container Service Developer Guide</i>.</p>
      */
@@ -4248,8 +4317,8 @@ export interface ContainerDefinition {
      * 		       <p>This parameter maps to <code>Volumes</code> in the <a href="https://docs.docker.com/engine/api/v1.35/#operation/ContainerCreate">Create a container</a>
      * 			section of the <a href="https://docs.docker.com/engine/api/v1.35/">Docker Remote API</a> and the <code>--volume</code> option to <a href="https://docs.docker.com/engine/reference/run/#security-configuration">docker run</a>.</p>
      * 		       <p>Windows containers can mount whole directories on the same drive as
-     * 				<code>$env:ProgramData</code>. Windows containers cannot mount directories on a
-     * 			different drive, and mount point cannot be across drives.</p>
+     * 				<code>$env:ProgramData</code>. Windows containers can't mount directories on a
+     * 			different drive, and mount point can't be across drives.</p>
      */
     mountPoints?: MountPoint[];
     /**
@@ -4279,20 +4348,19 @@ export interface ContainerDefinition {
      * 			least version 1.26.0 of the container agent to enable container dependencies. However,
      * 			we recommend using the latest container agent version. For information about checking
      * 			your agent version and updating to the latest version, see <a href="https://docs.aws.amazon.com/AmazonECS/latest/developerguide/ecs-agent-update.html">Updating the Amazon ECS
-     * 				Container Agent</a> in the <i>Amazon Elastic Container Service Developer Guide</i>. If you are
-     * 			using an Amazon ECS-optimized Linux AMI, your instance needs at least version 1.26.0-1 of the
+     * 				Container Agent</a> in the <i>Amazon Elastic Container Service Developer Guide</i>. If you're using
+     * 			an Amazon ECS-optimized Linux AMI, your instance needs at least version 1.26.0-1 of the
      * 				<code>ecs-init</code> package. If your container instances are launched from version
      * 				<code>20190301</code> or later, then they contain the required versions of the
      * 			container agent and <code>ecs-init</code>. For more information, see <a href="https://docs.aws.amazon.com/AmazonECS/latest/developerguide/ecs-optimized_AMI.html">Amazon ECS-optimized Linux AMI</a> in the <i>Amazon Elastic Container Service Developer Guide</i>.</p>
-     * 		       <p>For tasks using the Fargate launch type, the task or service requires the followiwng platforms:</p>
+     * 		       <p>For tasks using the Fargate launch type, the task or service requires
+     * 			the following platforms:</p>
      * 		       <ul>
      *             <li>
-     * 				           <p>Linux platform
-     * 					version <code>1.3.0</code> or later.</p>
+     * 				           <p>Linux platform version <code>1.3.0</code> or later.</p>
      * 			         </li>
      *             <li>
-     * 				           <p>Windows platform
-     * 					version <code>1.0.0</code> or later.</p>
+     * 				           <p>Windows platform version <code>1.0.0</code> or later.</p>
      * 			         </li>
      *          </ul>
      */
@@ -4302,22 +4370,21 @@ export interface ContainerDefinition {
      * 			container. For example, you specify two containers in a task definition with containerA
      * 			having a dependency on containerB reaching a <code>COMPLETE</code>,
      * 			<code>SUCCESS</code>, or <code>HEALTHY</code> status. If a <code>startTimeout</code>
-     * 			value is specified for containerB and it does not reach the desired status within that
-     * 			time then containerA will give up and not start. This results in the task transitioning
-     * 			to a <code>STOPPED</code> state.</p>
+     * 			value is specified for containerB and it doesn't reach the desired status within that
+     * 			time then containerA gives up and not start. This results in the task transitioning to a
+     * 				<code>STOPPED</code> state.</p>
      * 		       <note>
      * 			         <p>When the <code>ECS_CONTAINER_START_TIMEOUT</code> container agent configuration
-     * 				variable is used, it is enforced indendently from this start timeout value.</p>
+     * 				variable is used, it's enforced independently from this start timeout value.</p>
      * 		       </note>
-     * 		       <p>For tasks using the Fargate launch type, the task or service requires the followiwng platforms:</p>
+     * 		       <p>For tasks using the Fargate launch type, the task or service requires
+     * 			the following platforms:</p>
      * 		       <ul>
      *             <li>
-     * 				           <p>Linux platform
-     * 					version <code>1.3.0</code> or later.</p>
+     * 				           <p>Linux platform version <code>1.3.0</code> or later.</p>
      * 			         </li>
      *             <li>
-     * 				           <p>Windows platform
-     * 					version <code>1.0.0</code> or later.</p>
+     * 				           <p>Windows platform version <code>1.0.0</code> or later.</p>
      * 			         </li>
      *          </ul>
      * 		       <p>For tasks using the EC2 launch type, your container instances require at
@@ -4325,9 +4392,9 @@ export interface ContainerDefinition {
      * 			timeout value. However, we recommend using the latest container agent version. For
      * 			information about checking your agent version and updating to the latest version, see
      * 				<a href="https://docs.aws.amazon.com/AmazonECS/latest/developerguide/ecs-agent-update.html">Updating the Amazon ECS
-     * 				Container Agent</a> in the <i>Amazon Elastic Container Service Developer Guide</i>. If you are
-     * 			using an Amazon ECS-optimized Linux AMI, your instance needs at least version <code>1.26.0-1</code> of
-     * 			the <code>ecs-init</code> package. If your container instances are launched from version
+     * 				Container Agent</a> in the <i>Amazon Elastic Container Service Developer Guide</i>. If you're using
+     * 			an Amazon ECS-optimized Linux AMI, your instance needs at least version <code>1.26.0-1</code> of the
+     * 				<code>ecs-init</code> package. If your container instances are launched from version
      * 				<code>20190301</code> or later, then they contain the required versions of the
      * 			container agent and <code>ecs-init</code>. For more information, see <a href="https://docs.aws.amazon.com/AmazonECS/latest/developerguide/ecs-optimized_AMI.html">Amazon ECS-optimized Linux AMI</a> in the <i>Amazon Elastic Container Service Developer Guide</i>.</p>
      */
@@ -4335,22 +4402,21 @@ export interface ContainerDefinition {
     /**
      * <p>Time duration (in seconds) to wait before the container is forcefully killed if it
      * 			doesn't exit normally on its own.</p>
-     * 		       <p>For tasks using the Fargate launch type, the task or service requires the followiwng platforms:</p>
+     * 		       <p>For tasks using the Fargate launch type, the task or service requires
+     * 			the following platforms:</p>
      * 		       <ul>
      *             <li>
-     * 				           <p>Linux platform
-     * 					version <code>1.3.0</code> or later.</p>
+     * 				           <p>Linux platform version <code>1.3.0</code> or later.</p>
      * 			         </li>
      *             <li>
-     * 				           <p>Windows platform
-     * 					version <code>1.0.0</code> or later.</p>
+     * 				           <p>Windows platform version <code>1.0.0</code> or later.</p>
      * 			         </li>
      *          </ul>
-     * 		       <p>The max stop timeout value is 120 seconds and if the
-     * 			parameter is not specified, the default value of 30 seconds is used.</p>
-     * 		       <p>For tasks using the EC2 launch type, if the <code>stopTimeout</code>
-     * 			parameter is not specified, the value set for the Amazon ECS container agent configuration
-     * 			variable <code>ECS_CONTAINER_STOP_TIMEOUT</code> is used by default. If neither the
+     * 		       <p>The max stop timeout value is 120 seconds and if the parameter is not specified, the
+     * 			default value of 30 seconds is used.</p>
+     * 		       <p>For tasks that use the EC2 launch type, if the <code>stopTimeout</code>
+     * 			parameter isn't specified, the value set for the Amazon ECS container agent configuration
+     * 			variable <code>ECS_CONTAINER_STOP_TIMEOUT</code> is used. If neither the
      * 				<code>stopTimeout</code> parameter or the <code>ECS_CONTAINER_STOP_TIMEOUT</code>
      * 			agent configuration variable are set, then the default values of 30 seconds for Linux
      * 			containers and 30 seconds on Windows containers are used. Your container instances
@@ -4358,8 +4424,8 @@ export interface ContainerDefinition {
      * 			timeout value. However, we recommend using the latest container agent version. For
      * 			information about checking your agent version and updating to the latest version, see
      * 				<a href="https://docs.aws.amazon.com/AmazonECS/latest/developerguide/ecs-agent-update.html">Updating the Amazon ECS
-     * 				Container Agent</a> in the <i>Amazon Elastic Container Service Developer Guide</i>. If you are
-     * 			using an Amazon ECS-optimized Linux AMI, your instance needs at least version 1.26.0-1 of the
+     * 				Container Agent</a> in the <i>Amazon Elastic Container Service Developer Guide</i>. If you're using
+     * 			an Amazon ECS-optimized Linux AMI, your instance needs at least version 1.26.0-1 of the
      * 				<code>ecs-init</code> package. If your container instances are launched from version
      * 				<code>20190301</code> or later, then they contain the required versions of the
      * 			container agent and <code>ecs-init</code>. For more information, see <a href="https://docs.aws.amazon.com/AmazonECS/latest/developerguide/ecs-optimized_AMI.html">Amazon ECS-optimized Linux AMI</a> in the <i>Amazon Elastic Container Service Developer Guide</i>.</p>
@@ -4371,7 +4437,7 @@ export interface ContainerDefinition {
      * 				<code>--hostname</code> option to <a href="https://docs.docker.com/engine/reference/run/#security-configuration">docker
      * 				run</a>.</p>
      * 		       <note>
-     * 			         <p>The <code>hostname</code> parameter is not supported if you are using the
+     * 			         <p>The <code>hostname</code> parameter is not supported if you're using the
      * 					<code>awsvpc</code> network mode.</p>
      * 		       </note>
      */
@@ -4382,9 +4448,9 @@ export interface ContainerDefinition {
      * 				<code>--user</code> option to <a href="https://docs.docker.com/engine/reference/run/#security-configuration">docker
      * 			run</a>.</p>
      * 		       <important>
-     * 			         <p>When running tasks using the <code>host</code> network mode, you should not run
-     * 				containers using the root user (UID 0). It is considered best practice to use a
-     * 				non-root user.</p>
+     * 			         <p>When running tasks using the <code>host</code> network mode, don't run containers
+     * 				using the root user (UID 0). We recommend using a non-root user for better
+     * 				security.</p>
      * 		       </important>
      * 		       <p>You can specify the <code>user</code> using the following formats. If specifying a UID
      * 			or GID, you must specify it as a positive integer.</p>
@@ -4420,14 +4486,14 @@ export interface ContainerDefinition {
      *                </p>
      * 			         </li>
      *          </ul>
-     *          <note>
+     * 		       <note>
      *                         <p>This parameter is not supported for Windows containers.</p>
      *                      </note>
      */
     user?: string;
     /**
-     * <p>The working directory in which to run commands inside the container. This parameter
-     * 			maps to <code>WorkingDir</code> in the <a href="https://docs.docker.com/engine/api/v1.35/#operation/ContainerCreate">Create a container</a> section of the
+     * <p>The working directory to run commands inside the container in. This parameter maps to
+     * 				<code>WorkingDir</code> in the <a href="https://docs.docker.com/engine/api/v1.35/#operation/ContainerCreate">Create a container</a> section of the
      * 			<a href="https://docs.docker.com/engine/api/v1.35/">Docker Remote API</a> and the <code>--workdir</code> option to <a href="https://docs.docker.com/engine/reference/run/#security-configuration">docker run</a>.</p>
      */
     workingDirectory?: string;
@@ -4435,7 +4501,7 @@ export interface ContainerDefinition {
      * <p>When this parameter is true, networking is disabled within the container. This
      * 			parameter maps to <code>NetworkDisabled</code> in the <a href="https://docs.docker.com/engine/api/v1.35/#operation/ContainerCreate">Create a container</a>
      * 			section of the <a href="https://docs.docker.com/engine/api/v1.35/">Docker Remote API</a>.</p>
-     *          <note>
+     * 		       <note>
      *                         <p>This parameter is not supported for Windows containers.</p>
      *                      </note>
      */
@@ -4445,7 +4511,7 @@ export interface ContainerDefinition {
      * 			container instance (similar to the <code>root</code> user). This parameter maps to
      * 				<code>Privileged</code> in the <a href="https://docs.docker.com/engine/api/v1.35/#operation/ContainerCreate">Create a container</a> section of the
      * 			<a href="https://docs.docker.com/engine/api/v1.35/">Docker Remote API</a> and the <code>--privileged</code> option to <a href="https://docs.docker.com/engine/reference/run/#security-configuration">docker run</a>.</p>
-     *          <note>
+     * 		       <note>
      *                                 <p>This parameter is not supported for Windows containers or tasks run on Fargate.</p>
      *                              </note>
      */
@@ -4456,7 +4522,7 @@ export interface ContainerDefinition {
      * 			<a href="https://docs.docker.com/engine/api/v1.35/#operation/ContainerCreate">Create a container</a> section of the <a href="https://docs.docker.com/engine/api/v1.35/">Docker Remote API</a> and the
      * 				<code>--read-only</code> option to <a href="https://docs.docker.com/engine/reference/run/#security-configuration">docker
      * 				run</a>.</p>
-     *          <note>
+     * 		       <note>
      *                         <p>This parameter is not supported for Windows containers.</p>
      *                      </note>
      */
@@ -4465,7 +4531,7 @@ export interface ContainerDefinition {
      * <p>A list of DNS servers that are presented to the container. This parameter maps to
      * 				<code>Dns</code> in the <a href="https://docs.docker.com/engine/api/v1.35/#operation/ContainerCreate">Create a container</a> section of the
      * 			<a href="https://docs.docker.com/engine/api/v1.35/">Docker Remote API</a> and the <code>--dns</code> option to <a href="https://docs.docker.com/engine/reference/run/#security-configuration">docker run</a>.</p>
-     *          <note>
+     * 		       <note>
      *                         <p>This parameter is not supported for Windows containers.</p>
      *                      </note>
      */
@@ -4474,7 +4540,7 @@ export interface ContainerDefinition {
      * <p>A list of DNS search domains that are presented to the container. This parameter maps
      * 			to <code>DnsSearch</code> in the <a href="https://docs.docker.com/engine/api/v1.35/#operation/ContainerCreate">Create a container</a> section of the
      * 			<a href="https://docs.docker.com/engine/api/v1.35/">Docker Remote API</a> and the <code>--dns-search</code> option to <a href="https://docs.docker.com/engine/reference/run/#security-configuration">docker run</a>.</p>
-     *          <note>
+     * 		       <note>
      *                         <p>This parameter is not supported for Windows containers.</p>
      *                      </note>
      */
@@ -4486,14 +4552,14 @@ export interface ContainerDefinition {
      * 				<code>--add-host</code> option to <a href="https://docs.docker.com/engine/reference/run/#security-configuration">docker
      * 				run</a>.</p>
      * 		       <note>
-     * 			         <p>This parameter is not supported for Windows containers or tasks that use the
+     * 			         <p>This parameter isn't supported for Windows containers or tasks that use the
      * 					<code>awsvpc</code> network mode.</p>
      * 		       </note>
      */
     extraHosts?: HostEntry[];
     /**
      * <p>A list of strings to provide custom labels for SELinux and AppArmor multi-level
-     * 			security systems. This field is not valid for containers in tasks using the
+     * 			security systems. This field isn't valid for containers in tasks using the
      * 			Fargate launch type.</p>
      * 		       <p>With Windows containers, this parameter can be used to reference a credential spec
      * 			file when configuring a container for Active Directory authentication. For more
@@ -4517,10 +4583,10 @@ export interface ContainerDefinition {
      */
     dockerSecurityOptions?: string[];
     /**
-     * <p>When this parameter is <code>true</code>, this allows you to deploy containerized
-     * 			applications that require <code>stdin</code> or a <code>tty</code> to be allocated. This
-     * 			parameter maps to <code>OpenStdin</code> in the <a href="https://docs.docker.com/engine/api/v1.35/#operation/ContainerCreate">Create a container</a>
-     * 			section of the <a href="https://docs.docker.com/engine/api/v1.35/">Docker Remote API</a> and the <code>--interactive</code> option to <a href="https://docs.docker.com/engine/reference/run/#security-configuration">docker run</a>.</p>
+     * <p>When this parameter is <code>true</code>, you can deploy containerized applications
+     * 			that require <code>stdin</code> or a <code>tty</code> to be allocated. This parameter
+     * 			maps to <code>OpenStdin</code> in the <a href="https://docs.docker.com/engine/api/v1.35/#operation/ContainerCreate">Create a container</a> section of the
+     * 			<a href="https://docs.docker.com/engine/api/v1.35/">Docker Remote API</a> and the <code>--interactive</code> option to <a href="https://docs.docker.com/engine/reference/run/#security-configuration">docker run</a>.</p>
      */
     interactive?: boolean;
     /**
@@ -4540,8 +4606,8 @@ export interface ContainerDefinition {
     };
     /**
      * <p>A list of <code>ulimits</code> to set in the container. If a ulimit value is specified
-     * 			in a task definition, it will override the default values set by Docker. This parameter
-     * 			maps to <code>Ulimits</code> in the <a href="https://docs.docker.com/engine/api/v1.35/#operation/ContainerCreate">Create a container</a> section of the
+     * 			in a task definition, it overrides the default values set by Docker. This parameter maps
+     * 			to <code>Ulimits</code> in the <a href="https://docs.docker.com/engine/api/v1.35/#operation/ContainerCreate">Create a container</a> section of the
      * 			<a href="https://docs.docker.com/engine/api/v1.35/">Docker Remote API</a> and the <code>--ulimit</code> option to <a href="https://docs.docker.com/engine/reference/run/#security-configuration">docker run</a>. Valid naming values are displayed
      * 			in the <a>Ulimit</a> data type.</p>
      * 		       <p>Amazon ECS tasks hosted on Fargate use the default
@@ -4553,7 +4619,7 @@ export interface ContainerDefinition {
      * 							is <code>4096</code>.</p>
      * 		       <p>This parameter requires version 1.18 of the Docker Remote API or greater on your container instance. To check the Docker Remote API version on your container instance, log in to your container instance and run the following command: <code>sudo docker version --format '{{.Server.APIVersion}}'</code>
      *          </p>
-     *          <note>
+     * 		       <note>
      *                         <p>This parameter is not supported for Windows containers.</p>
      *                      </note>
      */
@@ -4564,12 +4630,12 @@ export interface ContainerDefinition {
      * 			<a href="https://docs.docker.com/engine/api/v1.35/#operation/ContainerCreate">Create a container</a> section of the <a href="https://docs.docker.com/engine/api/v1.35/">Docker Remote API</a> and the
      * 				<code>--log-driver</code> option to <a href="https://docs.docker.com/engine/reference/run/#security-configuration">docker
      * 				run</a>. By default, containers use the same logging driver that the Docker
-     * 			daemon uses. However the container may use a different logging driver than the Docker
+     * 			daemon uses. However the container can use a different logging driver than the Docker
      * 			daemon by specifying a log driver with this parameter in the container definition. To
      * 			use a different logging driver for a container, the log system must be configured
      * 			properly on the container instance (or on a different log server for remote logging
-     * 			options). For more information on the options for different supported log drivers, see
-     * 				<a href="https://docs.docker.com/engine/admin/logging/overview/">Configure
+     * 			options). For more information about the options for different supported log drivers,
+     * 			see <a href="https://docs.docker.com/engine/admin/logging/overview/">Configure
      * 				logging drivers</a> in the Docker documentation.</p>
      * 		       <note>
      * 			         <p>Amazon ECS currently supports a subset of the logging drivers available to the Docker
@@ -4601,10 +4667,10 @@ export interface ContainerDefinition {
      * 				<code>Sysctls</code> in the <a href="https://docs.docker.com/engine/api/v1.35/#operation/ContainerCreate">Create a container</a> section of the
      * 			<a href="https://docs.docker.com/engine/api/v1.35/">Docker Remote API</a> and the <code>--sysctl</code> option to <a href="https://docs.docker.com/engine/reference/run/#security-configuration">docker run</a>.</p>
      * 		       <note>
-     * 			         <p>It is not recommended that you specify network-related <code>systemControls</code>
+     * 			         <p>We don't recommended that you specify network-related <code>systemControls</code>
      * 				parameters for multiple containers in a single task that also uses either the
      * 					<code>awsvpc</code> or <code>host</code> network modes. For tasks that use the
-     * 					<code>awsvpc</code> network mode, the container that is started last determines
+     * 					<code>awsvpc</code> network mode, the container that's started last determines
      * 				which <code>systemControls</code> parameters take effect. For tasks that use the
      * 					<code>host</code> network mode, it changes the container instance's namespaced
      * 				kernel parameters as well as the containers.</p>
@@ -4635,15 +4701,14 @@ export declare namespace ContainerDefinition {
  * 			tasks hosted on Fargate. For more information, see <a href="https://docs.aws.amazon.com/AmazonECS/latest/userguide/using_data_volumes.html">Fargate task
  * 				storage</a> in the <i>Amazon ECS User Guide for Fargate</i>.</p>
  * 		       <note>
- * 			         <p>This parameter is only supported for tasks hosted on Fargate using the following platform versions:</p>
+ * 			         <p>This parameter is only supported for tasks hosted on Fargate using
+ * 				the following platform versions:</p>
  * 			         <ul>
  *                <li>
- * 					             <p>Linux platform
- * 						version <code>1.4.0</code> or later.</p>
+ * 					             <p>Linux platform version <code>1.4.0</code> or later.</p>
  * 				           </li>
  *                <li>
- * 					             <p>Windows platform
- * 						version <code>1.0.0</code> or later.</p>
+ * 					             <p>Windows platform version <code>1.0.0</code> or later.</p>
  * 				           </li>
  *             </ul>
  * 		       </note>
@@ -4663,9 +4728,8 @@ export declare namespace EphemeralStorage {
     const filterSensitiveLog: (obj: EphemeralStorage) => any;
 }
 /**
- * <p>Details on a Elastic Inference accelerator. For more information, see <a href="https://docs.aws.amazon.com/AmazonECS/latest/developerguide/ecs-inference.html">Working with
- * 				Amazon Elastic Inference on Amazon ECS</a> in the
- * 				<i>Amazon Elastic Container Service Developer Guide</i>.</p>
+ * <p>Details on an Elastic Inference accelerator. For more information, see <a href="https://docs.aws.amazon.com/AmazonECS/latest/developerguide/ecs-inference.html">Working with Amazon Elastic Inference on
+ * 				Amazon ECS</a> in the <i>Amazon Elastic Container Service Developer Guide</i>.</p>
  */
 export interface InferenceAccelerator {
     /**
@@ -4707,7 +4771,7 @@ export declare enum TaskDefinitionPlacementConstraintType {
  * 			information, see <a href="https://docs.aws.amazon.com/AmazonECS/latest/developerguide/task-placement-constraints.html">Task placement constraints</a> in the
  * 				<i>Amazon Elastic Container Service Developer Guide</i>.</p>
  * 		       <note>
- * 			         <p>Task placement constraints are not supported for tasks run on Fargate.</p>
+ * 			         <p>Task placement constraints aren't supported for tasks run on Fargate.</p>
  * 		       </note>
  */
 export interface TaskDefinitionPlacementConstraint {
@@ -4734,10 +4798,10 @@ export declare enum ProxyConfigurationType {
 }
 /**
  * <p>The configuration details for the App Mesh proxy.</p>
- * 		       <p>For tasks using the EC2 launch type, the container instances require at
- * 			least version 1.26.0 of the container agent and at least version 1.26.0-1 of the
+ * 		       <p>For tasks that use the EC2 launch type, the container instances require
+ * 			at least version 1.26.0 of the container agent and at least version 1.26.0-1 of the
  * 				<code>ecs-init</code> package to enable a proxy configuration. If your container
- * 			instances are launched from the Amazon ECS-optimized AMI version <code>20190301</code> or
+ * 			instances are launched from the Amazon ECS optimized AMI version <code>20190301</code> or
  * 			later, then they contain the required versions of the container agent and
  * 				<code>ecs-init</code>. For more information, see <a href="https://docs.aws.amazon.com/AmazonECS/latest/developerguide/ecs-optimized_AMI.html">Amazon ECS-optimized Linux AMI</a>
  * 		       </p>
@@ -4849,8 +4913,8 @@ export declare enum Scope {
     TASK = "task"
 }
 /**
- * <p>This parameter is specified when you are using Docker volumes. Docker volumes are only
- * 			supported when you are using the EC2 launch type. Windows containers only
+ * <p>This parameter is specified when you're using Docker volumes. Docker volumes are only
+ * 			supported when you're using the EC2 launch type. Windows containers only
  * 			support the use of the <code>local</code> driver. To use bind mounts, specify a
  * 				<code>host</code> instead.</p>
  */
@@ -4863,8 +4927,8 @@ export interface DockerVolumeConfiguration {
      */
     scope?: Scope | string;
     /**
-     * <p>If this value is <code>true</code>, the Docker volume is created if it does not
-     * 			already exist.</p>
+     * <p>If this value is <code>true</code>, the Docker volume is created if it doesn't already
+     * 			exist.</p>
      * 		       <note>
      * 			         <p>This field is only used if the <code>scope</code> is <code>shared</code>.</p>
      * 		       </note>
@@ -4925,7 +4989,7 @@ export interface EFSAuthorizationConfig {
      */
     accessPointId?: string;
     /**
-     * <p>Whether or not to use the Amazon ECS task IAM role defined in a task definition when
+     * <p>Determines whether to use the Amazon ECS task IAM role defined in a task definition when
      * 			mounting the Amazon EFS file system. If enabled, transit encryption must be enabled in the
      * 				<code>EFSVolumeConfiguration</code>. If this parameter is omitted, the default value
      * 			of <code>DISABLED</code> is used. For more information, see <a href="https://docs.aws.amazon.com/AmazonECS/latest/developerguide/efs-volumes.html#efs-volume-accesspoints">Using
@@ -4944,7 +5008,7 @@ export declare enum EFSTransitEncryption {
     ENABLED = "ENABLED"
 }
 /**
- * <p>This parameter is specified when you are using an Amazon Elastic File System file system for task
+ * <p>This parameter is specified when you're using an Amazon Elastic File System file system for task
  * 			storage. For more information, see <a href="https://docs.aws.amazon.com/AmazonECS/latest/developerguide/efs-volumes.html">Amazon EFS Volumes</a> in the
  * 				<i>Amazon Elastic Container Service Developer Guide</i>.</p>
  */
@@ -4965,10 +5029,10 @@ export interface EFSVolumeConfiguration {
      */
     rootDirectory?: string;
     /**
-     * <p>Whether or not to enable encryption for Amazon EFS data in transit between the Amazon ECS host
-     * 			and the Amazon EFS server. Transit encryption must be enabled if Amazon EFS IAM authorization is
-     * 			used. If this parameter is omitted, the default value of <code>DISABLED</code> is used.
-     * 			For more information, see <a href="https://docs.aws.amazon.com/efs/latest/ug/encryption-in-transit.html">Encrypting Data in Transit</a> in
+     * <p>Determines whether to enable encryption for Amazon EFS data in transit between the Amazon ECS
+     * 			host and the Amazon EFS server. Transit encryption must be enabled if Amazon EFS IAM authorization
+     * 			is used. If this parameter is omitted, the default value of <code>DISABLED</code> is
+     * 			used. For more information, see <a href="https://docs.aws.amazon.com/efs/latest/ug/encryption-in-transit.html">Encrypting Data in Transit</a> in
      * 			the <i>Amazon Elastic File System User Guide</i>.</p>
      */
     transitEncryption?: EFSTransitEncryption | string;
@@ -5016,7 +5080,7 @@ export declare namespace FSxWindowsFileServerAuthorizationConfig {
     const filterSensitiveLog: (obj: FSxWindowsFileServerAuthorizationConfig) => any;
 }
 /**
- * <p>This parameter is specified when you are using <a href="https://docs.aws.amazon.com/fsx/latest/WindowsGuide/what-is.html">Amazon FSx for Windows File Server</a> file system for task
+ * <p>This parameter is specified when you're using <a href="https://docs.aws.amazon.com/fsx/latest/WindowsGuide/what-is.html">Amazon FSx for Windows File Server</a> file system for task
  * 			storage.</p>
  * 		       <p>For more information and the input format, see <a href="https://docs.aws.amazon.com/AmazonECS/latest/developerguide/wfsx-volumes.html">Amazon FSx for Windows File Server Volumes</a>
  * 			in the <i>Amazon Elastic Container Service Developer Guide</i>.</p>
@@ -5048,14 +5112,14 @@ export declare namespace FSxWindowsFileServerVolumeConfiguration {
 export interface HostVolumeProperties {
     /**
      * <p>When the <code>host</code> parameter is used, specify a <code>sourcePath</code> to
-     * 			declare the path on the host container instance that is presented to the container. If
+     * 			declare the path on the host container instance that's presented to the container. If
      * 			this parameter is empty, then the Docker daemon has assigned a host path for you. If the
      * 				<code>host</code> parameter contains a <code>sourcePath</code> file location, then
      * 			the data volume persists at the specified location on the host container instance until
-     * 			you delete it manually. If the <code>sourcePath</code> value does not exist on the host
+     * 			you delete it manually. If the <code>sourcePath</code> value doesn't exist on the host
      * 			container instance, the Docker daemon creates it. If the location does exist, the
      * 			contents of the source path folder are exported.</p>
-     * 		       <p>If you are using the Fargate launch type, the <code>sourcePath</code>
+     * 		       <p>If you're using the Fargate launch type, the <code>sourcePath</code>
      * 			parameter is not supported.</p>
      */
     sourcePath?: string;
@@ -5067,9 +5131,9 @@ export declare namespace HostVolumeProperties {
     const filterSensitiveLog: (obj: HostVolumeProperties) => any;
 }
 /**
- * <p>A data volume used in a task definition. For tasks that use the Amazon Elastic File
- * 			System (Amazon EFS), specify an <code>efsVolumeConfiguration</code>. For Windows tasks
- * 			that use Amazon FSx for Windows File Server file system, specify a
+ * <p>A data volume that's used in a task definition. For tasks that use the Amazon Elastic
+ * 			File System (Amazon EFS), specify an <code>efsVolumeConfiguration</code>. For Windows
+ * 			tasks that use Amazon FSx for Windows File Server file system, specify a
  * 				<code>fsxWindowsFileServerVolumeConfiguration</code>. For tasks that use a Docker
  * 			volume, specify a <code>DockerVolumeConfiguration</code>. For tasks that use a bind
  * 			mount host volume, specify a <code>host</code> and optional <code>sourcePath</code>. For
@@ -5084,35 +5148,35 @@ export interface Volume {
      */
     name?: string;
     /**
-     * <p>This parameter is specified when you are using bind mount host volumes. The contents
-     * 			of the <code>host</code> parameter determine whether your bind mount host volume
-     * 			persists on the host container instance and where it is stored. If the <code>host</code>
-     * 			parameter is empty, then the Docker daemon assigns a host path for your data volume.
-     * 			However, the data is not guaranteed to persist after the containers associated with it
-     * 			stop running.</p>
+     * <p>This parameter is specified when you use bind mount host volumes. The contents of the
+     * 				<code>host</code> parameter determine whether your bind mount host volume persists
+     * 			on the host container instance and where it's stored. If the <code>host</code> parameter
+     * 			is empty, then the Docker daemon assigns a host path for your data volume. However, the
+     * 			data isn't guaranteed to persist after the containers that are associated with it stop
+     * 			running.</p>
      * 		       <p>Windows containers can mount whole directories on the same drive as
-     * 				<code>$env:ProgramData</code>. Windows containers cannot mount directories on a
-     * 			different drive, and mount point cannot be across drives. For example, you can mount
+     * 				<code>$env:ProgramData</code>. Windows containers can't mount directories on a
+     * 			different drive, and mount point can't be across drives. For example, you can mount
      * 				<code>C:\my\path:C:\my\path</code> and <code>D:\:D:\</code>, but not
      * 				<code>D:\my\path:C:\my\path</code> or <code>D:\:C:\my\path</code>.</p>
      */
     host?: HostVolumeProperties;
     /**
-     * <p>This parameter is specified when you are using Docker volumes.</p>
+     * <p>This parameter is specified when you use Docker volumes.</p>
      * 		       <p>Windows containers only support the use of the <code>local</code> driver. To use bind
      * 			mounts, specify the <code>host</code> parameter instead.</p>
      * 		       <note>
-     * 			         <p>Docker volumes are not supported by tasks run on Fargate.</p>
+     * 			         <p>Docker volumes aren't supported by tasks run on Fargate.</p>
      * 		       </note>
      */
     dockerVolumeConfiguration?: DockerVolumeConfiguration;
     /**
-     * <p>This parameter is specified when you are using an Amazon Elastic File System file system for task
+     * <p>This parameter is specified when you use an Amazon Elastic File System file system for task
      * 			storage.</p>
      */
     efsVolumeConfiguration?: EFSVolumeConfiguration;
     /**
-     * <p>This parameter is specified when you are using Amazon FSx for Windows File Server file system for task
+     * <p>This parameter is specified when you use Amazon FSx for Windows File Server file system for task
      * 			storage.</p>
      */
     fsxWindowsFileServerVolumeConfiguration?: FSxWindowsFileServerVolumeConfiguration;
@@ -5142,8 +5206,9 @@ export interface TaskDefinition {
      */
     containerDefinitions?: ContainerDefinition[];
     /**
-     * <p>The name of a family that this task definition is registered to. Up to 255 letters
-     * 			(uppercase and lowercase), numbers, hyphens, and underscores are allowed.</p>
+     * <p>The name of a family that this task definition is registered to. Up to 255 characters
+     * 			are allowed. Letters (both uppercase and lowercase letters), numbers, hyphens (-), and
+     * 			underscores (_) are allowed.</p>
      * 		       <p>A family groups multiple versions of a task definition. Amazon ECS gives the first task
      * 			definition that you registered to a family a revision number of 1. Amazon ECS gives
      * 			sequential revision numbers to each task definition that you add.</p>
@@ -5155,8 +5220,7 @@ export interface TaskDefinition {
      * 				Task Role</a> in the <i>Amazon Elastic Container Service Developer Guide</i>.</p>
      * 		       <p>IAM roles for tasks on Windows require that the <code>-EnableTaskIAMRole</code> option
      * 			is set when you launch the Amazon ECS-optimized Windows AMI. Your containers must also run some
-     * 			configuration code in order to take advantage of the feature. For more information, see
-     * 				<a href="https://docs.aws.amazon.com/AmazonECS/latest/developerguide/windows_task_IAM_roles.html">Windows IAM roles
+     * 			configuration code to use the feature. For more information, see <a href="https://docs.aws.amazon.com/AmazonECS/latest/developerguide/windows_task_IAM_roles.html">Windows IAM roles
      * 				for tasks</a> in the <i>Amazon Elastic Container Service Developer Guide</i>.</p>
      */
     taskRoleArn?: string;
@@ -5202,15 +5266,15 @@ export interface TaskDefinition {
      * <p>The revision of the task in a particular family. The revision is a version number of a
      * 			task definition in a family. When you register a task definition for the first time, the
      * 			revision is <code>1</code>. Each time that you register a new revision of a task
-     * 			definition in the same family, the revision value always increases by one, even if you
-     * 			have deregistered previous revisions in this family.</p>
+     * 			definition in the same family, the revision value always increases by one. This is even
+     * 			if you deregistered previous revisions in this family.</p>
      */
     revision?: number;
     /**
      * <p>The list of data volume definitions for the task. For more information, see <a href="https://docs.aws.amazon.com/AmazonECS/latest/developerguide/using_data_volumes.html">Using data volumes in tasks</a> in the
      * 			<i>Amazon Elastic Container Service Developer Guide</i>.</p>
      * 		       <note>
-     * 			         <p>The <code>host</code> and <code>sourcePath</code> parameters are not supported for
+     * 			         <p>The <code>host</code> and <code>sourcePath</code> parameters aren't supported for
      * 				tasks run on Fargate.</p>
      * 		       </note>
      */
@@ -5222,19 +5286,19 @@ export interface TaskDefinition {
     /**
      * <p>The container instance attributes required by your task. When an Amazon EC2 instance is
      * 			registered to your cluster, the Amazon ECS container agent assigns some standard attributes
-     * 			to the instance. You can apply custom attributes, specified as key-value pairs using the
-     * 			Amazon ECS console or the <a>PutAttributes</a> API. These attributes are used when
-     * 			considering task placement for tasks hosted on Amazon EC2 instances. For more information,
-     * 			see <a href="https://docs.aws.amazon.com/AmazonECS/latest/developerguide/task-placement-constraints.html#attributes">Attributes</a> in the <i>Amazon Elastic Container Service Developer Guide</i>.</p>
+     * 			to the instance. You can apply custom attributes. These are specified as key-value pairs
+     * 			using the Amazon ECS console or the <a>PutAttributes</a> API. These attributes are
+     * 			used when determining task placement for tasks hosted on Amazon EC2 instances. For more
+     * 			information, see <a href="https://docs.aws.amazon.com/AmazonECS/latest/developerguide/task-placement-constraints.html#attributes">Attributes</a> in the <i>Amazon Elastic Container Service Developer Guide</i>.</p>
      * 		       <note>
-     * 			         <p>This parameter is not supported for tasks run on Fargate.</p>
+     * 			         <p>This parameter isn't supported for tasks run on Fargate.</p>
      * 		       </note>
      */
     requiresAttributes?: Attribute[];
     /**
      * <p>An array of placement constraint objects to use for tasks.</p>
      * 		       <note>
-     * 			         <p>This parameter is not supported for tasks run on Fargate.</p>
+     * 			         <p>This parameter isn't supported for tasks run on Fargate.</p>
      * 		       </note>
      */
     placementConstraints?: TaskDefinitionPlacementConstraint[];
@@ -5245,8 +5309,10 @@ export interface TaskDefinition {
      */
     compatibilities?: (Compatibility | string)[];
     /**
-     * <p>The operating system  that your task definitions are running on. A platform family is specified only for tasks using the Fargate launch type. </p>
-     * 		       <p>When you specify a task in a service, this value must match the <code>runtimePlatform</code> value of the service.</p>
+     * <p>The operating system that your task definitions are running on. A platform family is
+     * 			specified only for tasks using the Fargate launch type. </p>
+     * 		       <p>When you specify a task in a service, this value must match the
+     * 				<code>runtimePlatform</code> value of the service.</p>
      */
     runtimePlatform?: RuntimePlatform;
     /**
@@ -5255,10 +5321,12 @@ export interface TaskDefinition {
      */
     requiresCompatibilities?: (Compatibility | string)[];
     /**
-     * <p>The number of <code>cpu</code> units used by the task. If you are using the EC2 launch
-     * 			type, this field is optional and any value can be used. If you are using the Fargate
-     * 			launch type, this field is required and you must use one of the following values, which
-     * 			determines your range of valid values for the <code>memory</code> parameter:</p>
+     * <p>The number of <code>cpu</code> units used by the task. If you use the EC2 launch type,
+     * 			this field is optional. Any value can be used. If you use the Fargate launch type, this
+     * 			field is required. You must use one of the following values. The value that you choose
+     * 			determines your range of valid values for the <code>memory</code> parameter.</p>
+     * 		       <p>The CPU units cannot be less than 1 vCPU when you use Windows containers on
+     * 			Fargate.</p>
      * 		       <ul>
      *             <li>
      *                 <p>256 (.25 vCPU) - Available <code>memory</code> values: 512 (0.5 GB), 1024 (1 GB), 2048 (2 GB)</p>
@@ -5280,15 +5348,15 @@ export interface TaskDefinition {
     cpu?: string;
     /**
      * <p>The amount (in MiB) of memory used by the task.</p>
-     * 		       <p>If your tasks will be run on Amazon EC2 instances, you must specify either a task-level
-     * 			memory value or a container-level memory value. This field is optional and any value can
-     * 			be used. If a task-level memory value is specified then the container-level memory value
-     * 			is optional. For more information regarding container-level memory and memory
-     * 			reservation, see <a href="https://docs.aws.amazon.com/AmazonECS/latest/APIReference/API_ContainerDefinition.html">ContainerDefinition</a>.</p>
-     * 		       <p>If your tasks will be run on Fargate, this field is required and you must use one of
-     * 			the following values, which determines your range of valid values for the
-     * 				<code>cpu</code> parameter:</p>
-     *          <ul>
+     * 		       <p>If your tasks runs on Amazon EC2 instances, you must specify either a task-level memory
+     * 			value or a container-level memory value. This field is optional and any value can be
+     * 			used. If a task-level memory value is specified, the container-level memory value is
+     * 			optional. For more information regarding container-level memory and memory reservation,
+     * 			see <a href="https://docs.aws.amazon.com/AmazonECS/latest/APIReference/API_ContainerDefinition.html">ContainerDefinition</a>.</p>
+     * 		       <p>If your tasks runs on Fargate, this field is required. You must use one of the
+     * 			following values. The value you choose determines your range of valid values for the
+     * 				<code>cpu</code> parameter.</p>
+     * 		       <ul>
      *             <li>
      *                 <p>512 (0.5 GB), 1024 (1 GB), 2048 (2 GB) - Available <code>cpu</code> values: 256 (.25 vCPU)</p>
      *             </li>
@@ -5308,7 +5376,7 @@ export interface TaskDefinition {
      */
     memory?: string;
     /**
-     * <p>The Elastic Inference accelerator associated with the task.</p>
+     * <p>The Elastic Inference accelerator that's associated with the task.</p>
      */
     inferenceAccelerators?: InferenceAccelerator[];
     /**
@@ -5369,17 +5437,17 @@ export interface TaskDefinition {
      * <p>The configuration details for the App Mesh proxy.</p>
      * 		       <p>Your Amazon ECS container instances require at least version 1.26.0 of the container agent
      * 			and at least version 1.26.0-1 of the <code>ecs-init</code> package to enable a proxy
-     * 			configuration. If your container instances are launched from the Amazon ECS-optimized AMI
-     * 			version <code>20190301</code> or later, then they contain the required versions of the
+     * 			configuration. If your container instances are launched from the Amazon ECS optimized AMI
+     * 			version <code>20190301</code> or later, they contain the required versions of the
      * 			container agent and <code>ecs-init</code>. For more information, see <a href="https://docs.aws.amazon.com/AmazonECS/latest/developerguide/ecs-optimized_AMI.html">Amazon ECS-optimized Linux AMI</a> in the <i>Amazon Elastic Container Service Developer Guide</i>.</p>
      */
     proxyConfiguration?: ProxyConfiguration;
     /**
-     * <p>The Unix timestamp for when the task definition was registered.</p>
+     * <p>The Unix timestamp for the time when the task definition was registered.</p>
      */
     registeredAt?: Date;
     /**
-     * <p>The Unix timestamp for when the task definition was deregistered.</p>
+     * <p>The Unix timestamp for the time when the task definition was deregistered.</p>
      */
     deregisteredAt?: Date;
     /**
@@ -5421,7 +5489,7 @@ export interface DescribeCapacityProvidersRequest {
     /**
      * <p>Specifies whether or not you want to see the resource tags for the capacity provider.
      * 			If <code>TAGS</code> is specified, the tags are included in the response. If this field
-     * 			is omitted, tags are not included in the response.</p>
+     * 			is omitted, tags aren't included in the response.</p>
      */
     include?: (CapacityProviderField | string)[];
     /**
@@ -5518,8 +5586,8 @@ export interface DescribeClustersRequest {
      */
     clusters?: string[];
     /**
-     * <p>Whether to include additional information about the clusters in the response. If this
-     * 			field is omitted, this information isn't included.</p>
+     * <p>Determines whether to include additional information about the clusters in the
+     * 			response. If this field is omitted, this information isn't included.</p>
      * 		       <p>If <code>ATTACHMENTS</code> is specified, the attachments for the container instances
      * 			or tasks within the cluster are included.</p>
      * 		       <p>If <code>SETTINGS</code> is specified, the settings for the cluster are
@@ -5556,6 +5624,7 @@ export declare namespace DescribeClustersResponse {
     const filterSensitiveLog: (obj: DescribeClustersResponse) => any;
 }
 export declare enum ContainerInstanceField {
+    CONTAINER_INSTANCE_HEALTH = "CONTAINER_INSTANCE_HEALTH",
     TAGS = "TAGS"
 }
 export interface DescribeContainerInstancesRequest {
@@ -5572,8 +5641,10 @@ export interface DescribeContainerInstancesRequest {
     containerInstances: string[] | undefined;
     /**
      * <p>Specifies whether you want to see the resource tags for the container instance. If
-     * 				<code>TAGS</code> is specified, the tags are included in the response. If this field
-     * 			is omitted, tags are not included in the response.</p>
+     * 				<code>TAGS</code> is specified, the tags are included in the response. If
+     * 				<code>CONTAINER_INSTANCE_HEALTH</code> is specified, the container instance health
+     * 			is included in the response. If this field is omitted, tags and container instance
+     * 			health status aren't included in the response.</p>
      */
     include?: (ContainerInstanceField | string)[];
 }
@@ -5615,9 +5686,9 @@ export interface DescribeServicesRequest {
      */
     services: string[] | undefined;
     /**
-     * <p>Specifies whether you want to see the resource tags for the service. If
+     * <p>Determines whether you want to see the resource tags for the service. If
      * 				<code>TAGS</code> is specified, the tags are included in the response. If this field
-     * 			is omitted, tags are not included in the response.</p>
+     * 			is omitted, tags aren't included in the response.</p>
      */
     include?: (ServiceField | string)[];
 }
@@ -5655,9 +5726,9 @@ export interface DescribeTaskDefinitionRequest {
      */
     taskDefinition: string | undefined;
     /**
-     * <p>Specifies whether to see the resource tags for the task definition. If
+     * <p>Determines whether to see the resource tags for the task definition. If
      * 				<code>TAGS</code> is specified, the tags are included in the response. If this field
-     * 			is omitted, tags are not included in the response.</p>
+     * 			is omitted, tags aren't included in the response.</p>
      */
     include?: (TaskDefinitionField | string)[];
 }
@@ -5673,10 +5744,9 @@ export interface DescribeTaskDefinitionResponse {
      */
     taskDefinition?: TaskDefinition;
     /**
-     * <p>The metadata that is applied to the task definition to help you categorize and
-     * 			organize them. Each tag consists of a key and an optional value, both of which you
-     * 			define.</p>
-     *          <p>The following basic restrictions apply to tags:</p>
+     * <p>The metadata that's applied to the task definition to help you categorize and organize
+     * 			them. Each tag consists of a key and an optional value. You define both.</p>
+     * 		       <p>The following basic restrictions apply to tags:</p>
      *         <ul>
      *             <li>
      *                 <p>Maximum number of tags per resource - 50</p>
@@ -5732,8 +5802,8 @@ export interface DescribeTasksRequest {
     tasks: string[] | undefined;
     /**
      * <p>Specifies whether you want to see the resource tags for the task. If <code>TAGS</code>
-     * 			is specified, the tags are included in the response. If this field is omitted, tags are
-     * 			not included in the response.</p>
+     * 			is specified, the tags are included in the response. If this field is omitted, tags
+     * 			aren't included in the response.</p>
      */
     include?: (TaskField | string)[];
 }
@@ -5760,7 +5830,7 @@ export declare enum ManagedAgentName {
  */
 export interface ManagedAgent {
     /**
-     * <p>The Unix timestamp for when the managed agent was last started.</p>
+     * <p>The Unix timestamp for the time when the managed agent was last started.</p>
      */
     lastStartedAt?: Date;
     /**
@@ -5795,11 +5865,11 @@ export interface NetworkBinding {
      */
     bindIP?: string;
     /**
-     * <p>The port number on the container that is used with the network binding.</p>
+     * <p>The port number on the container that's used with the network binding.</p>
      */
     containerPort?: number;
     /**
-     * <p>The port number on the host that is used with the network binding.</p>
+     * <p>The port number on the host that's used with the network binding.</p>
      */
     hostPort?: number;
     /**
@@ -5838,7 +5908,7 @@ export declare namespace NetworkInterface {
     const filterSensitiveLog: (obj: NetworkInterface) => any;
 }
 /**
- * <p>A Docker container that is part of a task.</p>
+ * <p>A Docker container that's part of a task.</p>
  */
 export interface Container {
     /**
@@ -5891,7 +5961,7 @@ export interface Container {
      */
     networkInterfaces?: NetworkInterface[];
     /**
-     * <p>The health status of the container. If health checks are not configured for this
+     * <p>The health status of the container. If health checks aren't configured for this
      * 			container in its task definition, then it reports the health status as
      * 				<code>UNKNOWN</code>.</p>
      */
@@ -5901,8 +5971,8 @@ export interface Container {
      */
     managedAgents?: ManagedAgent[];
     /**
-     * <p>The number of CPU units set for the container. The value will be <code>0</code> if no
-     * 			value was specified in the container definition when the task definition was
+     * <p>The number of CPU units set for the container. The value is <code>0</code> if no value
+     * 			was specified in the container definition when the task definition was
      * 			registered.</p>
      */
     cpu?: string;
@@ -5926,10 +5996,10 @@ export declare namespace Container {
     const filterSensitiveLog: (obj: Container) => any;
 }
 /**
- * <p>The overrides that should be sent to a container. An empty container override can be
- * 			passed in. An example of an empty container override would be
- * 				<code>{"containerOverrides": [ ] }</code>. If a non-empty container override is
- * 			specified, the <code>name</code> parameter must be included.</p>
+ * <p>The overrides that are sent to a container. An empty container override can be passed
+ * 			in. An example of an empty container override is <code>{"containerOverrides": [ ]
+ * 				}</code>. If a non-empty container override is specified, the <code>name</code>
+ * 			parameter must be included.</p>
  */
 export interface ContainerOverride {
     /**
@@ -5985,8 +6055,9 @@ export declare namespace ContainerOverride {
 /**
  * <p>Details on an Elastic Inference accelerator task override. This parameter is used to
  * 			override the Elastic Inference accelerator specified in the task definition. For more
- * 			information, see <a href="https://docs.aws.amazon.com/AmazonECS/latest/developerguide/ecs-inference.html">Working with Amazon Elastic Inference on Amazon ECS</a> in the
- * 				<i>Amazon Elastic Container Service Developer Guide</i>.</p>
+ * 			information, see <a href="https://docs.aws.amazon.com/AmazonECS/latest/developerguide/ecs-inference.html">Working with Amazon
+ * 				Elastic Inference on Amazon ECS</a> in the
+ * 			<i>Amazon Elastic Container Service Developer Guide</i>.</p>
  */
 export interface InferenceAcceleratorOverride {
     /**
@@ -6006,11 +6077,11 @@ export declare namespace InferenceAcceleratorOverride {
     const filterSensitiveLog: (obj: InferenceAcceleratorOverride) => any;
 }
 /**
- * <p>The overrides associated with a task.</p>
+ * <p>The overrides that are associated with a task.</p>
  */
 export interface TaskOverride {
     /**
-     * <p>One or more container overrides sent to a task.</p>
+     * <p>One or more container overrides that are sent to a task.</p>
      */
     containerOverrides?: ContainerOverride[];
     /**
@@ -6022,8 +6093,8 @@ export interface TaskOverride {
      */
     inferenceAcceleratorOverrides?: InferenceAcceleratorOverride[];
     /**
-     * <p>The Amazon Resource Name (ARN) of the task execution IAM role override for the task. For more information,
-     * 			see <a href="https://docs.aws.amazon.com/AmazonECS/latest/developerguide/task_execution_IAM_role.html">Amazon ECS task
+     * <p>The Amazon Resource Name (ARN) of the task execution IAM role override for the task. For more
+     * 			information, see <a href="https://docs.aws.amazon.com/AmazonECS/latest/developerguide/task_execution_IAM_role.html">Amazon ECS task
      * 				execution IAM role</a> in the <i>Amazon Elastic Container Service Developer Guide</i>.</p>
      */
     executionRoleArn?: string;
@@ -6032,8 +6103,8 @@ export interface TaskOverride {
      */
     memory?: string;
     /**
-     * <p>The Amazon Resource Name (ARN) of the IAM role that containers in this task can assume. All containers in
-     * 			this task are granted the permissions that are specified in this role. For more
+     * <p>The Amazon Resource Name (ARN) of the IAM role that containers in this task can assume. All containers
+     * 			in this task are granted the permissions that are specified in this role. For more
      * 			information, see <a href="https://docs.aws.amazon.com/AmazonECS/latest/developerguide/task-iam-roles.html">IAM Role for Tasks</a>
      * 			in the <i>Amazon Elastic Container Service Developer Guide</i>.</p>
      */
@@ -6041,15 +6112,14 @@ export interface TaskOverride {
     /**
      * <p>The ephemeral storage setting override for the task.</p>
      * 		       <note>
-     * 			         <p>This parameter is only supported for tasks hosted on Fargate using the following platform versions:</p>
+     * 			         <p>This parameter is only supported for tasks hosted on Fargate that
+     * 				use the following platform versions:</p>
      * 			         <ul>
      *                <li>
-     * 					             <p>Linux platform
-     * 						version <code>1.4.0</code> or later.</p>
+     * 					             <p>Linux platform version <code>1.4.0</code> or later.</p>
      * 				           </li>
      *                <li>
-     * 					             <p>Windows platform
-     * 						version <code>1.0.0</code> or later.</p>
+     * 					             <p>Windows platform version <code>1.0.0</code> or later.</p>
      * 				           </li>
      *             </ul>
      * 		       </note>
@@ -6072,7 +6142,7 @@ export declare enum TaskStopCode {
  */
 export interface Task {
     /**
-     * <p>The Elastic Network Adapter associated with the task if the task uses the
+     * <p>The Elastic Network Adapter that's associated with the task if the task uses the
      * 				<code>awsvpc</code> network mode.</p>
      */
     attachments?: Attachment[];
@@ -6081,11 +6151,11 @@ export interface Task {
      */
     attributes?: Attribute[];
     /**
-     * <p>The availability zone of the task.</p>
+     * <p>The Availability Zone for the task.</p>
      */
     availabilityZone?: string;
     /**
-     * <p>The capacity provider associated with the task.</p>
+     * <p>The capacity provider that's associated with the task.</p>
      */
     capacityProviderName?: string;
     /**
@@ -6097,7 +6167,7 @@ export interface Task {
      */
     connectivity?: Connectivity | string;
     /**
-     * <p>The Unix timestamp for when the task last went into <code>CONNECTED</code>
+     * <p>The Unix timestamp for the time when the task last went into <code>CONNECTED</code>
      * 			status.</p>
      */
     connectivityAt?: Date;
@@ -6106,22 +6176,24 @@ export interface Task {
      */
     containerInstanceArn?: string;
     /**
-     * <p>The containers associated with the task.</p>
+     * <p>The containers that's associated with the task.</p>
      */
     containers?: Container[];
     /**
      * <p>The number of CPU units used by the task as expressed in a task definition. It can be
-     * 			expressed as an integer using CPU units, for example <code>1024</code>. It can also be
-     * 			expressed as a string using vCPUs, for example <code>1 vCPU</code> or <code>1
-     * 				vcpu</code>. String values are converted to an integer indicating the CPU units when
-     * 			the task definition is registered.</p>
-     * 		       <p>If you are using the EC2 launch type, this field is optional. Supported
-     * 			values are between <code>128</code> CPU units (<code>0.125</code> vCPUs) and
-     * 				<code>10240</code> CPU units (<code>10</code> vCPUs).</p>
-     * 		       <p>If you are using the Fargate launch type, this field is required and you
-     * 			must use one of the following values, which determines your range of supported values
-     * 			for the <code>memory</code> parameter:</p>
-     *          <ul>
+     * 			expressed as an integer using CPU units (for example, <code>1024</code>). It can also be
+     * 			expressed as a string using vCPUs (for example, <code>1 vCPU</code> or <code>1
+     * 				vcpu</code>). String values are converted to an integer that indicates the CPU units
+     * 			when the task definition is registered.</p>
+     * 		       <p>If you use the EC2 launch type, this field is optional. Supported values
+     * 			are between <code>128</code> CPU units (<code>0.125</code> vCPUs) and <code>10240</code>
+     * 			CPU units (<code>10</code> vCPUs).</p>
+     * 		       <p>If you use the Fargate launch type, this field is required. You must use
+     * 			one of the following values. These values determine the range of supported values for
+     * 			the <code>memory</code> parameter:</p>
+     * 		       <p>The CPU units cannot be less than 1 vCPU when you use Windows containers on
+     * 			Fargate.</p>
+     * 		       <ul>
      *             <li>
      *                 <p>256 (.25 vCPU) - Available <code>memory</code> values: 512 (0.5 GB), 1024 (1 GB), 2048 (2 GB)</p>
      *             </li>
@@ -6141,8 +6213,8 @@ export interface Task {
      */
     cpu?: string;
     /**
-     * <p>The Unix timestamp for when the task was created (the task entered the
-     * 				<code>PENDING</code> state).</p>
+     * <p>The Unix timestamp for the time when the task was created. More specifically, it's for
+     * 			the time when the task entered the <code>PENDING</code> state.</p>
      */
     createdAt?: Date;
     /**
@@ -6151,60 +6223,60 @@ export interface Task {
      */
     desiredStatus?: string;
     /**
-     * <p>Whether or not execute command functionality is enabled for this task. If
-     * 				<code>true</code>, this enables execute command functionality on all containers in
+     * <p>Determines whether execute command functionality is enabled for this task. If
+     * 				<code>true</code>, execute command functionality is enabled on all the containers in
      * 			the task.</p>
      */
     enableExecuteCommand?: boolean;
     /**
-     * <p>The Unix timestamp for when the task execution stopped.</p>
+     * <p>The Unix timestamp for the time when the task execution stopped.</p>
      */
     executionStoppedAt?: Date;
     /**
-     * <p>The name of the task group associated with the task.</p>
+     * <p>The name of the task group that's associated with the task.</p>
      */
     group?: string;
     /**
-     * <p>The health status for the task, which is determined by the health of the essential
+     * <p>The health status for the task. It's determined by the health of the essential
      * 			containers in the task. If all essential containers in the task are reporting as
-     * 				<code>HEALTHY</code>, then the task status also reports as <code>HEALTHY</code>. If
-     * 			any essential containers in the task are reporting as <code>UNHEALTHY</code> or
-     * 				<code>UNKNOWN</code>, then the task status also reports as <code>UNHEALTHY</code> or
-     * 				<code>UNKNOWN</code>, accordingly.</p>
+     * 				<code>HEALTHY</code>, the task status also reports as <code>HEALTHY</code>. If any
+     * 			essential containers in the task are reporting as <code>UNHEALTHY</code> or
+     * 				<code>UNKNOWN</code>, the task status also reports as <code>UNHEALTHY</code> or
+     * 				<code>UNKNOWN</code>.</p>
      * 		       <note>
-     * 			         <p>The Amazon ECS container agent does not monitor or report on Docker health checks that
-     * 				are embedded in a container image (such as those specified in a parent image or from
-     * 				the image's Dockerfile) and not specified in the container definition. Health check
-     * 				parameters that are specified in a container definition override any Docker health
-     * 				checks that exist in the container image.</p>
+     * 			         <p>The Amazon ECS container agent doesn't monitor or report on Docker health checks that
+     * 				are embedded in a container image and not specified in the container definition. For
+     * 				example, this includes those specified in a parent image or from the image's
+     * 				Dockerfile. Health check parameters that are specified in a container definition
+     * 				override any Docker health checks that are found in the container image.</p>
      * 		       </note>
      */
     healthStatus?: HealthStatus | string;
     /**
-     * <p>The Elastic Inference accelerator associated with the task.</p>
+     * <p>The Elastic Inference accelerator that's associated with the task.</p>
      */
     inferenceAccelerators?: InferenceAccelerator[];
     /**
-     * <p>The last known status of the task. For more information, see <a href="https://docs.aws.amazon.com/AmazonECS/latest/developerguide/task-lifecycle.html">Task
+     * <p>The last known status for the task. For more information, see <a href="https://docs.aws.amazon.com/AmazonECS/latest/developerguide/task-lifecycle.html">Task
      * 				Lifecycle</a>.</p>
      */
     lastStatus?: string;
     /**
-     * <p>The infrastructure on which your task is running. For more information, see <a href="https://docs.aws.amazon.com/AmazonECS/latest/developerguide/launch_types.html">Amazon ECS
+     * <p>The infrastructure where your task runs on. For more information, see <a href="https://docs.aws.amazon.com/AmazonECS/latest/developerguide/launch_types.html">Amazon ECS
      * 				launch types</a> in the <i>Amazon Elastic Container Service Developer Guide</i>.</p>
      */
     launchType?: LaunchType | string;
     /**
-     * <p>The amount of memory (in MiB) used by the task as expressed in a task definition. It
-     * 			can be expressed as an integer using MiB, for example <code>1024</code>. It can also be
-     * 			expressed as a string using GB, for example <code>1GB</code> or <code>1 GB</code>.
-     * 			String values are converted to an integer indicating the MiB when the task definition is
+     * <p>The amount of memory (in MiB) that the task uses as expressed in a task definition. It
+     * 			can be expressed as an integer using MiB (for example, <code>1024</code>). If it's
+     * 			expressed as a string using GB (for example, <code>1GB</code> or <code>1 GB</code>),
+     * 			it's converted to an integer indicating the MiB when the task definition is
      * 			registered.</p>
-     * 		       <p>If you are using the EC2 launch type, this field is optional.</p>
-     * 		       <p>If you are using the Fargate launch type, this field is required and you
-     * 			must use one of the following values, which determines your range of supported values
-     * 			for the <code>cpu</code> parameter:</p>
-     *          <ul>
+     * 		       <p>If you use the EC2 launch type, this field is optional.</p>
+     * 		       <p>If you use the Fargate launch type, this field is required. You must use
+     * 			one of the following values. The value that you choose determines the range of supported
+     * 			values for the <code>cpu</code> parameter.</p>
+     * 		       <ul>
      *             <li>
      *                 <p>512 (0.5 GB), 1024 (1 GB), 2048 (2 GB) - Available <code>cpu</code> values: 256 (.25 vCPU)</p>
      *             </li>
@@ -6228,45 +6300,48 @@ export interface Task {
      */
     overrides?: TaskOverride;
     /**
-     * <p>The platform version on which your task is running. A platform version is only
-     * 			specified for tasks using the Fargate launch type. If one is not
-     * 			specified, the <code>LATEST</code> platform version is used by default. For more
-     * 			information, see <a href="https://docs.aws.amazon.com/AmazonECS/latest/developerguide/platform_versions.html">Fargate Platform
-     * 				Versions</a> in the <i>Amazon Elastic Container Service Developer Guide</i>.</p>
+     * <p>The platform version where your task runs on. A platform version is only specified for
+     * 			tasks that use the Fargate launch type. If you didn't specify one, the
+     * 				<code>LATEST</code> platform version is used. For more information, see <a href="https://docs.aws.amazon.com/AmazonECS/latest/developerguide/platform_versions.html">Fargate Platform Versions</a> in the
+     * 			<i>Amazon Elastic Container Service Developer Guide</i>.</p>
      */
     platformVersion?: string;
     /**
-     * <p>The operating system  that your tasks are running on. A platform family is specified only for tasks using the Fargate launch type. </p>
-     * 		       <p> All tasks that run as part of this service must use the same <code>platformFamily</code> value as the service, for example, <code>LINUX.</code>.</p>
+     * <p>The operating system that your tasks are running on. A platform family is specified
+     * 			only for tasks that use the Fargate launch type. </p>
+     * 		       <p> All tasks that run as part of this service must use the same
+     * 				<code>platformFamily</code> value as the service (for example,
+     * 			<code>LINUX.</code>).</p>
      */
     platformFamily?: string;
     /**
-     * <p>The Unix timestamp for when the container image pull began.</p>
+     * <p>The Unix timestamp for the time when the container image pull began.</p>
      */
     pullStartedAt?: Date;
     /**
-     * <p>The Unix timestamp for when the container image pull completed.</p>
+     * <p>The Unix timestamp for the time when the container image pull completed.</p>
      */
     pullStoppedAt?: Date;
     /**
-     * <p>The Unix timestamp for when the task started (the task transitioned from the
-     * 				<code>PENDING</code> state to the <code>RUNNING</code> state).</p>
+     * <p>The Unix timestamp for the time when the task started. More specifically, it's for the
+     * 			time when the task transitioned from the <code>PENDING</code> state to the
+     * 				<code>RUNNING</code> state.</p>
      */
     startedAt?: Date;
     /**
-     * <p>The tag specified when a task is started. If the task is started by an Amazon ECS service,
-     * 			then the <code>startedBy</code> parameter contains the deployment ID of the service that
-     * 			starts it.</p>
+     * <p>The tag specified when a task is started. If an Amazon ECS service started the task, the
+     * 				<code>startedBy</code> parameter contains the deployment ID of that service.</p>
      */
     startedBy?: string;
     /**
-     * <p>The stop code indicating why a task was stopped. The <code>stoppedReason</code> may
+     * <p>The stop code indicating why a task was stopped. The <code>stoppedReason</code> might
      * 			contain additional details.</p>
      */
     stopCode?: TaskStopCode | string;
     /**
-     * <p>The Unix timestamp for when the task was stopped (the task transitioned from the
-     * 				<code>RUNNING</code> state to the <code>STOPPED</code> state).</p>
+     * <p>The Unix timestamp for the time when the task was stopped. More specifically, it's for
+     * 			the time when the task transitioned from the <code>RUNNING</code> state to the
+     * 				<code>STOPPED</code> state.</p>
      */
     stoppedAt?: Date;
     /**
@@ -6274,13 +6349,15 @@ export interface Task {
      */
     stoppedReason?: string;
     /**
-     * <p>The Unix timestamp for when the task stops (transitions from the <code>RUNNING</code>
-     * 			state to <code>STOPPED</code>).</p>
+     * <p>The Unix timestamp for the time when the task stops. More specifically, it's for the
+     * 			time when the task transitions from the <code>RUNNING</code> state to
+     * 				<code>STOPPED</code>.</p>
      */
     stoppingAt?: Date;
     /**
-     * <p>The metadata that you apply to the task to help you categorize and organize them. Each
-     * 			tag consists of a key and an optional value, both of which you define.</p>
+     * <p>The metadata that you apply to the task to help you categorize and organize the task.
+     * 			Each tag consists of a key and an optional value. You define both the key and
+     * 			value.</p>
      * 		       <p>The following basic restrictions apply to tags:</p>
      *         <ul>
      *             <li>
@@ -6323,9 +6400,9 @@ export interface Task {
      */
     taskDefinitionArn?: string;
     /**
-     * <p>The version counter for the task. Every time a task experiences a change that triggers
-     * 			a CloudWatch event, the version counter is incremented. If you are replicating your Amazon ECS task
-     * 			state with CloudWatch Events, you can compare the version of a task reported by the Amazon ECS API
+     * <p>The version counter for the task. Every time a task experiences a change that starts a
+     * 			CloudWatch event, the version counter is incremented. If you replicate your Amazon ECS task state
+     * 			with CloudWatch Events, you can compare the version of a task reported by the Amazon ECS API
      * 			actions with the version reported in CloudWatch Events for the task (inside the
      * 				<code>detail</code> object) to verify that the version in your event stream is
      * 			current.</p>
@@ -6378,7 +6455,7 @@ export interface DescribeTaskSetsRequest {
     taskSets?: string[];
     /**
      * <p>Specifies whether to see the resource tags for the task set. If <code>TAGS</code> is
-     * 			specified, the tags are included in the response. If this field is omitted, tags are not
+     * 			specified, the tags are included in the response. If this field is omitted, tags aren't
      * 			included in the response.</p>
      */
     include?: (TaskSetField | string)[];
@@ -6412,8 +6489,8 @@ export interface DiscoverPollEndpointRequest {
      */
     containerInstance?: string;
     /**
-     * <p>The short name or full Amazon Resource Name (ARN) of the cluster to which the container instance
-     * 			belongs.</p>
+     * <p>The short name or full Amazon Resource Name (ARN) of the cluster that the container instance belongs
+     * 			to.</p>
      */
     cluster?: string;
 }
@@ -6470,7 +6547,7 @@ export declare namespace ExecuteCommandRequest {
     const filterSensitiveLog: (obj: ExecuteCommandRequest) => any;
 }
 /**
- * <p>The details of the execute command session.</p>
+ * <p>The details for the execute command session.</p>
  */
 export interface Session {
     /**
@@ -6478,12 +6555,14 @@ export interface Session {
      */
     sessionId?: string;
     /**
-     * <p>A URL back to managed agent on the container that the SSM Session Manager client uses
-     * 			to send commands and receive output from the container.</p>
+     * <p>A URL
+     * 			back
+     * 			to managed agent on the container that the SSM Session Manager client
+     * 			uses to send commands and receive output from the container.</p>
      */
     streamUrl?: string;
     /**
-     * <p>An encrypted token value containing session and caller information. Used to
+     * <p>An encrypted token value containing session and caller information. It's used to
      * 			authenticate the connection to the container.</p>
      */
     tokenValue?: string;
@@ -6508,9 +6587,9 @@ export interface ExecuteCommandResponse {
      */
     containerName?: string;
     /**
-     * <p>Whether or not the execute command session is running in interactive mode. Amazon ECS only
-     * 			supports initiating interactive sessions, so you must specify <code>true</code> for this
-     * 			value.</p>
+     * <p>Determines whether the execute command session is running in interactive mode. Amazon ECS
+     * 			only supports initiating interactive sessions, so you must specify <code>true</code> for
+     * 			this value.</p>
      */
     interactive?: boolean;
     /**
@@ -6530,7 +6609,7 @@ export declare namespace ExecuteCommandResponse {
     const filterSensitiveLog: (obj: ExecuteCommandResponse) => any;
 }
 /**
- * <p>The target container is not properly configured with the execute command agent or the
+ * <p>The target container isn't properly configured with the execute command agent or the
  * 			container is no longer active or running.</p>
  */
 export interface TargetNotConnectedException extends __SmithyException, $MetadataBearer {
@@ -6550,8 +6629,8 @@ export interface ListAccountSettingsRequest {
      */
     name?: SettingName | string;
     /**
-     * <p>The value of the account settings with which to filter results. You must also specify
-     * 			an account setting name to use this parameter.</p>
+     * <p>The value of the account settings to filter results with. You must also specify an
+     * 			account setting name to use this parameter.</p>
      */
     value?: string;
     /**
@@ -6565,18 +6644,18 @@ export interface ListAccountSettingsRequest {
      */
     principalArn?: string;
     /**
-     * <p>Specifies whether to return the effective settings. If <code>true</code>, the account
+     * <p>Determines whether to return the effective settings. If <code>true</code>, the account
      * 			settings for the root user or the default setting for the <code>principalArn</code> are
      * 			returned. If <code>false</code>, the account settings for the <code>principalArn</code>
-     * 			are returned if they are set. Otherwise, no account settings are returned.</p>
+     * 			are returned if they're set. Otherwise, no account settings are returned.</p>
      */
     effectiveSettings?: boolean;
     /**
      * <p>The <code>nextToken</code> value returned from a <code>ListAccountSettings</code>
      * 			request indicating that more results are available to fulfill the request and further
-     * 			calls will be needed. If <code>maxResults</code> was provided, it is possible the number
+     * 			calls will be needed. If <code>maxResults</code> was provided, it's possible the number
      * 			of results to be fewer than <code>maxResults</code>.</p>
-     *          <note>
+     * 		       <note>
      *             <p>This token should be treated as an opaque identifier that is only used to
      *                 retrieve the next items in a list and not for other programmatic purposes.</p>
      *         </note>
@@ -6590,7 +6669,7 @@ export interface ListAccountSettingsRequest {
      * 			of the initial request can be seen by sending another <code>ListAccountSettings</code>
      * 			request with the returned <code>nextToken</code> value. This value can be between
      * 			1 and 10. If this
-     * 			parameter is not used, then <code>ListAccountSettings</code> returns up to
+     * 			parameter isn't used, then <code>ListAccountSettings</code> returns up to
      * 			10 results and a <code>nextToken</code> value
      * 			if applicable.</p>
      */
@@ -6629,37 +6708,37 @@ export interface ListAttributesRequest {
      */
     cluster?: string;
     /**
-     * <p>The type of the target with which to list attributes.</p>
+     * <p>The type of the target to list attributes with.</p>
      */
     targetType: TargetType | string | undefined;
     /**
-     * <p>The name of the attribute with which to filter the results. </p>
+     * <p>The name of the attribute to filter the results with. </p>
      */
     attributeName?: string;
     /**
-     * <p>The value of the attribute with which to filter results. You must also specify an
-     * 			attribute name to use this parameter.</p>
+     * <p>The value of the attribute to filter results with. You must also specify an attribute
+     * 			name to use this parameter.</p>
      */
     attributeValue?: string;
     /**
      * <p>The <code>nextToken</code> value returned from a <code>ListAttributes</code> request
-     * 			indicating that more results are available to fulfill the request and further calls will
-     * 			be needed. If <code>maxResults</code> was provided, it is possible the number of results
-     * 			to be fewer than <code>maxResults</code>.</p>
-     *          <note>
+     * 			indicating that more results are available to fulfill the request and further calls are
+     * 			needed. If <code>maxResults</code> was provided, it's possible the number of results to
+     * 			be fewer than <code>maxResults</code>.</p>
+     * 		       <note>
      *             <p>This token should be treated as an opaque identifier that is only used to
      *                 retrieve the next items in a list and not for other programmatic purposes.</p>
      *         </note>
      */
     nextToken?: string;
     /**
-     * <p>The maximum number of cluster results returned by <code>ListAttributes</code> in
+     * <p>The maximum number of cluster results that <code>ListAttributes</code> returned in
      * 			paginated output. When this parameter is used, <code>ListAttributes</code> only returns
      * 				<code>maxResults</code> results in a single page along with a <code>nextToken</code>
      * 			response element. The remaining results of the initial request can be seen by sending
      * 			another <code>ListAttributes</code> request with the returned <code>nextToken</code>
      * 			value. This value can be between 1 and 100. If this
-     * 			parameter is not used, then <code>ListAttributes</code> returns up to
+     * 			parameter isn't used, then <code>ListAttributes</code> returns up to
      * 			100 results and a <code>nextToken</code> value if applicable.</p>
      */
     maxResults?: number;
@@ -6693,24 +6772,24 @@ export declare namespace ListAttributesResponse {
 export interface ListClustersRequest {
     /**
      * <p>The <code>nextToken</code> value returned from a <code>ListClusters</code> request
-     * 			indicating that more results are available to fulfill the request and further calls will
-     * 			be needed. If <code>maxResults</code> was provided, it is possible the number of results
-     * 			to be fewer than <code>maxResults</code>.</p>
-     *          <note>
+     * 			indicating that more results are available to fulfill the request and further calls are
+     * 			needed. If <code>maxResults</code> was provided, it's possible the number of results to
+     * 			be fewer than <code>maxResults</code>.</p>
+     * 		       <note>
      *             <p>This token should be treated as an opaque identifier that is only used to
      *                 retrieve the next items in a list and not for other programmatic purposes.</p>
      *         </note>
      */
     nextToken?: string;
     /**
-     * <p>The maximum number of cluster results returned by <code>ListClusters</code> in
+     * <p>The maximum number of cluster results that <code>ListClusters</code> returned in
      * 			paginated output. When this parameter is used, <code>ListClusters</code> only returns
      * 				<code>maxResults</code> results in a single page along with a <code>nextToken</code>
      * 			response element. The remaining results of the initial request can be seen by sending
      * 			another <code>ListClusters</code> request with the returned <code>nextToken</code>
      * 			value. This value can be between 1 and 100. If this
-     * 			parameter is not used, then <code>ListClusters</code> returns up to
-     * 			100 results and a <code>nextToken</code> value if applicable.</p>
+     * 			parameter isn't used, then <code>ListClusters</code> returns up to 100
+     * 			results and a <code>nextToken</code> value if applicable.</p>
      */
     maxResults?: number;
 }
@@ -6722,7 +6801,7 @@ export declare namespace ListClustersRequest {
 }
 export interface ListClustersResponse {
     /**
-     * <p>The list of full Amazon Resource Name (ARN) entries for each cluster associated with your
+     * <p>The list of full Amazon Resource Name (ARN) entries for each cluster that's associated with your
      * 			account.</p>
      */
     clusterArns?: string[];
@@ -6763,31 +6842,32 @@ export interface ListContainerInstancesRequest {
     /**
      * <p>The <code>nextToken</code> value returned from a <code>ListContainerInstances</code>
      * 			request indicating that more results are available to fulfill the request and further
-     * 			calls will be needed. If <code>maxResults</code> was provided, it is possible the number
-     * 			of results to be fewer than <code>maxResults</code>.</p>
-     *          <note>
+     * 			calls are needed. If <code>maxResults</code> was provided, it's possible the number of
+     * 			results to be fewer than <code>maxResults</code>.</p>
+     * 		       <note>
      *             <p>This token should be treated as an opaque identifier that is only used to
      *                 retrieve the next items in a list and not for other programmatic purposes.</p>
      *         </note>
      */
     nextToken?: string;
     /**
-     * <p>The maximum number of container instance results returned by
-     * 				<code>ListContainerInstances</code> in paginated output. When this parameter is
-     * 			used, <code>ListContainerInstances</code> only returns <code>maxResults</code> results
-     * 			in a single page along with a <code>nextToken</code> response element. The remaining
-     * 			results of the initial request can be seen by sending another
-     * 				<code>ListContainerInstances</code> request with the returned <code>nextToken</code>
-     * 			value. This value can be between 1 and 100. If this
-     * 			parameter is not used, then <code>ListContainerInstances</code> returns up to
-     * 			100 results and a <code>nextToken</code> value if applicable.</p>
+     * <p>The maximum number of container instance results that
+     * 				<code>ListContainerInstances</code> returned in paginated output. When this
+     * 			parameter is used, <code>ListContainerInstances</code> only returns
+     * 				<code>maxResults</code> results in a single page along with a <code>nextToken</code>
+     * 			response element. The remaining results of the initial request can be seen by sending
+     * 			another <code>ListContainerInstances</code> request with the returned
+     * 				<code>nextToken</code> value. This value can be between 1 and
+     * 			100. If this parameter isn't used, then
+     * 				<code>ListContainerInstances</code> returns up to 100 results and
+     * 			a <code>nextToken</code> value if applicable.</p>
      */
     maxResults?: number;
     /**
      * <p>Filters the container instances by status. For example, if you specify the
      * 				<code>DRAINING</code> status, the results include only container instances that have
      * 			been set to <code>DRAINING</code> using <a>UpdateContainerInstancesState</a>.
-     * 			If you do not specify this parameter, the default is to include container instances set
+     * 			If you don't specify this parameter, the default is to include container instances set
      * 			to all states other than <code>INACTIVE</code>.</p>
      */
     status?: ContainerInstanceStatus | string;
@@ -6830,20 +6910,20 @@ export interface ListServicesRequest {
      * 			indicating that more results are available to fulfill the request and further calls will
      * 			be needed. If <code>maxResults</code> was provided, it is possible the number of results
      * 			to be fewer than <code>maxResults</code>.</p>
-     *          <note>
+     * 		       <note>
      *             <p>This token should be treated as an opaque identifier that is only used to
      *                 retrieve the next items in a list and not for other programmatic purposes.</p>
      *         </note>
      */
     nextToken?: string;
     /**
-     * <p>The maximum number of service results returned by <code>ListServices</code> in
+     * <p>The maximum number of service results that <code>ListServices</code> returned in
      * 			paginated output. When this parameter is used, <code>ListServices</code> only returns
      * 				<code>maxResults</code> results in a single page along with a <code>nextToken</code>
      * 			response element. The remaining results of the initial request can be seen by sending
      * 			another <code>ListServices</code> request with the returned <code>nextToken</code>
      * 			value. This value can be between 1 and 100. If
-     * 			this parameter is not used, then <code>ListServices</code> returns up to
+     * 			this parameter isn't used, then <code>ListServices</code> returns up to
      * 			10 results and a <code>nextToken</code> value if
      * 			applicable.</p>
      */
@@ -6866,7 +6946,7 @@ export declare namespace ListServicesRequest {
 }
 export interface ListServicesResponse {
     /**
-     * <p>The list of full ARN entries for each service associated with the specified
+     * <p>The list of full ARN entries for each service that's associated with the specified
      * 			cluster.</p>
      */
     serviceArns?: string[];
@@ -6887,7 +6967,7 @@ export declare namespace ListServicesResponse {
 }
 export interface ListTagsForResourceRequest {
     /**
-     * <p>The Amazon Resource Name (ARN) that identifies the resource for which to list the tags. Currently, the
+     * <p>The Amazon Resource Name (ARN) that identifies the resource to list the tags for. Currently, the
      * 			supported resources are Amazon ECS tasks, services, task definitions, clusters, and container
      * 			instances.</p>
      */
@@ -6918,15 +6998,15 @@ export declare enum TaskDefinitionFamilyStatus {
 }
 export interface ListTaskDefinitionFamiliesRequest {
     /**
-     * <p>The <code>familyPrefix</code> is a string that is used to filter the results of
+     * <p>The <code>familyPrefix</code> is a string that's used to filter the results of
      * 				<code>ListTaskDefinitionFamilies</code>. If you specify a <code>familyPrefix</code>,
      * 			only task definition family names that begin with the <code>familyPrefix</code> string
      * 			are returned.</p>
      */
     familyPrefix?: string;
     /**
-     * <p>The task definition family status with which to filter the
-     * 				<code>ListTaskDefinitionFamilies</code> results. By default, both
+     * <p>The task definition family status to filter the
+     * 				<code>ListTaskDefinitionFamilies</code> results with. By default, both
      * 				<code>ACTIVE</code> and <code>INACTIVE</code> task definition families are listed.
      * 			If this parameter is set to <code>ACTIVE</code>, only task definition families that have
      * 			an <code>ACTIVE</code> task definition revision are returned. If this parameter is set
@@ -6942,21 +7022,21 @@ export interface ListTaskDefinitionFamiliesRequest {
      * 			available to fulfill the request and further calls will be needed. If
      * 				<code>maxResults</code> was provided, it is possible the number of results to be
      * 			fewer than <code>maxResults</code>.</p>
-     *          <note>
+     * 		       <note>
      *             <p>This token should be treated as an opaque identifier that is only used to
      *                 retrieve the next items in a list and not for other programmatic purposes.</p>
      *         </note>
      */
     nextToken?: string;
     /**
-     * <p>The maximum number of task definition family results returned by
-     * 				<code>ListTaskDefinitionFamilies</code> in paginated output. When this parameter is
-     * 			used, <code>ListTaskDefinitions</code> only returns <code>maxResults</code> results in a
-     * 			single page along with a <code>nextToken</code> response element. The remaining results
-     * 			of the initial request can be seen by sending another
+     * <p>The maximum number of task definition family results that
+     * 				<code>ListTaskDefinitionFamilies</code> returned in paginated output. When this
+     * 			parameter is used, <code>ListTaskDefinitions</code> only returns <code>maxResults</code>
+     * 			results in a single page along with a <code>nextToken</code> response element. The
+     * 			remaining results of the initial request can be seen by sending another
      * 				<code>ListTaskDefinitionFamilies</code> request with the returned
      * 				<code>nextToken</code> value. This value can be between 1 and
-     * 			100. If this parameter is not used, then
+     * 			100. If this parameter isn't used, then
      * 				<code>ListTaskDefinitionFamilies</code> returns up to 100 results
      * 			and a <code>nextToken</code> value if applicable.</p>
      */
@@ -6995,27 +7075,27 @@ export declare enum SortOrder {
 }
 export interface ListTaskDefinitionsRequest {
     /**
-     * <p>The full family name with which to filter the <code>ListTaskDefinitions</code>
-     * 			results. Specifying a <code>familyPrefix</code> limits the listed task definitions to
-     * 			task definition revisions that belong to that family.</p>
+     * <p>The full family name to filter the <code>ListTaskDefinitions</code> results with.
+     * 			Specifying a <code>familyPrefix</code> limits the listed task definitions to task
+     * 			definition revisions that belong to that family.</p>
      */
     familyPrefix?: string;
     /**
-     * <p>The task definition status with which to filter the <code>ListTaskDefinitions</code>
-     * 			results. By default, only <code>ACTIVE</code> task definitions are listed. By setting
-     * 			this parameter to <code>INACTIVE</code>, you can view task definitions that are
+     * <p>The task definition status to filter the <code>ListTaskDefinitions</code> results
+     * 			with. By default, only <code>ACTIVE</code> task definitions are listed. By setting this
+     * 			parameter to <code>INACTIVE</code>, you can view task definitions that are
      * 				<code>INACTIVE</code> as long as an active task or service still references them. If
      * 			you paginate the resulting output, be sure to keep the <code>status</code> value
      * 			constant in each subsequent request.</p>
      */
     status?: TaskDefinitionStatus | string;
     /**
-     * <p>The order in which to sort the results. Valid values are <code>ASC</code> and
-     * 				<code>DESC</code>. By default (<code>ASC</code>), task definitions are listed
+     * <p>The order to sort the results in. Valid values are <code>ASC</code> and
+     * 				<code>DESC</code>. By default, (<code>ASC</code>) task definitions are listed
      * 			lexicographically by family name and in ascending numerical order by revision so that
      * 			the newest task definitions in a family are listed last. Setting this parameter to
-     * 				<code>DESC</code> reverses the sort order on family name and revision so that the
-     * 			newest task definitions in a family are listed first.</p>
+     * 				<code>DESC</code> reverses the sort order on family name and revision. This is so
+     * 			that the newest task definitions in a family are listed first.</p>
      */
     sort?: SortOrder | string;
     /**
@@ -7023,20 +7103,20 @@ export interface ListTaskDefinitionsRequest {
      * 			request indicating that more results are available to fulfill the request and further
      * 			calls will be needed. If <code>maxResults</code> was provided, it is possible the number
      * 			of results to be fewer than <code>maxResults</code>.</p>
-     *          <note>
+     * 		       <note>
      *             <p>This token should be treated as an opaque identifier that is only used to
      *                 retrieve the next items in a list and not for other programmatic purposes.</p>
      *         </note>
      */
     nextToken?: string;
     /**
-     * <p>The maximum number of task definition results returned by
-     * 				<code>ListTaskDefinitions</code> in paginated output. When this parameter is used,
+     * <p>The maximum number of task definition results that <code>ListTaskDefinitions</code>
+     * 			returned in paginated output. When this parameter is used,
      * 				<code>ListTaskDefinitions</code> only returns <code>maxResults</code> results in a
      * 			single page along with a <code>nextToken</code> response element. The remaining results
      * 			of the initial request can be seen by sending another <code>ListTaskDefinitions</code>
      * 			request with the returned <code>nextToken</code> value. This value can be between
-     * 			1 and 100. If this parameter is not used, then
+     * 			1 and 100. If this parameter isn't used, then
      * 				<code>ListTaskDefinitions</code> returns up to 100 results and a
      * 				<code>nextToken</code> value if applicable.</p>
      */
@@ -7096,27 +7176,27 @@ export interface ListTasksRequest {
     /**
      * <p>The <code>nextToken</code> value returned from a <code>ListTasks</code> request
      * 			indicating that more results are available to fulfill the request and further calls will
-     * 			be needed. If <code>maxResults</code> was provided, it is possible the number of results
+     * 			be needed. If <code>maxResults</code> was provided, it's possible the number of results
      * 			to be fewer than <code>maxResults</code>.</p>
-     *          <note>
+     * 		       <note>
      *             <p>This token should be treated as an opaque identifier that is only used to
      *                 retrieve the next items in a list and not for other programmatic purposes.</p>
      *         </note>
      */
     nextToken?: string;
     /**
-     * <p>The maximum number of task results returned by <code>ListTasks</code> in paginated
+     * <p>The maximum number of task results that <code>ListTasks</code> returned in paginated
      * 			output. When this parameter is used, <code>ListTasks</code> only returns
      * 				<code>maxResults</code> results in a single page along with a <code>nextToken</code>
      * 			response element. The remaining results of the initial request can be seen by sending
      * 			another <code>ListTasks</code> request with the returned <code>nextToken</code> value.
-     * 			This value can be between 1 and 100. If this parameter is
-     * 			not used, then <code>ListTasks</code> returns up to 100 results and a
-     * 				<code>nextToken</code> value if applicable.</p>
+     * 			This value can be between 1 and 100. If this parameter
+     * 			isn't used, then <code>ListTasks</code> returns up to 100 results and
+     * 			a <code>nextToken</code> value if applicable.</p>
      */
     maxResults?: number;
     /**
-     * <p>The <code>startedBy</code> value with which to filter the task results. Specifying a
+     * <p>The <code>startedBy</code> value to filter the task results with. Specifying a
      * 				<code>startedBy</code> value limits the results to tasks that were started with that
      * 			value.</p>
      */
@@ -7131,12 +7211,12 @@ export interface ListTasksRequest {
      * <p>The task desired status to use when filtering the <code>ListTasks</code> results.
      * 			Specifying a <code>desiredStatus</code> of <code>STOPPED</code> limits the results to
      * 			tasks that Amazon ECS has set the desired status to <code>STOPPED</code>. This can be useful
-     * 			for debugging tasks that are not starting properly or have died or finished. The default
+     * 			for debugging tasks that aren't starting properly or have died or finished. The default
      * 			status filter is <code>RUNNING</code>, which shows tasks that Amazon ECS has set the desired
      * 			status to <code>RUNNING</code>.</p>
      * 		       <note>
      * 			         <p>Although you can filter results based on a desired status of <code>PENDING</code>,
-     * 				this does not return any results. Amazon ECS never sets the desired status of a task to
+     * 				this doesn't return any results. Amazon ECS never sets the desired status of a task to
      * 				that value (only a task's <code>lastStatus</code> may have a value of
      * 					<code>PENDING</code>).</p>
      * 		       </note>
@@ -7259,9 +7339,9 @@ export declare namespace PutAccountSettingDefaultResponse {
     const filterSensitiveLog: (obj: PutAccountSettingDefaultResponse) => any;
 }
 /**
- * <p>You can apply up to 10 custom attributes per resource. You can view the attributes of
- * 			a resource with <a>ListAttributes</a>. You can remove existing attributes on
- * 			a resource with <a>DeleteAttributes</a>.</p>
+ * <p>You can apply up to 10 custom attributes for each resource. You can view the
+ * 			attributes of a resource with <a>ListAttributes</a>. You can remove existing
+ * 			attributes on a resource with <a>DeleteAttributes</a>.</p>
  */
 export interface AttributeLimitExceededException extends __SmithyException, $MetadataBearer {
     name: "AttributeLimitExceededException";
@@ -7282,7 +7362,7 @@ export interface PutAttributesRequest {
     cluster?: string;
     /**
      * <p>The attributes to apply to your resource. You can specify up to 10 custom attributes
-     * 			per resource. You can specify up to 10 attributes in a single call.</p>
+     * 			for each resource. You can specify up to 10 attributes in a single call.</p>
      */
     attributes: Attribute[] | undefined;
 }
@@ -7307,7 +7387,7 @@ export declare namespace PutAttributesResponse {
 export interface PutClusterCapacityProvidersRequest {
     /**
      * <p>The short name or full Amazon Resource Name (ARN) of the cluster to modify the capacity provider
-     * 			settings for. If you do not specify a cluster, the default cluster is assumed.</p>
+     * 			settings for. If you don't specify a cluster, the default cluster is assumed.</p>
      */
     cluster: string | undefined;
     /**
@@ -7359,7 +7439,7 @@ export declare namespace PutClusterCapacityProvidersResponse {
     const filterSensitiveLog: (obj: PutClusterCapacityProvidersResponse) => any;
 }
 /**
- * <p>The specified resource is in-use and cannot be removed.</p>
+ * <p>The specified resource is in-use and can't be removed.</p>
  */
 export interface ResourceInUseException extends __SmithyException, $MetadataBearer {
     name: "ResourceInUseException";
@@ -7381,13 +7461,13 @@ export declare enum PlatformDeviceType {
  */
 export interface PlatformDevice {
     /**
-     * <p>The ID for the GPU(s) on the container instance. The available GPU IDs can also be
+     * <p>The ID for the GPUs on the container instance. The available GPU IDs can also be
      * 			obtained on the container instance in the
      * 				<code>/var/lib/ecs/gpu/nvidia_gpu_info.json</code> file.</p>
      */
     id: string | undefined;
     /**
-     * <p>The type of device that is available on the container instance. The only supported
+     * <p>The type of device that's available on the container instance. The only supported
      * 			value is <code>GPU</code>.</p>
      */
     type: PlatformDeviceType | string | undefined;
@@ -7400,8 +7480,8 @@ export declare namespace PlatformDevice {
 }
 export interface RegisterContainerInstanceRequest {
     /**
-     * <p>The short name or full Amazon Resource Name (ARN) of the cluster with which to register your container
-     * 			instance. If you do not specify a cluster, the default cluster is assumed.</p>
+     * <p>The short name or full Amazon Resource Name (ARN) of the cluster to register your container instance
+     * 			with. If you do not specify a cluster, the default cluster is assumed.</p>
      */
     cluster?: string;
     /**
@@ -7423,8 +7503,8 @@ export interface RegisterContainerInstanceRequest {
      */
     totalResources?: Resource[];
     /**
-     * <p>The version information for the Amazon ECS container agent and Docker daemon running on the
-     * 			container instance.</p>
+     * <p>The version information for the Amazon ECS container agent and Docker daemon that runs on
+     * 			the container instance.</p>
      */
     versionInfo?: VersionInfo;
     /**
@@ -7442,9 +7522,8 @@ export interface RegisterContainerInstanceRequest {
     platformDevices?: PlatformDevice[];
     /**
      * <p>The metadata that you apply to the container instance to help you categorize and
-     * 			organize them. Each tag consists of a key and an optional value, both of which you
-     * 			define.</p>
-     *          <p>The following basic restrictions apply to tags:</p>
+     * 			organize them. Each tag consists of a key and an optional value. You define both.</p>
+     * 		       <p>The following basic restrictions apply to tags:</p>
      *         <ul>
      *             <li>
      *                 <p>Maximum number of tags per resource - 50</p>
@@ -7498,9 +7577,9 @@ export declare namespace RegisterContainerInstanceResponse {
 }
 export interface RegisterTaskDefinitionRequest {
     /**
-     * <p>You must specify a <code>family</code> for a task definition, which allows you to
-     * 			track multiple versions of the same task definition. The <code>family</code> is used as
-     * 			a name for your task definition. Up to 255 letters (uppercase and lowercase), numbers, underscores, and hyphens are allowed.</p>
+     * <p>You must specify a <code>family</code> for a task definition. You can use it track
+     * 			multiple versions of the same task definition. The <code>family</code> is used as a name
+     * 			for your task definition. Up to 255 letters (uppercase and lowercase), numbers, underscores, and hyphens are allowed.</p>
      */
     family: string | undefined;
     /**
@@ -7554,18 +7633,18 @@ export interface RegisterTaskDefinitionRequest {
      */
     containerDefinitions: ContainerDefinition[] | undefined;
     /**
-     * <p>A list of volume definitions in JSON format that containers in your task may
+     * <p>A list of volume definitions in JSON format that containers in your task might
      * 			use.</p>
      */
     volumes?: Volume[];
     /**
      * <p>An array of placement constraint objects to use for the task. You can specify a
-     * 			maximum of 10 constraints per task (this limit includes constraints in the task
-     * 			definition and those specified at runtime).</p>
+     * 			maximum of 10 constraints for each task. This limit includes constraints in the task
+     * 			definition and those specified at runtime.</p>
      */
     placementConstraints?: TaskDefinitionPlacementConstraint[];
     /**
-     * <p>The task launch type that Amazon ECS should validate the task definition against. A client
+     * <p>The task launch type that Amazon ECS validates the task definition against. A client
      * 			exception is returned if the task definition doesn't validate against the
      * 			compatibilities specified. If no value is specified, the parameter is omitted from the
      * 			response.</p>
@@ -7573,21 +7652,23 @@ export interface RegisterTaskDefinitionRequest {
     requiresCompatibilities?: (Compatibility | string)[];
     /**
      * <p>The number of CPU units used by the task. It can be expressed as an integer using CPU
-     * 			units, for example <code>1024</code>, or as a string using vCPUs, for example <code>1
-     * 				vCPU</code> or <code>1 vcpu</code>, in a task definition. String values are
+     * 			units (for example, <code>1024</code>) or as a string using vCPUs (for example, <code>1
+     * 				vCPU</code> or <code>1 vcpu</code>) in a task definition. String values are
      * 			converted to an integer indicating the CPU units when the task definition is
      * 			registered.</p>
      * 		       <note>
      * 			         <p>Task-level CPU and memory parameters are ignored for Windows containers. We
      * 				recommend specifying container-level resources for Windows containers.</p>
      * 		       </note>
-     * 		       <p>If you are using the EC2 launch type, this field is optional. Supported
+     * 		       <p>If you're using the EC2 launch type, this field is optional. Supported
      * 			values are between <code>128</code> CPU units (<code>0.125</code> vCPUs) and
      * 				<code>10240</code> CPU units (<code>10</code> vCPUs).</p>
-     * 		       <p>If you are using the Fargate launch type, this field is required and you
+     * 		       <p>If you're using the Fargate launch type, this field is required and you
      * 			must use one of the following values, which determines your range of supported values
      * 			for the <code>memory</code> parameter:</p>
-     *          <ul>
+     * 		       <p>The CPU units cannot be less than 1 vCPU when you use Windows containers on
+     * 			Fargate.</p>
+     * 		       <ul>
      *             <li>
      *                 <p>256 (.25 vCPU) - Available <code>memory</code> values: 512 (0.5 GB), 1024 (1 GB), 2048 (2 GB)</p>
      *             </li>
@@ -7608,8 +7689,8 @@ export interface RegisterTaskDefinitionRequest {
     cpu?: string;
     /**
      * <p>The amount of memory (in MiB) used by the task. It can be expressed as an integer
-     * 			using MiB, for example <code>1024</code>, or as a string using GB, for example
-     * 				<code>1GB</code> or <code>1 GB</code>, in a task definition. String values are
+     * 			using MiB (for example ,<code>1024</code>) or as a string using GB (for example,
+     * 				<code>1GB</code> or <code>1 GB</code>) in a task definition. String values are
      * 			converted to an integer indicating the MiB when the task definition is
      * 			registered.</p>
      * 		       <note>
@@ -7618,9 +7699,11 @@ export interface RegisterTaskDefinitionRequest {
      * 		       </note>
      * 		       <p>If using the EC2 launch type, this field is optional.</p>
      * 		       <p>If using the Fargate launch type, this field is required and you must
-     * 			use one of the following values, which determines your range of supported values for the
-     * 				<code>cpu</code> parameter:</p>
-     *          <ul>
+     * 			use one of the following values. This determines your range of supported values for the
+     * 				<code>cpu</code> parameter.</p>
+     * 		       <p>The CPU units cannot be less than 1 vCPU when you use Windows containers on
+     * 			Fargate.</p>
+     * 		       <ul>
      *             <li>
      *                 <p>512 (0.5 GB), 1024 (1 GB), 2048 (2 GB) - Available <code>cpu</code> values: 256 (.25 vCPU)</p>
      *             </li>
@@ -7641,7 +7724,7 @@ export interface RegisterTaskDefinitionRequest {
     memory?: string;
     /**
      * <p>The metadata that you apply to the task definition to help you categorize and organize
-     * 			them. Each tag consists of a key and an optional value, both of which you define.</p>
+     * 			them. Each tag consists of a key and an optional value. You define both of them.</p>
      * 		       <p>The following basic restrictions apply to tags:</p>
      *         <ul>
      *             <li>
@@ -7750,23 +7833,24 @@ export interface RegisterTaskDefinitionRequest {
      * 			tasks hosted on Fargate. For more information, see <a href="https://docs.aws.amazon.com/AmazonECS/latest/userguide/using_data_volumes.html">Fargate task
      * 				storage</a> in the <i>Amazon ECS User Guide for Fargate</i>.</p>
      * 		       <note>
-     * 			         <p>This parameter is only supported for tasks hosted on Fargate using the following platform versions:</p>
+     * 			         <p>This parameter is only supported for tasks hosted on Fargate using
+     * 				the following platform versions:</p>
      * 			         <ul>
      *                <li>
-     * 					             <p>Linux platform
-     * 						version <code>1.4.0</code> or later.</p>
+     * 					             <p>Linux platform version <code>1.4.0</code> or later.</p>
      * 				           </li>
      *                <li>
-     * 					             <p>Windows platform
-     * 						version <code>1.0.0</code> or later.</p>
+     * 					             <p>Windows platform version <code>1.0.0</code> or later.</p>
      * 				           </li>
      *             </ul>
      * 		       </note>
      */
     ephemeralStorage?: EphemeralStorage;
     /**
-     * <p>The operating system  that your tasks definitions run on. A platform family is specified only for tasks using the Fargate launch type. </p>
-     * 		       <p>When you specify a task definition in a service, this value must match the <code>runtimePlatform</code> value of the service.</p>
+     * <p>The operating system that your tasks definitions run on. A platform family is
+     * 			specified only for tasks using the Fargate launch type. </p>
+     * 		       <p>When you specify a task definition in a service, this value must match the
+     * 				<code>runtimePlatform</code> value of the service.</p>
      */
     runtimePlatform?: RuntimePlatform;
 }
@@ -7793,7 +7877,7 @@ export declare namespace RegisterTaskDefinitionResponse {
     const filterSensitiveLog: (obj: RegisterTaskDefinitionResponse) => any;
 }
 /**
- * <p>Your Amazon Web Services account has been blocked. For more information, contact <a href="http://aws.amazon.com/contact-us/">
+ * <p>Your Amazon Web Services account was blocked. For more information, contact <a href="http://aws.amazon.com/contact-us/">
  * 				Amazon Web Services Support</a>.</p>
  */
 export interface BlockedException extends __SmithyException, $MetadataBearer {
@@ -7814,18 +7898,19 @@ export interface RunTaskRequest {
      * 			parameter must be omitted. If no <code>capacityProviderStrategy</code> or
      * 				<code>launchType</code> is specified, the
      * 				<code>defaultCapacityProviderStrategy</code> for the cluster is used.</p>
-     * 		       <p>When you use cluster auto scaling, you must specify <code>capacityProviderStrategy</code> and not <code>launchType</code>. </p>
+     * 		       <p>When you use cluster auto scaling, you must specify
+     * 				<code>capacityProviderStrategy</code> and not <code>launchType</code>. </p>
      * 		       <p>A capacity provider strategy may contain a maximum of 6 capacity providers.</p>
      */
     capacityProviderStrategy?: CapacityProviderStrategyItem[];
     /**
-     * <p>The short name or full Amazon Resource Name (ARN) of the cluster on which to run your task.
+     * <p>The short name or full Amazon Resource Name (ARN) of the cluster to run your task on.
      * 			If you do not specify a cluster, the default cluster is assumed.</p>
      */
     cluster?: string;
     /**
      * <p>The number of instantiations of the specified task to place on your cluster. You can
-     * 			specify up to 10 tasks per call.</p>
+     * 			specify up to 10 tasks for each call.</p>
      */
     count?: number;
     /**
@@ -7835,9 +7920,9 @@ export interface RunTaskRequest {
      */
     enableECSManagedTags?: boolean;
     /**
-     * <p>Whether or not to enable the execute command functionality for the containers in this
-     * 			task. If <code>true</code>, this enables execute command functionality on all containers
-     * 			in the task.</p>
+     * <p>Determines whether to enable the execute command functionality for the containers in
+     * 			this task. If <code>true</code>, this enables execute command functionality on all
+     * 			containers in the task.</p>
      */
     enableExecuteCommand?: boolean;
     /**
@@ -7846,8 +7931,8 @@ export interface RunTaskRequest {
      */
     group?: string;
     /**
-     * <p>The infrastructure on which to run your standalone task. For more information, see
-     * 				<a href="https://docs.aws.amazon.com/AmazonECS/latest/developerguide/launch_types.html">Amazon ECS launch types</a> in the <i>Amazon Elastic Container Service Developer Guide</i>.</p>
+     * <p>The infrastructure to run your standalone task on. For more information, see <a href="https://docs.aws.amazon.com/AmazonECS/latest/developerguide/launch_types.html">Amazon ECS
+     * 				launch types</a> in the <i>Amazon Elastic Container Service Developer Guide</i>.</p>
      * 		       <p>The <code>FARGATE</code> launch type runs your tasks on Fargate On-Demand
      * 			infrastructure.</p>
      * 		       <note>
@@ -7857,26 +7942,27 @@ export interface RunTaskRequest {
      * 		       </note>
      * 		       <p>The <code>EC2</code> launch type runs your tasks on Amazon EC2 instances registered to your
      * 			cluster.</p>
-     * 		       <p>The <code>EXTERNAL</code> launch type runs your tasks on your on-premise server or
+     * 		       <p>The <code>EXTERNAL</code> launch type runs your tasks on your on-premises server or
      * 			virtual machine (VM) capacity registered to your cluster.</p>
      * 		       <p>A task can use either a launch type or a capacity provider strategy. If a
      * 				<code>launchType</code> is specified, the <code>capacityProviderStrategy</code>
      * 			parameter must be omitted.</p>
-     * 		       <p>When you use cluster auto scaling, you must specify <code>capacityProviderStrategy</code> and not <code>launchType</code>. </p>
+     * 		       <p>When you use cluster auto scaling, you must specify
+     * 				<code>capacityProviderStrategy</code> and not <code>launchType</code>. </p>
      */
     launchType?: LaunchType | string;
     /**
      * <p>The network configuration for the task. This parameter is required for task
      * 			definitions that use the <code>awsvpc</code> network mode to receive their own elastic
-     * 			network interface, and it is not supported for other network modes. For more
-     * 			information, see <a href="https://docs.aws.amazon.com/AmazonECS/latest/developerguide/task-networking.html">Task networking</a>
+     * 			network interface, and it isn't supported for other network modes. For more information,
+     * 			see <a href="https://docs.aws.amazon.com/AmazonECS/latest/developerguide/task-networking.html">Task networking</a>
      * 			in the <i>Amazon Elastic Container Service Developer Guide</i>.</p>
      */
     networkConfiguration?: NetworkConfiguration;
     /**
      * <p>A list of container overrides in JSON format that specify the name of a container in
      * 			the specified task definition and the overrides it should receive. You can override the
-     * 			default command for a container (that is specified in the task definition or Docker
+     * 			default command for a container (that's specified in the task definition or Docker
      * 			image) with a <code>command</code> override. You can also override existing environment
      * 			variables (that are specified in the task definition or Docker image) on a container or
      * 			add new environment variables to it with an <code>environment</code> override.</p>
@@ -7886,25 +7972,25 @@ export interface RunTaskRequest {
     overrides?: TaskOverride;
     /**
      * <p>An array of placement constraint objects to use for the task. You can specify up to 10
-     * 			constraints per task (including constraints in the task definition and those specified
-     * 			at runtime).</p>
+     * 			constraints for each task (including constraints in the task definition and those
+     * 			specified at runtime).</p>
      */
     placementConstraints?: PlacementConstraint[];
     /**
      * <p>The placement strategy objects to use for the task. You can specify a maximum of 5
-     * 			strategy rules per task.</p>
+     * 			strategy rules for each task.</p>
      */
     placementStrategy?: PlacementStrategy[];
     /**
-     * <p>The platform version the task should use. A platform version is only specified for
-     * 			tasks hosted on Fargate. If one is not specified, the <code>LATEST</code>
-     * 			platform version is used by default. For more information, see <a href="https://docs.aws.amazon.com/AmazonECS/latest/developerguide/platform_versions.html">Fargate platform versions</a> in the
-     * 			<i>Amazon Elastic Container Service Developer Guide</i>.</p>
+     * <p>The platform version the task uses. A platform version is only specified for tasks
+     * 			hosted on Fargate. If one isn't specified, the <code>LATEST</code>
+     * 			platform version is used. For more information, see <a href="https://docs.aws.amazon.com/AmazonECS/latest/developerguide/platform_versions.html">Fargate platform
+     * 				versions</a> in the <i>Amazon Elastic Container Service Developer Guide</i>.</p>
      */
     platformVersion?: string;
     /**
      * <p>Specifies whether to propagate the tags from the task definition to the task. If no
-     * 			value is specified, the tags are not propagated. Tags can only be propagated to the task
+     * 			value is specified, the tags aren't propagated. Tags can only be propagated to the task
      * 			during task creation. To add tags to a task after task creation, use the <a>TagResource</a> API action.</p>
      * 		       <note>
      * 			         <p>An error will be received if you specify the <code>SERVICE</code> option when
@@ -7923,7 +8009,7 @@ export interface RunTaskRequest {
      * 			job to your task with the <code>startedBy</code> parameter. You can then identify which
      * 			tasks belong to that job by filtering the results of a <a>ListTasks</a> call
      * 			with the <code>startedBy</code> value. Up to 36 letters (uppercase and lowercase),
-     * 			numbers, hyphens, and underscores are allowed.</p>
+     * 			numbers, hyphens (-), and underscores (_) are allowed.</p>
      * 		       <p>If a task is started by an Amazon ECS service, then the <code>startedBy</code> parameter
      * 			contains the deployment ID of the service that starts it.</p>
      */
@@ -7966,10 +8052,11 @@ export interface RunTaskRequest {
     tags?: Tag[];
     /**
      * <p>The <code>family</code> and <code>revision</code> (<code>family:revision</code>) or
-     * 			full ARN of the task definition to run. If a <code>revision</code> is not specified,
+     * 			full ARN of the task definition to run. If a <code>revision</code> isn't specified,
      * 			the latest <code>ACTIVE</code> revision is used.</p>
-     * 		       <p>The full ARN value must match the value that you specified ias the <code>Resource</code>
-     * 			of the IAM principal's permissions policy. For example, if the <code>Resource</code> is
+     * 		       <p>The full ARN value must match the value that you specified as the
+     * 				<code>Resource</code> of the IAM principal's permissions policy. For example, if the
+     * 				<code>Resource</code> is
      * 			arn:aws:ecs:us-east-1:111122223333:task-definition/TaskFamilyName:*, the
      * 				<code>taskDefinition</code> ARN value must be
      * 				<code>arn:aws:ecs:us-east-1:111122223333:task-definition/TaskFamilyName</code>.</p>
@@ -8001,13 +8088,13 @@ export declare namespace RunTaskResponse {
 }
 export interface StartTaskRequest {
     /**
-     * <p>The short name or full Amazon Resource Name (ARN) of the cluster on which to start your task.
+     * <p>The short name or full Amazon Resource Name (ARN) of the cluster where to start your task.
      * 			If you do not specify a cluster, the default cluster is assumed.</p>
      */
     cluster?: string;
     /**
-     * <p>The container instance IDs or full ARN entries for the container instances on which
-     * 			you would like to place your task. You can specify up to 10 container instances.</p>
+     * <p>The container instance IDs or full ARN entries for the container instances where you
+     * 			would like to place your task. You can specify up to 10 container instances.</p>
      */
     containerInstances: string[] | undefined;
     /**
@@ -8034,8 +8121,8 @@ export interface StartTaskRequest {
     networkConfiguration?: NetworkConfiguration;
     /**
      * <p>A list of container overrides in JSON format that specify the name of a container in
-     * 			the specified task definition and the overrides it should receive. You can override the
-     * 			default command for a container (that is specified in the task definition or Docker
+     * 			the specified task definition and the overrides it receives. You can override the
+     * 			default command for a container (that's specified in the task definition or Docker
      * 			image) with a <code>command</code> override. You can also override existing environment
      * 			variables (that are specified in the task definition or Docker image) on a container or
      * 			add new environment variables to it with an <code>environment</code> override.</p>
@@ -8047,7 +8134,7 @@ export interface StartTaskRequest {
     overrides?: TaskOverride;
     /**
      * <p>Specifies whether to propagate the tags from the task definition or the service to the
-     * 			task. If no value is specified, the tags are not propagated.</p>
+     * 			task. If no value is specified, the tags aren't propagated.</p>
      */
     propagateTags?: PropagateTags | string;
     /**
@@ -8060,8 +8147,8 @@ export interface StartTaskRequest {
      * 			job to your task with the <code>startedBy</code> parameter. You can then identify which
      * 			tasks belong to that job by filtering the results of a <a>ListTasks</a> call
      * 			with the <code>startedBy</code> value. Up to 36 letters (uppercase and lowercase),
-     * 			numbers, hyphens, and underscores are allowed.</p>
-     * 		       <p>If a task is started by an Amazon ECS service, then the <code>startedBy</code> parameter
+     * 			numbers, hyphens (-), and underscores (_) are allowed.</p>
+     * 		       <p>If a task is started by an Amazon ECS service, the <code>startedBy</code> parameter
      * 			contains the deployment ID of the service that starts it.</p>
      */
     startedBy?: string;
@@ -8103,7 +8190,7 @@ export interface StartTaskRequest {
     tags?: Tag[];
     /**
      * <p>The <code>family</code> and <code>revision</code> (<code>family:revision</code>) or
-     * 			full ARN of the task definition to start. If a <code>revision</code> is not specified,
+     * 			full ARN of the task definition to start. If a <code>revision</code> isn't specified,
      * 			the latest <code>ACTIVE</code> revision is used.</p>
      */
     taskDefinition: string | undefined;
@@ -8142,7 +8229,7 @@ export interface StopTaskRequest {
      */
     task: string | undefined;
     /**
-     * <p>An optional message specified when a task is stopped. For example, if you are using a
+     * <p>An optional message specified when a task is stopped. For example, if you're using a
      * 			custom scheduler, you can use this parameter to specify the reason for stopping the task
      * 			here, and the message appears in subsequent <a>DescribeTasks</a> API
      * 			operations on this task. Up to 255 characters are allowed in this message.</p>
@@ -8237,7 +8324,7 @@ export interface SubmitContainerStateChangeRequest {
      */
     status?: string;
     /**
-     * <p>The exit code returned for the state change request.</p>
+     * <p>The exit code that's returned for the state change request.</p>
      */
     exitCode?: number;
     /**
@@ -8268,7 +8355,7 @@ export declare namespace SubmitContainerStateChangeResponse {
     const filterSensitiveLog: (obj: SubmitContainerStateChangeResponse) => any;
 }
 /**
- * <p>An object representing a change in state for a container.</p>
+ * <p>An object that represents a change in state for a container.</p>
  */
 export interface ContainerStateChange {
     /**
@@ -8289,7 +8376,7 @@ export interface ContainerStateChange {
      */
     exitCode?: number;
     /**
-     * <p>Any network bindings associated with the container.</p>
+     * <p>Any network bindings that are associated with the container.</p>
      */
     networkBindings?: NetworkBinding[];
     /**
@@ -8312,7 +8399,7 @@ export declare namespace ContainerStateChange {
  */
 export interface ManagedAgentStateChange {
     /**
-     * <p>The name of the container associated with the managed agent.</p>
+     * <p>The name of the container that's associated with the managed agent.</p>
      */
     containerName: string | undefined;
     /**
@@ -8352,7 +8439,7 @@ export interface SubmitTaskStateChangeRequest {
      */
     reason?: string;
     /**
-     * <p>Any containers associated with the state change request.</p>
+     * <p>Any containers that's associated with the state change request.</p>
      */
     containers?: ContainerStateChange[];
     /**
@@ -8360,19 +8447,19 @@ export interface SubmitTaskStateChangeRequest {
      */
     attachments?: AttachmentStateChange[];
     /**
-     * <p>The details for the managed agent associated with the task.</p>
+     * <p>The details for the managed agent that's associated with the task.</p>
      */
     managedAgents?: ManagedAgentStateChange[];
     /**
-     * <p>The Unix timestamp for when the container image pull began.</p>
+     * <p>The Unix timestamp for the time when the container image pull started.</p>
      */
     pullStartedAt?: Date;
     /**
-     * <p>The Unix timestamp for when the container image pull completed.</p>
+     * <p>The Unix timestamp for the time when the container image pull completed.</p>
      */
     pullStoppedAt?: Date;
     /**
-     * <p>The Unix timestamp for when the task execution stopped.</p>
+     * <p>The Unix timestamp for the time when the task execution stopped.</p>
      */
     executionStoppedAt?: Date;
 }
@@ -8395,7 +8482,7 @@ export declare namespace SubmitTaskStateChangeResponse {
     const filterSensitiveLog: (obj: SubmitTaskStateChangeResponse) => any;
 }
 /**
- * <p>The specified resource could not be found.</p>
+ * <p>The specified resource wasn't found.</p>
  */
 export interface ResourceNotFoundException extends __SmithyException, $MetadataBearer {
     name: "ResourceNotFoundException";
@@ -8410,8 +8497,8 @@ export declare namespace ResourceNotFoundException {
 }
 export interface TagResourceRequest {
     /**
-     * <p>The Amazon Resource Name (ARN) of the resource to which to add tags. Currently, the supported resources
-     * 			are Amazon ECS capacity providers, tasks, services, task definitions, clusters, and container
+     * <p>The Amazon Resource Name (ARN) of the resource to add tags to. Currently, the supported resources are
+     * 			Amazon ECS capacity providers, tasks, services, task definitions, clusters, and container
      * 			instances.</p>
      */
     resourceArn: string | undefined;
@@ -8467,9 +8554,9 @@ export declare namespace TagResourceResponse {
 }
 export interface UntagResourceRequest {
     /**
-     * <p>The Amazon Resource Name (ARN) of the resource from which to delete tags. Currently, the supported
-     * 			resources are Amazon ECS capacity providers, tasks, services, task definitions, clusters, and
-     * 			container instances.</p>
+     * <p>The Amazon Resource Name (ARN) of the resource to delete tags from. Currently, the supported resources
+     * 			are Amazon ECS capacity providers, tasks, services, task definitions, clusters, and container
+     * 			instances.</p>
      */
     resourceArn: string | undefined;
     /**
@@ -8505,14 +8592,14 @@ export interface AutoScalingGroupProviderUpdate {
      * 			protection.</p>
      * 		       <important>
      * 			         <p>When using managed termination protection, managed scaling must also be used
-     * 				otherwise managed termination protection will not work.</p>
+     * 				otherwise managed termination protection doesn't work.</p>
      * 		       </important>
      * 		       <p>When managed termination protection is enabled, Amazon ECS prevents the Amazon EC2 instances in
      * 			an Auto Scaling group that contain tasks from being terminated during a scale-in action.
      * 			The Auto Scaling group and each instance in the Auto Scaling group must have instance
-     * 			protection from scale-in actions enabled as well. For more information, see <a href="https://docs.aws.amazon.com/autoscaling/ec2/userguide/as-instance-termination.html#instance-protection">Instance Protection</a> in the <i>Auto Scaling User Guide</i>.</p>
-     * 		       <p>When managed termination protection is disabled, your Amazon EC2 instances are not
-     * 			protected from termination when the Auto Scaling group scales in.</p>
+     * 			protection from scale-in actions enabled. For more information, see <a href="https://docs.aws.amazon.com/autoscaling/ec2/userguide/as-instance-termination.html#instance-protection">Instance Protection</a> in the <i>Auto Scaling User Guide</i>.</p>
+     * 		       <p>When managed termination protection is disabled, your Amazon EC2 instances aren't protected
+     * 			from termination when the Auto Scaling group scales in.</p>
      */
     managedTerminationProtection?: ManagedTerminationProtection | string;
 }
@@ -8528,7 +8615,7 @@ export interface UpdateCapacityProviderRequest {
      */
     name: string | undefined;
     /**
-     * <p>An object representing the parameters to update for the Auto Scaling group capacity
+     * <p>An object that represent the parameters to update for the Auto Scaling group capacity
      * 			provider.</p>
      */
     autoScalingGroupProvider: AutoScalingGroupProviderUpdate | undefined;
@@ -8590,7 +8677,7 @@ export interface UpdateClusterSettingsRequest {
     cluster: string | undefined;
     /**
      * <p>The setting to use by default for a cluster. This parameter is used to enable CloudWatch
-     * 			Container Insights for a cluster. If this value is specified, it will override the
+     * 			Container Insights for a cluster. If this value is specified, it overrides the
      * 				<code>containerInsights</code> value set with <a>PutAccountSetting</a> or
      * 				<a>PutAccountSettingDefault</a>.</p>
      */
@@ -8615,10 +8702,10 @@ export declare namespace UpdateClusterSettingsResponse {
     const filterSensitiveLog: (obj: UpdateClusterSettingsResponse) => any;
 }
 /**
- * <p>Amazon ECS is unable to determine the current version of the Amazon ECS container agent on the
- * 			container instance and does not have enough information to proceed with an update. This
- * 			could be because the agent running on the container instance is an older or custom
- * 			version that does not use our version information.</p>
+ * <p>Amazon ECS can't determine the current version of the Amazon ECS container agent on the
+ * 			container instance and doesn't have enough information to proceed with an update. This
+ * 			could be because the agent running on the container instance is a previous or custom
+ * 			version that doesn't use our version information.</p>
  */
 export interface MissingVersionException extends __SmithyException, $MetadataBearer {
     name: "MissingVersionException";
@@ -8632,9 +8719,9 @@ export declare namespace MissingVersionException {
     const filterSensitiveLog: (obj: MissingVersionException) => any;
 }
 /**
- * <p>There is no update available for this Amazon ECS container agent. This could be because the
- * 			agent is already running the latest version, or it is so old that there is no update
- * 			path to the current version.</p>
+ * <p>There's no update available for this Amazon ECS container agent. This might be because the
+ * 			agent is already running the latest version or because it's so old that there's no
+ * 			update path to the current version.</p>
  */
 export interface NoUpdateAvailableException extends __SmithyException, $MetadataBearer {
     name: "NoUpdateAvailableException";
@@ -8654,8 +8741,8 @@ export interface UpdateContainerAgentRequest {
      */
     cluster?: string;
     /**
-     * <p>The container instance ID or full ARN entries for the container instance on which
-     * 			you would like to update the Amazon ECS container agent.</p>
+     * <p>The container instance ID or full ARN entries for the container instance where you
+     * 			would like to update the Amazon ECS container agent.</p>
      */
     containerInstance: string | undefined;
 }
@@ -8667,7 +8754,7 @@ export declare namespace UpdateContainerAgentRequest {
 }
 export interface UpdateContainerAgentResponse {
     /**
-     * <p>The container instance for which the container agent was updated.</p>
+     * <p>The container instance that the container agent was updated for.</p>
      */
     containerInstance?: ContainerInstance;
 }
@@ -8688,13 +8775,12 @@ export interface UpdateContainerInstancesStateRequest {
      */
     containerInstances: string[] | undefined;
     /**
-     * <p>The container instance state with which to update the container instance. The only
-     * 			valid values for this action are <code>ACTIVE</code> and <code>DRAINING</code>. A
-     * 			container instance can only be updated to <code>DRAINING</code> status once it has
-     * 			reached an <code>ACTIVE</code> state. If a container instance is in
-     * 				<code>REGISTERING</code>, <code>DEREGISTERING</code>, or
-     * 				<code>REGISTRATION_FAILED</code> state you can describe the container instance but
-     * 			will be unable to update the container instance state.</p>
+     * <p>The container instance state to update the container instance with. The only valid
+     * 			values for this action are <code>ACTIVE</code> and <code>DRAINING</code>. A container
+     * 			instance can only be updated to <code>DRAINING</code> status once it has reached an
+     * 				<code>ACTIVE</code> state. If a container instance is in <code>REGISTERING</code>,
+     * 				<code>DEREGISTERING</code>, or <code>REGISTRATION_FAILED</code> state you can
+     * 			describe the container instance but can't update the container instance state.</p>
      */
     status: ContainerInstanceStatus | string | undefined;
 }
@@ -8722,7 +8808,7 @@ export declare namespace UpdateContainerInstancesStateResponse {
 }
 export interface UpdateServiceRequest {
     /**
-     * <p>The short name or full Amazon Resource Name (ARN) of the cluster that your service is running on.
+     * <p>The short name or full Amazon Resource Name (ARN) of the cluster that your service runs on.
      * 			If you do not specify a cluster, the default cluster is assumed.</p>
      */
     cluster?: string;
@@ -8745,11 +8831,11 @@ export interface UpdateServiceRequest {
     taskDefinition?: string;
     /**
      * <p>The capacity provider strategy to update the service to use.</p>
-     * 		       <p>If the service is using the default capacity provider strategy for the cluster, the
+     * 		       <p>if the service uses the default capacity provider strategy for the cluster, the
      * 			service can be updated to use one or more capacity providers as opposed to the default
      * 			capacity provider strategy. However, when a service is using a capacity provider
-     * 			strategy that is not the default capacity provider strategy, the service cannot be
-     * 			updated to use the cluster's default capacity provider strategy.</p>
+     * 			strategy that's not the default capacity provider strategy, the service can't be updated
+     * 			to use the cluster's default capacity provider strategy.</p>
      * 		       <p>A capacity provider strategy consists of one or more capacity providers along with the
      * 				<code>base</code> and <code>weight</code> to assign to them. A capacity provider
      * 			must be associated with the cluster to be used in a capacity provider strategy. The
@@ -8782,8 +8868,8 @@ export interface UpdateServiceRequest {
      * 			unchanged. If this value is specified, it will override any existing placement
      * 			constraints defined for the service. To remove all existing placement constraints,
      * 			specify an empty array.</p>
-     * 		       <p>You can specify a maximum of 10 constraints per task (this limit includes constraints
-     * 			in the task definition and those specified at runtime).</p>
+     * 		       <p>You can specify a maximum of 10 constraints for each task. This limit includes
+     * 			constraints in the task definition and those specified at runtime.</p>
      */
     placementConstraints?: PlacementConstraint[];
     /**
@@ -8791,34 +8877,34 @@ export interface UpdateServiceRequest {
      * 			specified, the existing placement strategy for the service will remain unchanged. If
      * 			this value is specified, it will override the existing placement strategy defined for
      * 			the service. To remove an existing placement strategy, specify an empty object.</p>
-     * 		       <p>You can specify a maximum of five strategy rules per service.</p>
+     * 		       <p>You can specify a maximum of five strategy rules for each service.</p>
      */
     placementStrategy?: PlacementStrategy[];
     /**
-     * <p>The platform version on which your tasks in the service are running. A platform
-     * 			version is only specified for tasks using the Fargate launch type. If a
-     * 			platform version is not specified, the <code>LATEST</code> platform version is used by
-     * 			default. For more information, see <a href="https://docs.aws.amazon.com/AmazonECS/latest/developerguide/platform_versions.html">Fargate Platform
+     * <p>The platform version that your tasks in the service run on. A platform version is only
+     * 			specified for tasks using the Fargate launch type. If a platform version
+     * 			is not specified, the <code>LATEST</code> platform version is used. For more
+     * 			information, see <a href="https://docs.aws.amazon.com/AmazonECS/latest/developerguide/platform_versions.html">Fargate Platform
      * 				Versions</a> in the <i>Amazon Elastic Container Service Developer Guide</i>.</p>
      */
     platformVersion?: string;
     /**
-     * <p>Whether to force a new deployment of the service. Deployments are not forced by
-     * 			default. You can use this option to trigger a new deployment with no service definition
-     * 			changes. For example, you can update a service's tasks to use a newer Docker image with
-     * 			the same image/tag combination (<code>my_image:latest</code>) or to roll Fargate tasks
-     * 			onto a newer platform version.</p>
+     * <p>Determines whether to force a new deployment of the service. By default, deployments
+     * 			aren't forced. You can use this option to start a new deployment with no service
+     * 			definition changes. For example, you can update a service's tasks to use a newer Docker
+     * 			image with the same image/tag combination (<code>my_image:latest</code>) or to roll
+     * 			Fargate tasks onto a newer platform version.</p>
      */
     forceNewDeployment?: boolean;
     /**
-     * <p>The period of time, in seconds, that the Amazon ECS service scheduler should ignore
-     * 			unhealthy Elastic Load Balancing target health checks after a task has first started. This is only valid
-     * 			if your service is configured to use a load balancer. If your service's tasks take a
-     * 			while to start and respond to Elastic Load Balancing health checks, you can specify a health check grace
-     * 			period of up to 2,147,483,647 seconds. During that time, the Amazon ECS service
-     * 			scheduler ignores the Elastic Load Balancing health check status. This grace period can prevent the ECS
-     * 			service scheduler from marking tasks as unhealthy and stopping them before they have
-     * 			time to come up.</p>
+     * <p>The period of time, in seconds, that the Amazon ECS service scheduler ignores unhealthy
+     * 			Elastic Load Balancing target health checks after a task has first started. This is only valid if your
+     * 			service is configured to use a load balancer. If your service's tasks take a while to
+     * 			start and respond to Elastic Load Balancing health checks, you can specify a health check grace period of
+     * 			up to 2,147,483,647 seconds. During that time, the Amazon ECS service scheduler ignores
+     * 			the Elastic Load Balancing health check status. This grace period can prevent the ECS service scheduler
+     * 			from marking tasks as unhealthy and stopping them before they have time to come
+     * 			up.</p>
      */
     healthCheckGracePeriodSeconds?: number;
     /**
@@ -8884,11 +8970,11 @@ export declare namespace UpdateServicePrimaryTaskSetResponse {
 export interface UpdateTaskSetRequest {
     /**
      * <p>The short name or full Amazon Resource Name (ARN) of the cluster that hosts the service that the task
-     * 			set exists in.</p>
+     * 			set is found in.</p>
      */
     cluster: string | undefined;
     /**
-     * <p>The short name or full Amazon Resource Name (ARN) of the service that the task set exists in.</p>
+     * <p>The short name or full Amazon Resource Name (ARN) of the service that the task set is found in.</p>
      */
     service: string | undefined;
     /**