Skip to content

Commit

Permalink
chore(documentation): Update README.md (#12892)
Browse files Browse the repository at this point in the history
Fix typos in documentation


----

*By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license*
  • Loading branch information
hemant6488 authored Mar 2, 2021
1 parent d884a34 commit ba99ad0
Showing 1 changed file with 3 additions and 3 deletions.
6 changes: 3 additions & 3 deletions packages/@aws-cdk/aws-ecs/README.md
Original file line number Diff line number Diff line change
Expand Up @@ -67,7 +67,7 @@ one to run tasks on AWS Fargate.
Here are the main differences:

- **Amazon EC2**: instances are under your control. Complete control of task to host
allocation. Required to specify at least a memory reseration or limit for
allocation. Required to specify at least a memory reservation or limit for
every container. Can use Host, Bridge and AwsVpc networking modes. Can attach
Classic Load Balancer. Can share volumes between container and host.
- **AWS Fargate**: tasks run on AWS-managed instances, AWS manages task to host
Expand Down Expand Up @@ -175,7 +175,7 @@ cluster.addCapacity('AsgSpot', {
When the `ecs.AddCapacityOptions` that you provide has a non-zero `taskDrainTime` (the default) then an SNS topic and Lambda are created to ensure that the
cluster's instances have been properly drained of tasks before terminating. The SNS Topic is sent the instance-terminating lifecycle event from the AutoScalingGroup,
and the Lambda acts on that event. If you wish to engage [server-side encryption](https://docs.aws.amazon.com/sns/latest/dg/sns-data-encryption.html) for this SNS Topic
then you may do so by providing a KMS key for the `topicEncryptionKey` propery of `ecs.AddCapacityOptions`.
then you may do so by providing a KMS key for the `topicEncryptionKey` property of `ecs.AddCapacityOptions`.

```ts
// Given
Expand All @@ -190,7 +190,7 @@ cluster.addCapacity('ASGEncryptedSNS', {

## Task definitions

A task Definition describes what a single copy of a **task** should look like.
A task definition describes what a single copy of a **task** should look like.
A task definition has one or more containers; typically, it has one
main container (the *default container* is the first one that's added
to the task definition, and it is marked *essential*) and optionally
Expand Down

0 comments on commit ba99ad0

Please sign in to comment.