fix typos in docs

vapor-ware · Oct 10, 2017 · 329dedf · 329dedf
1 parent 0dbcf17
commit 329dedf
Show file tree

Hide file tree

Showing 2 changed files with 3 additions and 3 deletions.
diff --git a/docs/source/devicebuses.rst b/docs/source/devicebuses.rst
@@ -6,7 +6,7 @@ DeviceBus Interfaces
 ====================
 
 At the heart of Synse Server is the notion of "device bus" (or "devicebus"), which is so-named due to the original
-single-purpose PLC bus, and can now be said to describe "devices and busses" supported by Synse Server. Currently, there
+single-purpose PLC bus, and can now be said to describe "devices and buses" supported by Synse Server. Currently, there
 are six supported devicebus interfaces:
  - :ref:`synse-server-plc-device`
  - :ref:`synse-server-ipmi-device`

diff --git a/docs/source/running.rst b/docs/source/running.rst
@@ -13,7 +13,7 @@ started with
 
 But this won't do very much, since it will have no devices configured to issue commands to. To get Synse Server working
 with real or even emulated hardware, there is a bit of configuration that needs to be done. Below, there is a
-"Quick Start" approach to getting start with using Synse Server. After, the "Detailed Start" covers a bit more detail
+"Quick Start" approach to getting started with using Synse Server. After, the "Detailed Start" covers a bit more detail
 all the ways in which Synse Server can be configured for running.
 
 Quick Start
@@ -88,7 +88,7 @@ Synse Server devices are all set up by configuration. These configurations can e
 (if building a custom Synse Server image) or mounted into the container, which is the preferred approach as it is more
 flexible.
 
-When Synse Server starts, it reads in is configuration files to determine which devices are configured. By default,
+When Synse Server starts, it reads in configuration files to determine which devices should exist. By default,
 Synse Server is not configured with any devices, so it won't do much other than sit there.
 
 .. code-block:: json