From 1ae86fa4a7de5e86d7c9ce2bde6c1aa7cf064859 Mon Sep 17 00:00:00 2001
From: Sarah Guthals <sarah@guthals.com>
Date: Wed, 18 Dec 2024 08:30:10 -0800
Subject: [PATCH] Update docs/product/dev-toolbar/setup.mdx

---
 docs/product/dev-toolbar/setup.mdx | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/docs/product/dev-toolbar/setup.mdx b/docs/product/dev-toolbar/setup.mdx
index 0d84471f3d19d..37c8795029489 100644
--- a/docs/product/dev-toolbar/setup.mdx
+++ b/docs/product/dev-toolbar/setup.mdx
@@ -131,7 +131,7 @@ if (isDev ) {
 
 ## Deploying to Production Environments
 
-In production however, it's strongly recommended to *conditionally* include the Dev Toolbar `<script>` tag so that only members of your Sentry organization can see it. The specific implementation for conditionally including the Dev Toolbar is something you'll need to write based on how your app works and how your dev team is set up.
+In production, it's strongly recommended to *conditionally* include the Dev Toolbar `<script>` tag so that only members of your Sentry organization can see it. The specific implementation for conditionally including the Dev Toolbar is something you'll need to write based on how your app works and how your dev team is set up.
 
 For example, if your web application requires authentication to access, you could add a conditional where the Dev Toolbar is shown always when deployed to development **and** staging, but in production only show the toolbar **if** an employee is logged in.