From 89f0c704ce78d9844630504fd5195d8b265a1de1 Mon Sep 17 00:00:00 2001
From: Josh Soref <jsoref@users.noreply.github.com>
Date: Thu, 26 May 2016 18:35:34 +0000
Subject: [PATCH] spelling: initialized

---
 RELEASE-NOTES.md            | 4 ++--
 test/modules/module.spec.js | 2 +-
 2 files changed, 3 insertions(+), 3 deletions(-)

diff --git a/RELEASE-NOTES.md b/RELEASE-NOTES.md
index 788afebeb..47107ba10 100644
--- a/RELEASE-NOTES.md
+++ b/RELEASE-NOTES.md
@@ -366,7 +366,7 @@ $('.ui.form')
 - **Tab** - Fixed issue where simple path would be tested before full path, i.e. `first/` vs `/second/first/` causing tab to not open in some cases **Thanks @habibutsu** [#2843](https://github.com/Semantic-Org/Semantic-UI/issues/2843)
 
 **Additional Bugs**
-- **API** - API now will use automatically use `form` action if no api event is specified now  when form is `stateContext` but not intialized element
+- **API** - API now will use automatically use `form` action if no api event is specified now  when form is `stateContext` but not initialized element
 - **Build Tools** - Fixes issue on `win` platform where packaged theme would not correctly update when using watch due to regExp not matching windows path separators.
 - **Dropdown** - Dropdown will no longer fire native `onchange` event on hidden input when setting value during initial load (unless `fireOnInit: true`) #2795 **Thanks @lauri-elevant**
 - **Dropdown** - Fixed issue where `forceSelection` would not occur when `pageLostFocus` (clicked into another tab and back)
@@ -450,7 +450,7 @@ This release should fix bugs some may have encountered with `npm install semanti
 - **Message** - Fixed issues where icon would overlap in `icon message` when at mobile resolutions due to `flex-collapse` value being incorrect [#2665](https://github.com/Semantic-Org/Semantic-UI/issues/2665)
 
 **Additional Fixes**
-- **Dropdown** - `<select>` dropdowns intialized without `multiple` property set on `<select>` will now produce an error to alert users selection will not be preserved correctly. Related [#2573](https://github.com/Semantic-Org/Semantic-UI/issues/2573)
+- **Dropdown** - `<select>` dropdowns initialized without `multiple` property set on `<select>` will now produce an error to alert users selection will not be preserved correctly. Related [#2573](https://github.com/Semantic-Org/Semantic-UI/issues/2573)
 - **Dropdown** - Dropdown `<option>` added with `userAddition` now recieve class name `addition` to distinguish from original `<select>` options. [#2573](https://github.com/Semantic-Org/Semantic-UI/issues/2573)
 - **Dropdown** - User additions now have their `<option>` removed if a user deselects an addition. [#2573](https://github.com/Semantic-Org/Semantic-UI/issues/2573)
 
diff --git a/test/modules/module.spec.js b/test/modules/module.spec.js
index 73bc0fca1..ff26c5285 100644
--- a/test/modules/module.spec.js
+++ b/test/modules/module.spec.js
@@ -176,7 +176,7 @@ function moduleTests(ui) {
 
       });
 
-      it("does not change other elements when re-initalized", function() {
+      it("does not change other elements when re-initialized", function() {
         $modules[module]();
 
         $oneModule[module]({