Fixed a couple of typos in the documentation

[eval.git] / t / moe / config_parser.py

diff --git a/t/moe/config_parser.py b/t/moe/config_parser.py
index ad10b02ed365d2d2cc47b2ca842039d169b3aa45..a6aac797e9337be0048bb8b479f844fc2d785d87 100644 (file)
--- a/t/moe/config_parser.py
+++ b/t/moe/config_parser.py
@@ -2,7 +2,7 @@ r"""
 Simple Moe configuration file syntax parser. 
 
 Generally, whitespace and comments are alowed everywhere except in variable names and inside expressions,
-``\\n`` ends a ``COMMENT``.
+``\n`` ends a ``COMMENT``.
 
 ``FILE``, ``BLOCK``, ``STATEMENT``, ``OPERATION``, ``SUBTREE``, ``CONDITION``, ``FORMULA``, ``AND``, ``OR`` 
 and ``NOT`` ignore any preceding whitespace. 
@@ -35,7 +35,7 @@ The configuration syntax is the following::
     ECHAR = re('([^\{}]|\\|\{|\}|\\n)*')
     VARNAME = re('[a-zA-Z0-9-_]+(\.[a-zA-Z0-9-_]+)*')
 
-.. todo:: should whitespace (incl. '\n') be allowed (almost) everywhere? 
+.. todo:: should whitespace (incl. '\\n') be allowed (almost) everywhere? 
          can comment be anywhere whitespace can?
 .. note:: ';' or '\\n' is currently required even after CONDITION and SUBTREE block 
 .. note:: Formula can contain additional/unnecessary parentheses