Apply spell check (#41)

src/Calculator/Views/CalculatorProgrammerBitFlipPanel.xaml.cpp

@@ -166,7 +166,7 @@ void CalculatorProgrammerBitFlipPanel::OnBitToggled(_In_ Object^ sender, _In_ Ro
     // Any input from the Numpad may also result in toggling the bit as their state is bound to the BinaryDisplayValue.
     // Also, if the mode is switched to other Calculator modes when the BitFlip panel is open,
     // a race condition exists in which the IsProgrammerMode property is still true and the UpdatePrimaryResult() is called,
-    // which continously alters the Display Value and the state of the Bit Flip buttons.
+    // which continuously alters the Display Value and the state of the Bit Flip buttons.
     if ((Model->IsBitFlipChecked)
         && Model->IsProgrammer)
     {

src/Calculator/Views/MainPage.xaml.cpp

@@ -116,7 +116,7 @@ void MainPage::OnNavigatedTo(NavigationEventArgs^ e)
 
 void MainPage::WindowSizeChanged(_In_ Platform::Object^ /*sender*/, _In_ Windows::UI::Core::WindowSizeChangedEventArgs^ e)
 {
-    // We dont use layout aware page's view states, we have our own
+    // We don't use layout aware page's view states, we have our own
     UpdateViewState();
 }
 
@@ -321,7 +321,7 @@ void MainPage::EnsureCalculator()
 
         CalcHolder->Child = m_calculator;
 
-        // Calculator's "default" state is visibile, but if we get delay loaded
+        // Calculator's "default" state is visible, but if we get delay loaded
         // when in converter, we should not be visible. This is not a problem for converter
         // since it's default state is hidden.
         ShowHideControls(this->Model->Mode);

src/Calculator/Views/Memory.xaml.cpp

@@ -48,7 +48,7 @@ void Memory::MemoryListItemClick(_In_ Object^ sender, _In_ ItemClickEventArgs^ e
 {
     MemoryItemViewModel^ memorySlot = safe_cast<MemoryItemViewModel^>(e->ClickedItem);
 
-    // Incase the memory list is clicked and enter is pressed,
+    // In case the memory list is clicked and enter is pressed,
     // On Item clicked event gets fired and e->ClickedItem is Null.
     if (memorySlot != nullptr)
     {

src/Calculator/Views/NumberPad.xaml

@@ -102,7 +102,7 @@
 
         <!--
             This is the only button in all of the app that should ever have a explicit reference to KeyboardShortcutManager in Xaml
-            this is needed because we need to have at least 1 refernece from Xaml so the right metadata is generated for the
+            this is needed because we need to have at least 1 reference from Xaml so the right metadata is generated for the
             KeyboardShortcutManager class, otherwise the Xaml will stop parsing and the app won't boot therefore:
             DO NOT REMOVE the common:KeyboardShortcutManager.Character from this element, it's value will be overwritten by the
             string coming from the RESW file

src/Calculator/Views/SupplementaryResults.xaml.cpp

@@ -1,4 +1,4 @@
-// Copyright (c) Microsoft Corporation. All rights reserved.
+// Copyright (c) Microsoft Corporation. All rights reserved.
 // Licensed under the MIT License.
 
 //
@@ -72,7 +72,7 @@ SupplementaryResults::SupplementaryResults() :
 
 void SupplementaryResults::RefreshData()
 {
-    // Copy the list so that when we chop stuff off, we dont modify the original
+    // Copy the list so that when we chop stuff off, we don't modify the original
     // complete list.
     m_data->Clear();
     for(SupplementaryResult^ sr : safe_cast<UnitConverterViewModel^>(this->DataContext)->SupplementaryResults)