[freemarker] branch 2.3-gae updated: (Trivial fixes/additions in version history)

[dd...@apache.org]

This is an automated email from the ASF dual-hosted git repository.

ddekany pushed a commit to branch 2.3-gae
in repository https://gitbox.apache.org/repos/asf/freemarker.git


The following commit(s) were added to refs/heads/2.3-gae by this push:
     new 196d28d  (Trivial fixes/additions in version history)
196d28d is described below

commit 196d28d8482445bff0f2272d388c2b717d454361
Author: ddekany <dd...@apache.org>
AuthorDate: Sun Feb 16 19:06:28 2020 +0100

    (Trivial fixes/additions in version history)
---
 src/manual/en_US/book.xml | 13 ++++++++-----
 1 file changed, 8 insertions(+), 5 deletions(-)

diff --git a/src/manual/en_US/book.xml b/src/manual/en_US/book.xml
index a7d7200..89e0fb3 100644
--- a/src/manual/en_US/book.xml
+++ b/src/manual/en_US/book.xml
@@ -29262,7 +29262,9 @@ TemplateModel x = env.getVariable("x");  // get variable x</programlisting>
               property to <literal>BeansWrapper</literal>, and subclasses like
               <literal>DefaultObjectWrapper</literal>. This allows users to
               implement their own program logic to decide what members of
-              classes will be exposed to the templates.</para>
+              classes will be exposed to the templates. See See the <olink
+              targetdoc="api">FreeMarker Java API documentation</olink> for
+              more details.</para>
             </listitem>
 
             <listitem>
@@ -29312,10 +29314,11 @@ TemplateModel x = env.getVariable("x");  // get variable x</programlisting>
               <literal>BeansWrapper</literal>. The typical bad pattern is
               this: <literal>new
               Configuration(Configuration.getVersion())</literal>. Doing that
-              defeats the purpose of incompatibleImprovements, and makes
-              upgrading FreeMarker a potentially breaking change. Furthermore,
-              doing this probably won't be allowed starting from 2.4.0, and
-              will throw exception. So if above mistake is present in your
+              defeats the purpose of
+              <literal>incompatibleImprovements</literal>, and makes upgrading
+              FreeMarker a potentially breaking change. Furthermore, doing
+              this probably won't be allowed starting from 2.4.0, and will
+              throw exception. So if above mistake is present in your
               application, it should be fixed by setting
               <literal>incompatibleImprovements</literal> to the highest
               concrete version that's known to be compatible with the