Grammar fixes for README.md
Change-Id: Iaa1c4bc0680c5b0a0cf512e0c61f6b8241070551
Signed-off-by: Gunnar Mills <gmills@us.ibm.com>
diff --git a/README.md b/README.md
index 74f58bf..0e7beb2 100644
--- a/README.md
+++ b/README.md
@@ -1,16 +1,16 @@
# Introduction
-`phosphor-time-manager` is the time manager service that implements dbus
+`phosphor-time-manager` is the time manager service that implements D-Bus
interface `xyz/openbmc_project/Time/EpochTime.interface.yaml`.
-User can get or set the BMC's or HOST's time via this interface.
+The user can get or set the BMC's or HOST's time via this interface.
### General usage
-The service `xyz.openbmc_project.Time.Manager` provides two objects on dbus:
+The service `xyz.openbmc_project.Time.Manager` provides two objects on D-Bus:
* /xyz/openbmc_project/time/bmc
* /xyz/openbmc_project/time/host
where each object implements interface `xyz.openbmc_project.Time.EpochTime`.
-User can directly get or set the property `Elasped` of the objects to get or set
+The user can directly get or set the property `Elapsed` of the objects to get or set
the time. For example on an authenticated session:
* To get BMC's time:
@@ -37,15 +37,15 @@
### Time settings
Getting BMC or HOST time is always allowed, but setting the time may not be
-allowed depending on below two settings in settings manager.
+allowed depending on the below two settings in the settings manager.
* TimeSyncMethod
- * NTP: Time is set via NTP server.
- * MANUAL: Time is set manually.
+ * NTP: The time is set via NTP server.
+ * MANUAL: The time is set manually.
* TimeOwner
* BMC: BMC owns the time and can set the time.
* HOST: Host owns the time and can set the time.
- * SPLIT: BMC and Host owns separate time.
+ * SPLIT: BMC and Host own separate time.
* BOTH: Both BMC and Host can set the time.
A summary of which cases the time can be set on BMC or HOST:
@@ -62,11 +62,11 @@
MANUAL | BOTH | OK | OK
### Special note on host on
-When host is on, the changes of the above time mode/owner are not applied but
+When the host is on, the changes of the above time mode/owner are not applied but
deferred. The changes of the mode/owner are saved to persistent storage.
-When host is off, the saved mode/owner are read from persistent storage and are
+When the host is off, the saved mode/owner are read from persistent storage and are
applied.
-Note: user can set the time mode and owner in settings daemon at any time,
-but time manager applying them is governed by the above condition.
+Note: A user can set the time mode and owner in the settings daemon at any time,
+but the time manager applying them is governed by the above condition.