From 4ec2237bbc998d4dfa992ab79ff9fd5e4636238a Mon Sep 17 00:00:00 2001
From: eduardo <83775838+drauedo@users.noreply.github.com>
Date: Fri, 20 Feb 2026 16:58:42 +0100
Subject: [PATCH] Fixing typo

Some occurences we use Firehouse instead of Firehose.
---
 src/content/docs/aws/services/firehose.mdx | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/src/content/docs/aws/services/firehose.mdx b/src/content/docs/aws/services/firehose.mdx
index f88a35b0..cd862500 100644
--- a/src/content/docs/aws/services/firehose.mdx
+++ b/src/content/docs/aws/services/firehose.mdx
@@ -20,7 +20,7 @@ The supported APIs are available on our [API Coverage section](#api-coverage), w
 
 ## Getting started
 
-This guide is designed for users new to Data Firehouse and assumes basic knowledge of the AWS CLI and our [`awslocal`](https://github.com/localstack/awscli-local) wrapper script.
+This guide is designed for users new to Data Firehose and assumes basic knowledge of the AWS CLI and our [`awslocal`](https://github.com/localstack/awscli-local) wrapper script.
 
 Start your LocalStack container using your preferred method.
 We will demonstrate how to use Firehose to load Kinesis data into Elasticsearch with S3 Backup with the AWS CLI.
@@ -55,7 +55,7 @@ awslocal kinesis create-stream \
   --shard-count 2
 ```
 
-### Create a Firehouse delivery stream
+### Create a Firehose delivery stream
 
 You can now create the Firehose delivery stream.
 In this configuration, Elasticsearch serves as the destination, while S3 serves as the repository for our AllDocuments backup.