From 0a94bec874c40ad370fee4e74cff26fe874c183d Mon Sep 17 00:00:00 2001
From: Artem <_mag12@yahoo.com>
Date: Sat, 21 Jul 2018 21:04:08 +0700
Subject: [PATCH] Update internationalization_index.md (#58)

---
 docs/internationalization_index.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/docs/internationalization_index.md b/docs/internationalization_index.md
index 2c042272..3361d5c2 100644
--- a/docs/internationalization_index.md
+++ b/docs/internationalization_index.md
@@ -4,7 +4,7 @@ title: "Internationalization"
 
 The Home Assistant internationalization project includes preparing platforms and the frontend for localization, as well as the actual translation of localized strings.
 
-Some compmonents and platforms will have strings that need to be localized specifically for that platform. These strings are managed in the core [home-assistant](https://github.com/home-assistant/home-assistant) repository. The Home Assistant backend will serve strings to the clients based on the loaded components in the running instance.
+Some components and platforms will have strings that need to be localized specifically for that platform. These strings are managed in the core [home-assistant](https://github.com/home-assistant/home-assistant) repository. The Home Assistant backend will serve strings to the clients based on the loaded components in the running instance.
 
 There are also localizable strings that exist only on the frontend. These strings are managed in the [home-assistant-polymer](https://github.com/home-assistant/home-assistant-polymer) repository. These strings are stored with the frontend and don’t depend on the backend configuration.