incubator-freemarker git commit: (Trying to trigger github mirroring...)

[dd...@apache.org]

Repository: incubator-freemarker
Updated Branches:
  refs/heads/3 cae86e18e -> 591c69264


(Trying to trigger github mirroring...)


Project: http://git-wip-us.apache.org/repos/asf/incubator-freemarker/repo
Commit: http://git-wip-us.apache.org/repos/asf/incubator-freemarker/commit/591c6926
Tree: http://git-wip-us.apache.org/repos/asf/incubator-freemarker/tree/591c6926
Diff: http://git-wip-us.apache.org/repos/asf/incubator-freemarker/diff/591c6926

Branch: refs/heads/3
Commit: 591c692644bada56d08b17bc9246dd19e662aee5
Parents: cae86e1
Author: ddekany <dd...@apache.org>
Authored: Fri Sep 1 21:15:53 2017 +0200
Committer: ddekany <dd...@apache.org>
Committed: Fri Sep 1 21:15:53 2017 +0200

----------------------------------------------------------------------
 FM3-CHANGE-LOG.txt | 12 ++++++------
 1 file changed, 6 insertions(+), 6 deletions(-)
----------------------------------------------------------------------


http://git-wip-us.apache.org/repos/asf/incubator-freemarker/blob/591c6926/FM3-CHANGE-LOG.txt
----------------------------------------------------------------------
diff --git a/FM3-CHANGE-LOG.txt b/FM3-CHANGE-LOG.txt
index 012f1a0..77f5911 100644
--- a/FM3-CHANGE-LOG.txt
+++ b/FM3-CHANGE-LOG.txt
@@ -31,8 +31,8 @@ Note that the template converter tool (freemarker-converter) can automatically a
 templates. But changes that aren't purely syntactical (but behavioral) often can't be treated with 100% safety or at
 all, in which case it's always noted for that change as "Converter note:".
 
-Major changes / features
-------------------------
+Major template language changes / features
+------------------------------------------
 
 - Switched to camel case as the only supported naming convention. This is as if in FM2 you set the "namingConvention"
   configuration setting to "camelCase", however the "namingConvention" setting was removed, as no other convention will
@@ -64,8 +64,8 @@ Major changes / features
   - In FM2, the same macro could be called with specifying all parameters by position, or by specifying all parameters
     by name. In FM3 that won't work anymore, as now a parameter is either strictly positional or strictly named.
 
-Smaller changes
----------------
+Smaller template language changes
+---------------------------------
 
 Node: Changes already mentioned above aren't repeated here!
 
@@ -229,8 +229,8 @@ Major changes / features
   [Note: This is in very early stage, as of 2017-07-06.]
 
 
-Smaller changes (categorized)
------------------------------
+Smaller Java API changes (categorized)
+--------------------------------------
 
 Node: Changes already mentioned above aren't repeated here!