From 00176baa9a85d48ace8eaae961621966501a5fa1 Mon Sep 17 00:00:00 2001
From: Colin Campbell <142777+ColinCampbell@users.noreply.github.com>
Date: Wed, 12 Jul 2023 11:56:58 -0700
Subject: [PATCH] Fix spelling mistake in development_environment.mdx (#1842)

Assuming this was meant to reference "production" and not "productive"
---
 docs/development_environment.mdx | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/docs/development_environment.mdx b/docs/development_environment.mdx
index 1cf448ad..3e809886 100644
--- a/docs/development_environment.mdx
+++ b/docs/development_environment.mdx
@@ -48,7 +48,7 @@ When a task is currently running (like `Preview` for the docs), it can be restar
 
 If the Dev Container was set up correctly - it supports debugging by default, out-of-the-box. It provides the necessary debug configurations, so hitting F5 should launch Home Assistant. Any breakpoints put in the code should be triggered, and the debugger should stop. 
 
-It is also possible to debug a remote Home Assistance instance (e.g., productive instance) by following the procedure described [here](https://www.home-assistant.io/integrations/debugpy/).
+It is also possible to debug a remote Home Assistance instance (e.g., production instance) by following the procedure described [here](https://www.home-assistant.io/integrations/debugpy/).
 
 ## Manual Environment