docs: few touch ups and typos fixed

Signed-off-by: Mihai Tudor Panu <mihai.tudor.panu@intel.com>
This commit is contained in:
Mihai Tudor Panu
2015-03-04 11:22:56 -08:00
parent 9dcef6d7bb
commit b4c265005f
6 changed files with 23 additions and 19 deletions

View File

@ -3,7 +3,7 @@ Porting a module from Arduino {#porting}
Porting arduino libraries to libmraa as UPM libraries is usually fairly easy.
The issues typically come from misunderstanding of how a non real time OS deals
with interupts and timers. It also highly depends on the sensor. A concrete
with interrupts and timers. It also highly depends on the sensor. A concrete
example is explained in detail on @ref max31855
### Adding a new module to UPM
@ -36,9 +36,9 @@ required to talk to the board's IO. An I2c sensor will create a
mraa_i2c_context, keep it as a private member and require a bus number and slave
address in it's constructor.
Typically in sensors a simple object->read() function is prefered, depending on
your sensor/actuaotr this may or may not be easy or not even make sense. Most
UPM apis have a simple set of functions.
Typically in sensors a simple object->read() function is preferred, depending on
your sensor/actuator this may or may not be easy or not even make sense. Most
UPM APIs have a simple set of functions.
### Mapping arduino API to libmraa
@ -59,7 +59,7 @@ the UPM build system.
The last step is when you're happy with your module and it works send us a pull
request! We'd love to include your sensor in our repository.
If you don't like github you can also send brendan.le.foll@intel.com a git
formatted patch if your sensor. More details are on @ref contributions and on
If you don't like github you can also send mihai.tudor.panu@intel.com a git
formatted patch of your sensor. More details are on @ref contributions and on
https://help.github.com/articles/creating-a-pull-request