Site updated at 2018-01-25 17:33:45 UTC

developers/architecture/index.html

@@ -79,7 +79,7 @@
 <ul>
   <li>Home Control is responsible for collecting information and controlling devices.</li>
   <li>Home Automation triggers commands based on user configurations.</li>
-  <li>Smart Home triggers commands based on previous behaviour.</li>
+  <li>Smart Home triggers commands based on previous behavior.</li>
 </ul>
 <p class="img">
   <a href="/images/architecture/home_automation_landscape.png" name="landscape">

developers/development_guidelines/index.html

@@ -87,8 +87,8 @@
 </ul>
 <p>The maximum line length comes directly from the <a href="https://www.python.org/dev/peps/pep-0008/#maximum-line-length">PEP8 style guide</a>, and is also used by the Python standard library. All code must pass these linting checks, and no exceptions will be made. There have already been numerous requests to increase the maximum line length, but after evaluating the options, the Home Assistant maintainers have decided to stay at 79 characters. This decision is final.</p>
 <p>Those points may require that you adjust your IDE or editor settings.</p>
-<h2><a class="title-link" name="our-recommandations" href="#our-recommandations"></a> Our recommandations</h2>
-<p>For some cases <a href="https://www.python.org/dev/peps/">PEPs</a> don’t make a statement. This section covers our recommendations about the code style. Those points were collected from the exisiting code and based on what contributors and developers were using the most. This is basically a majority decision, thus you may not agree with it. But we would like to encourage you follow those recommandations to keep the code unified.</p>
+<h2><a class="title-link" name="our-recommendations" href="#our-recommendations"></a> Our recommendations</h2>
+<p>For some cases <a href="https://www.python.org/dev/peps/">PEPs</a> don’t make a statement. This section covers our recommendations about the code style. Those points were collected from the existing code and based on what contributors and developers were using the most. This is basically a majority decision, thus you may not agree with it. But we would like to encourage you follow those recommendations to keep the code unified.</p>
 <h3><a class="title-link" name="quotes" href="#quotes"></a> Quotes</h3>
 <p>Use single quotes <code class="highlighter-rouge">'</code> for single word and <code class="highlighter-rouge">"</code> for multiple words or sentences.</p>
 <div class="language-python highlighter-rouge"><pre class="highlight"><code><span class="n">ATTR_WATERLEVEL</span> <span class="o">=</span> <span class="s">'level'</span>

developers/development_submitting/index.html

@@ -107,7 +107,7 @@
       <li>On GitHub, navigate to the main page of the Home Assistant repository.</li>
       <li>In the “Branch” menu, choose the branch that contains your commits (from your fork).</li>
       <li>To the right of the Branch menu, click <strong>New pull request</strong>.</li>
-      <li>Use the base branch dropdown menu to select the branch you’d like to merge your changes into, then use the compare branch drop-down menu to choose the topic branch you made your changes in. Make sure the Home Assistant branch matches with your forked branch (<code class="highlighter-rouge">dev</code>) else you will propose ALL committs between branches.</li>
+      <li>Use the base branch dropdown menu to select the branch you’d like to merge your changes into, then use the compare branch drop-down menu to choose the topic branch you made your changes in. Make sure the Home Assistant branch matches with your forked branch (<code class="highlighter-rouge">dev</code>) else you will propose ALL commits between branches.</li>
       <li>Type a title and complete the provided description for your pull request.</li>
       <li>Click <strong>Create pull request</strong>.</li>
     </ul>

developers/development_validation/index.html

@@ -75,7 +75,7 @@
   </header>
   <hr class="divider">
   <p>The <code class="highlighter-rouge">configuration.yaml</code> file contains the configuration options for components and platforms. We use <a href="https://pypi.python.org/pypi/voluptuous">voluptuous</a> to make sure that the configuration provided by the user is valid. Some entries are optional or could be required to set up a platform or a component. Others must be a defined type or from an already-defined list.</p>
-<p>We test the configuration to ensure that users have a great experience and minimise notifications if something is wrong with a platform or component setup before Home Assistant runs.</p>
+<p>We test the configuration to ensure that users have a great experience and minimize notifications if something is wrong with a platform or component setup before Home Assistant runs.</p>
 <p>Besides <a href="https://pypi.python.org/pypi/voluptuous">voluptuous</a> default types, many custom types are available. For an overview, take a look at the <a href="https://github.com/home-assistant/home-assistant/blob/master/homeassistant/helpers/config_validation.py">config_validation.py</a> helper.</p>
 <ul>
   <li>Types: <code class="highlighter-rouge">string</code>, <code class="highlighter-rouge">byte</code>, and <code class="highlighter-rouge">boolean</code></li>

developers/documentation/standards/index.html

@@ -145,7 +145,7 @@ redirect_from: /getting-started/android/
 ---
 </code></pre>
 </div>
-<p>Adding a redirect also applies if you move content around in the <a href="/docs/">documention</a>.</p>
+<p>Adding a redirect also applies if you move content around in the <a href="/docs/">documentation</a>.</p>
 </article>
         </div>
         <aside id="sidebar" class="grid__item one-third lap-one-whole palm-one-whole">

developers/multiple_instances/index.html

@@ -75,7 +75,7 @@
   </header>
   <hr class="divider">
   <h1><a class="title-link" name="this-has-been-deprecated-and-is-no-longer-supported" href="#this-has-been-deprecated-and-is-no-longer-supported"></a> This has been deprecated and is no longer supported.</h1>
-<p>Home Assistant supports running multiple synchronised instances using a master-slave model. Whenever <code class="highlighter-rouge">events.fire</code> or <code class="highlighter-rouge">states.set</code> is called on the slave it will forward it to the master. The master will replicate all events and changed states to its slaves.</p>
+<p>Home Assistant supports running multiple synchronized instances using a master-slave model. Whenever <code class="highlighter-rouge">events.fire</code> or <code class="highlighter-rouge">states.set</code> is called on the slave it will forward it to the master. The master will replicate all events and changed states to its slaves.</p>
 <p class="img">
   <a href="/images/architecture/architecture-remote.png">
     <img src="/images/architecture/architecture-remote.png" />

developers/rest_api/index.html

@@ -477,7 +477,7 @@ The result will include any states that changed while the service was being exec
 <span class="p">}</span>
 </code></pre>
 </div>
-<p>It will return a message if event forwarding was cancelled successfully.</p>
+<p>It will return a message if event forwarding was canceled successfully.</p>
 <div class="language-json highlighter-rouge"><pre class="highlight"><code><span class="p">{</span><span class="w">
     </span><span class="nt">"message"</span><span class="p">:</span><span class="w"> </span><span class="s2">"Event forwarding cancelled."</span><span class="w">
 </span><span class="p">}</span><span class="w">