From dbd742f3d50f3383d7a1af9d0c665523829c2cdd Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Bryan=E2=84=A2?=
 <61433408+brycahta@users.noreply.github.com>
Date: Fri, 23 Apr 2021 13:15:00 -0500
Subject: [PATCH] Clarify EventBridge Rules setup

* Addressing concerns in #415
---
 README.md | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/README.md b/README.md
index ab0899c3..19e62fe5 100644
--- a/README.md
+++ b/README.md
@@ -261,9 +261,9 @@ EOF
 $ aws sqs create-queue --queue-name "${SQS_QUEUE_NAME}" --attributes file:///tmp/queue-attributes.json 
 ```
 
-#### 4. Create an Amazon EventBridge Rule
+#### 4. Create Amazon EventBridge Rules
 
-Here is the AWS CLI command to create an Amazon EventBridge rule so that ASG termination events are sent to the SQS queue created in the previous step. This should really be configured via your favorite infrastructure-as-code tool like CloudFormation or Terraform:
+Here are AWS CLI commands to create Amazon EventBridge rules so that ASG termination events, Spot Interruptions, and Rebalance Recommendations are sent to the SQS queue created in the previous step. This should really be configured via your favorite infrastructure-as-code tool like CloudFormation or Terraform:
 
 ```
 $ aws events put-rule \