From 8d0a224d3ee8a0133233308040d41504f16ecee9 Mon Sep 17 00:00:00 2001
From: John Hillery <34005807+jrhillery@users.noreply.github.com>
Date: Wed, 23 Apr 2025 16:59:19 -0400
Subject: [PATCH] Update development_tips.md for localization (#2650)

Co-authored-by: coderabbitai[bot] <136622811+coderabbitai[bot]@users.noreply.github.com>
---
 docs/development_tips.md | 8 +++++++-
 1 file changed, 7 insertions(+), 1 deletion(-)

diff --git a/docs/development_tips.md b/docs/development_tips.md
index 2bd6b6f7..8bfcc88a 100644
--- a/docs/development_tips.md
+++ b/docs/development_tips.md
@@ -16,7 +16,13 @@ See the [API library docs](api_lib_index#trying-your-library-inside-home-assista
 
 ### Test Core integration changes in your production Home Assistant environment
 
-If you made a change to a core integration and you want to test it in your production Home Assistant environment, copy the integration folder into `/config/custom_components`, add a version to the `manifest.json` (e.g. "version": "0.0.0"), and restart Home Assistant. Home Assistant will always prioritize integrations in `custom_components` over the core integration. Don't forget to remove it once you are done testing; otherwise, you will be stuck on that version.
+To test a core integration change in your production Home Assistant environment:
+1. Copy the integration folder into `/config/custom_components`.
+2. Add a **version** field to `manifest.json` (for example, `"version": "0.0.0"`).
+3. If the integration uses localized strings, copy `strings.json` into `translations/en.json` under the integration folder as described in [Custom integration localization](internationalization/custom_integration).
+4. Restart Home Assistant.
+
+Home Assistant will always prioritize integrations in `custom_components` over the core integration. Don't forget to remove it once you are done testing; otherwise, you will be stuck on that version.
 
 ### When adding a config flow to an integration, be aware of the frontend