From b7b77cb26eb22f2ec17e9087cf5de686033ce886 Mon Sep 17 00:00:00 2001
From: eschao <esc.chao@gmail.com>
Date: Wed, 13 Dec 2017 11:12:11 +0800
Subject: [PATCH] Update README.md

---
 README.md | 7 +++++--
 1 file changed, 5 insertions(+), 2 deletions(-)

diff --git a/README.md b/README.md
index 098a07c..598a0bd 100644
--- a/README.md
+++ b/README.md
@@ -185,7 +185,7 @@ Calls **ParseConfigFile(interface{}, string)** to parse given configuration file
 
 If the configuration file is not given, the default configuration files: **config.json** and **config.yaml** will be located under the same folder with fixed searching order.
 
-The **config.json** will be always first located, if it doesn't exist, then checks **config.yaml**. If all of them are not found, parsing will fail.
+The **config.json** will always be located first, if it doesn't exist, then checks **config.yaml**. If all of them are not found, parsing will fail.
 ```golang
   dbConfig := Database{}
   config.ParseConfigFile(&dbConfig, "")
@@ -203,7 +203,7 @@ Run application like:
 ```
 **ParseConfig()** will analyze command line argument and extract **config.json** from argument **-c**
 
-### III. Multi-configurations 
+### III. Multi-Configurations 
 You can define all supported configuration tags in a structure and call corresponding functions in your desired order to parse.
 
 Examples:
@@ -247,6 +247,9 @@ Then, you can parse as below:
  if err != nil {
    err = config.ParseCli(&dbConfig)
  }
+ 
+ // check if all requried configurations are set
+ ...
 ```
 
 You don't need call all of them. Invokes parsing function that your need.