From 06e96f543e2cacd3b5d629a9eefb9d937ae5b664 Mon Sep 17 00:00:00 2001
From: "github-actions[bot]"
 <41898282+github-actions[bot]@users.noreply.github.com>
Date: Wed, 18 Dec 2024 15:14:39 +0000
Subject: [PATCH] Commit changes made by code formatters

---
 runbooks/source/analyze-vpc-flow-logs.html.md.erb | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/runbooks/source/analyze-vpc-flow-logs.html.md.erb b/runbooks/source/analyze-vpc-flow-logs.html.md.erb
index 7069b982..e0193aa9 100644
--- a/runbooks/source/analyze-vpc-flow-logs.html.md.erb
+++ b/runbooks/source/analyze-vpc-flow-logs.html.md.erb
@@ -18,7 +18,7 @@ Things to note:
 
 - When creating a CloudFormation template, use the `Partition: Daily` option. This will create a partition for each day and will make it easier to query the logs for a specific day.
 - Provide Partition start date and end date closer when the issue was observed. The duration is limited to 20 days
-- Create two s3 buckets: 
-  - one for CloudFormation template 
+- Create two s3 buckets:
+  - one for CloudFormation template
   - one to store the Athena query results which you will provide when creating the CloudFormation stack.
 - When the flow logs are downloaded and the user has investigated the issue, delete the created s3 buckets for CloudFormation template and Athena query results and the CloudFormation stack.