Fix simple typo: problemtic -> problematic (#1059)

Plus rephrase the comment for greater clarity.

diff --git a/jinja2/runtime.py b/jinja2/runtime.py
index 92cd99a64442f4670ee1725c3bc94b7a9df5f7a4..b37465a950f1fa8d5fff233c4e968f58f234865e 100644 (file)
--- a/jinja2/runtime.py
+++ b/jinja2/runtime.py
@@ -500,9 +500,8 @@ class Macro(object):
         # decide largely based on compile-time information if a macro is
         # safe or unsafe.  While there was a volatile mode it was largely
         # unused for deciding on escaping.  This turns out to be
-        # problemtic for macros because if a macro is safe or not not so
-        # much depends on the escape mode when it was defined but when it
-        # was used.
+        # problematic for macros because whether a macro is safe depends not
+        # on the escape mode when it was defined, but rather when it was used.
         #
         # Because however we export macros from the module system and
         # there are historic callers that do not pass an eval context (and