Author: cbrisson
Date: Tue Oct  9 22:33:09 2018
New Revision: 1843359

URL: http://svn.apache.org/viewvc?rev=1843359&view=rev
Log:
[site/tools] Fix newsitem

Modified:
    velocity/site/cms/trunk/content/news.xml

Modified: velocity/site/cms/trunk/content/news.xml
URL: 
http://svn.apache.org/viewvc/velocity/site/cms/trunk/content/news.xml?rev=1843359&r1=1843358&r2=1843359&view=diff
==============================================================================
--- velocity/site/cms/trunk/content/news.xml (original)
+++ velocity/site/cms/trunk/content/news.xml Tue Oct  9 22:33:09 2018
@@ -11,18 +11,23 @@
         </categories>
         <text><![CDATA[
         The Velocity developers are pleased to announce the release of 
Velocity Tools 3.0.
+
         
         Velocity Tools is a library of template tools and helpers to ease the 
use of the
         Apache Velocity template engine in standalone applications and in 
webapps.
 
-        Velocity Tools brings a few new context tools (CollectionTool, 
JsonTool) and bugfixes
+
+        Velocity Tools 3.0 brings a few new context tools (CollectionTool, 
JsonTool) and bugfixes
         along with a complete rewrite for some other tools (BrowserTool, 
ImportTool, XmlTool).
-        It now uses Velocity Engine 2.0, and SLF4J.
+        It now uses Velocity Engine 2.0 and SLF4J.
+
 
         For a complete list of changes, please visit 
{{{https://dist.apache.org/repos/dist/release/velocity/tools/3.0/release-notes.html}the
 Velocity Tools 3.0 releases nodes}}.
 
+
         For notes on upgrading from Velocity Engine 1.x and Velocity Tools 
2.0, see {{{http://velocity.apache.org/engine/2.0/upgrading.html}Velocity 
Engine 2.0 Upgrading section}}
-        and {{{http://velocity.apache.org/tools/3.0/upgrading.html}Velocity 
Tools 3.0 Upgrading section}.
+        and {{{http://velocity.apache.org/tools/3.0/upgrading.html}Velocity 
Tools 3.0 Upgrading section}}.
+
 
         Downloads of Velocity Tools 3.0 are available 
{{{http://velocity.apache.org/download.cgi#tools}here}}.
 


Reply via email to