Grammar fixes in app-local-errors README

Change-Id: I217403a4a94f12b692a877418b34ed6a1cf8e142
Signed-off-by: Gunnar Mills <gmills@us.ibm.com>

1 files changed, 6 insertions, 6 deletions

diff --git a/app-local-errors/README.md b/app-local-errors/README.md
index 835b1d5..403c593 100644
--- a/app-local-errors/README.md
+++ b/app-local-errors/README.md
@@ -1,5 +1,5 @@
 ## Introduction

-Document captures steps for adding application specific error yaml files

+This document captures steps for adding application specific error yaml files

 

 ### Write app specific error yaml files

 Write error yamls for your application and place them in your application

@@ -9,7 +9,7 @@ Refer to *Host.errors.yaml* at
 https://github.com/openbmc/openpower-debug-collector/blob/master/org/open_power/

 

 ### Makefile rules to run sdbus++ on error yaml files

-Modify the Makefile.am as shown bellow for generation of error.cpp and erorr.hpp

+Modify the Makefile.am as shown below for generation of error.cpp and erorr.hpp

 ```

 org/open_power/Host/error.hpp: ${srcdir}/org/open_power/Host.errors.yaml

     @mkdir -p `dirname $@`

@@ -30,20 +30,20 @@ Refer to **do_install_append** method in
 https://github.com/openbmc/openbmc/blob/master/meta-openbmc-machines/meta-openpower/common/recipes-phosphor/debug/

 

 ### Establish dependency with phosphor-logging

-Establish debendency with phosphor-logging to ensure that error yaml files are

+Establish dependency with phosphor-logging to ensure that error yaml files are

 copied to a known location before phosphor logging parses the error yaml files

 

 Refer to **phosphor-logging-error-logs-native.bbappend** at

 https://github.com/openbmc/openbmc/blob/master/meta-openbmc-machines/meta-openpower/common/recipes-phosphor/debug/

 

-###Generate application local elog-errors.hpp file

+### Generate application local elog-errors.hpp file

 Applications should be independently compilable so it cannot have a

 dependency on the elog-errors.hpp generated by phosphor-logging

 

 Generate application specific elog-errors.hpp using the elog-gen.py

-parser. In future the same will be generated through autotools.

+parser. In the future, elog-errors.hpp will be generated through autotools.

 

-The application specific elog-errors.hpp is for the build purpose and the

+The application specific elog-errors.hpp is for the build process and the

 elog-errors.hpp from phosphor-logging will be used during elog commit/report

 

 #### Example