jeena/home-assistant.github.io
1
0
Fork 0
Code Issues Pull requests Projects Packages Wiki Activity Actions

Various markdown, spelling, and grammar fixes #3 (#4510)

Browse source 
* ✅ Various markdown, spelling, and grammar fixes

* ✅ Various markdown, spelling, and grammar fixes

* ✅ Various markdown, spelling, and grammar fixes
This commit is contained in:
Franck Nijhof 2018-01-25 18:21:05 +01:00 • committed by Fabian Affolter
parent 42f9a8e5cd
commit 6224c71c08
98 changed files with 131 additions and 131 deletions
Download patch file Download diff file Expand all files Collapse all files

2
source/developers/architecture.markdown
View file

@ -16,7 +16,7 @@ For more information about each part in this overview, <a href='/blog/2014/12/26
* Home Control is responsible for collecting information and controlling devices.
* Home Automation triggers commands based on user configurations.
* Smart Home triggers commands based on previous behaviour.
* Smart Home triggers commands based on previous behavior.
<p class='img'>
<a href='{{site_root}}/images/architecture/home_automation_landscape.png' name='landscape'>

4
source/developers/development_guidelines.markdown
View file

@ -25,9 +25,9 @@ The maximum line length comes directly from the [PEP8 style guide](https://www.p
Those points may require that you adjust your IDE or editor settings.
## {% linkable_title Our recommandations %}
## {% linkable_title Our recommendations %}
For some cases [PEPs](https://www.python.org/dev/peps/) 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.
For some cases [PEPs](https://www.python.org/dev/peps/) 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.
### {% linkable_title Quotes %}

2
source/developers/development_submitting.markdown
View file

@ -39,7 +39,7 @@ Submit your improvements, fixes, and new features to Home Assistant one at a tim
* On GitHub, navigate to the main page of the Home Assistant repository.
* In the "Branch" menu, choose the branch that contains your commits (from your fork).
* To the right of the Branch menu, click **New pull request**.
* 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 (`dev`) else you will propose ALL committs between branches.
* 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 (`dev`) else you will propose ALL commits between branches.
* Type a title and complete the provided description for your pull request.
* Click **Create pull request**.

2
source/developers/development_validation.markdown
View file

@ -11,7 +11,7 @@ footer: true
The `configuration.yaml` file contains the configuration options for components and platforms. We use [voluptuous](https://pypi.python.org/pypi/voluptuous) 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.
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.
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.
Besides [voluptuous](https://pypi.python.org/pypi/voluptuous) default types, many custom types are available. For an overview, take a look at the [config_validation.py](https://github.com/home-assistant/home-assistant/blob/master/homeassistant/helpers/config_validation.py) helper.

2
source/developers/documentation/standards.markdown
View file

@ -66,4 +66,4 @@ redirect_from: /getting-started/android/
---
```
Adding a redirect also applies if you move content around in the [documention](/docs/).
Adding a redirect also applies if you move content around in the [documentation](/docs/).

2
source/developers/multiple_instances.markdown
View file

@ -11,7 +11,7 @@ footer: true
# {% linkable_title This has been deprecated and is no longer supported. %}
Home Assistant supports running multiple synchronised instances using a master-slave model. Whenever `events.fire` or `states.set` is called on the slave it will forward it to the master. The master will replicate all events and changed states to its slaves.
Home Assistant supports running multiple synchronized instances using a master-slave model. Whenever `events.fire` or `states.set` 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 class='img'>
<a href='/images/architecture/architecture-remote.png'>

2
source/developers/rest_api.markdown
View file

@ -515,7 +515,7 @@ Requires a JSON object that represents the API to cancel forwarding to.
}
```
It will return a message if event forwarding was cancelled successfully.
It will return a message if event forwarding was canceled successfully.
```json
{