diff options
author | Matt Riddle <mriddle89@gmail.com> | 2014-07-21 13:01:35 -0500 |
---|---|---|
committer | Matt Riddle <mriddle89@gmail.com> | 2014-07-21 13:01:35 -0500 |
commit | 5e4eb1c3c5a036946636986189ad520e9e46dd2a (patch) | |
tree | 64522ab97e3f475c0c948db753adb1f14afc1306 | |
parent | 641949a55dfecb99cb22050b30987da554227561 (diff) | |
download | mixlib-config-5e4eb1c3c5a036946636986189ad520e9e46dd2a.tar.gz |
Fix typos
-rw-r--r-- | README.md | 4 |
1 files changed, 2 insertions, 2 deletions
@@ -112,9 +112,9 @@ Misspellings are a common configuration problem, and Mixlib::Config has an answ end ``` -Now if a user types `fielname "~/output-mine.txt"` in their configuration file, it will toss an exception telling them that the option "fielname" is unknown. If you do not set config_strict_mode, the fielname option will be merrily set and the application just won't know about it. +Now if a user types `filename "~/output-mine.txt"` in their configuration file, it will toss an exception telling them that the option "filename" is unknown. If you do not set config_strict_mode, the filename option will be merrily set and the application just won't know about it. -Different config_contexts can have different strict modes; but they inherit the strict mode of their parent if you don't explicitly set it. So setting it once at the top level is sufficient. In the above example, `logging.base_naem 'mylog'` will raise an error. +Different config_contexts can have different strict modes; but they inherit the strict mode of their parent if you don't explicitly set it. So setting it once at the top level is sufficient. In the above example, `logging.base_name 'mylog'` will raise an error. In conclusion: *always set config_strict_mode to true*. You know you want to. |