Spelling fixes
Spelling errors found using github.com/lucasdemarchi/codespell
A tool to fix common misspellings.
This tool is licensed under GNU General Public License, version 2.
Change-Id: Ia3dd39a0f7aa9e9146c0dc9888160e77d312615c
Signed-off-by: Gunnar Mills <gmills@us.ibm.com>
diff --git a/MAINTAINERS b/MAINTAINERS
index f37c155..1893eb4 100644
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@ -89,17 +89,17 @@
# THIS REPOSITORY HAS A DIFFERENT SUBMISSION PROCESS: this is a subtree in
# @openbmc and is synced by the maintainer using git-subtree. Please submit
-# changes aginst @openbmc.
+# changes against @openbmc.
@meta-aspeed://*
# THIS REPOSITORY HAS A DIFFERENT SUBMISSION PROCESS: this is a subtree in
# @openbmc and is synced by the maintainer using git-subtree. Please submit
-# changes aginst @openbmc.
+# changes against @openbmc.
@meta-openpower://*
# THIS REPOSITORY HAS A DIFFERENT SUBMISSION PROCESS: this is a subtree in
# @openbmc and is synced by the maintainer using git-subtree. Please submit
-# changes aginst @openbmc.
+# changes against @openbmc.
@meta-phosphor://*
@obmc-console://*
diff --git a/kernel-development.md b/kernel-development.md
index 76d8ab8..b646cf2 100644
--- a/kernel-development.md
+++ b/kernel-development.md
@@ -23,7 +23,7 @@
Once you are sure a driver needs to be written, you should develop and test the driver, before sending it upstream to the relevant maintainers. You should feel welcome to cc the OpenBMC list when sending upstream, so other kernel developers can provide input where appropriate. Be sure to follow the (upstream development process)[https://www.kernel.org/doc/Documentation/process/submitting-patches.rst].
-In the past patches underwent 'pre-review' on the OpenBMC mailing list. While this is useful for developers who are not familiar with writing kenrel code, it has lead to confusion about the upstreaming process, so now we do all of our development in the community.
+In the past patches underwent 'pre-review' on the OpenBMC mailing list. While this is useful for developers who are not familiar with writing kernel code, it has lead to confusion about the upstreaming process, so now we do all of our development in the community.
Once the driver has been accepted upstream, send the good news to the OpenBMC list with a reference to the upstream tree. This may be Linus' tree, or it might be one of the subsystem maintainers. From there the OpenBMC kernel team can decide how best to include your code in the OpenBMC tree.
@@ -48,7 +48,7 @@
- Witherspoon, an OpenPower Power9 box containing an ast2500 with NCSI networking
- qemu-plametto and qemu-romulus
-Before submitting patches it is recommended you boot test on at least the Qemu platforms, and whatever hardware you have availaible.
+Before submitting patches it is recommended you boot test on at least the Qemu platforms, and whatever hardware you have available.
# Tips and Tricks
diff --git a/rest-api.md b/rest-api.md
index aa9e924..7147d52 100644
--- a/rest-api.md
+++ b/rest-api.md
@@ -225,7 +225,7 @@
c) The client needs to send, over the websocket, a JSON dictionary, comprising
of key-value pairs. This dictionary serves as the "events filter". All the
- keys are optinal, so the dictionary can be empty if no filtering is desired.
+ keys are optional, so the dictionary can be empty if no filtering is desired.
The filters represented by each of the key-value pairs are ORed.
One of the supported keys is "paths". The corresponding value is an array of
@@ -282,7 +282,7 @@
d) The rest server on the BMC will respond over the websocket when a D-Bus event
occurs, considering the client supplied filters. The rest servers notifies
- about InterfacesAdded and PropertiesChanged events. The reponse is a JSON
+ about InterfacesAdded and PropertiesChanged events. The response is a JSON
dictionary as follows :
InterfacesAdded
diff --git a/rfc-obmc-service-iface.md b/rfc-obmc-service-iface.md
index eacf0a3..dcc77a5 100644
--- a/rfc-obmc-service-iface.md
+++ b/rfc-obmc-service-iface.md
@@ -135,7 +135,7 @@
busctl call org.openbmc.LogManager /org/openbmc/LogManager/rsyslog org.freedesktop.DBus.Properties Get ss org.openbmc.Errl port
```
-#### Get All configuration properties of the logging sevice.
+#### Get All configuration properties of the logging service.
```
busctl call org.openbmc.LogManager /org/openbmc/LogManager/rsyslog org.freedesktop.DBus.Properties GetAll s org.openbmc.Errl
```