Index: /FCKeditor/trunk/_whatsnew.html
===================================================================
--- /FCKeditor/trunk/_whatsnew.html	(revision 865)
+++ /FCKeditor/trunk/_whatsnew.html	(revision 866)
@@ -35,8 +35,41 @@
 		New Features and Improvements:</p>
 	<ul>
+		<li>[<a target="_blank" href="http://dev.fckeditor.net/ticket/494">#494</a>] Introduced the <strong>new Style System</strong>. We are not anymore relaying on browser features
+			to apply and remove styles, which guarantees that the editor will <strong>behave in the
+			same way in all browsers</strong>. It is an incredibly flexible system, which aims to fit
+			all developer's needs, from Flash content or HTML4 to XHTML 1.0 Strict or XHTML
+			1.1:
+			<ul>
+				<li>All basic formatting features, like Bold and Italic, can be precisely controlled
+					by using the configuration file (<b>CoreStyles</b> setting). It means that now,
+					the Bold button, for example, can produce &lt;b&gt;, &lt;strong&gt;, &lt;span class...&gt;,
+					&lt;span style...&gt; or anything the developer prefers.</li>
+				<li>Again with the <b>CoreStyles</b> setting, each block format, font, size, and even
+					the color pickers can precisely reflect end developer's needs.</li>
+				<li>Because of the above changes, font sizes are much more flexible. <b>Any kind of
+					font unit</b> can be used, including a mix of units.</li>
+				<li>All styles, including toolbar bottom styles, are precisely controlled when being
+					applied to the document. FCKeditor uses an element table derived from the <b>W3C XHTML
+						DTDs</b> to precisely create the elements, guarantee standards compliant code.</li>
+				<li><b>No more &lt;font&gt; tags</b>... well... actually, the system is so flexible
+					that it is up to you to use them or not.</li>
+				<li>It is possible to configure FCKeditor to produce a truly <b>semantic aware </b>and<b>
+					XHTML 1.1 compliant </b>code. Check out sample14.html.</li>
+				<li>It's also possible to precisely control which inline elements must be removed with
+					the &quot;Remove All&quot; button, by using the &quot;<b>RemoveFormatTags</b>&quot;
+					setting.</li>
+				<li>Paragraph <b>indentation</b> and <b>justification</b> now uses style attributes
+					and don't create unnecessary elements, and &lt;blockquote&gt; is not anymore used
+					for it. Now, even CSS classes can be used to indent or align text.</li>
+				<li>All paragraph formatting features work well when EnterMode=br.</li>
+			</ul>
+		</li>
+		<li>[<a target="_blank" href="http://dev.fckeditor.net/ticket/1197">#1197</a>] The toolbar
+			now presents a <strong>new button for Blockquote</strong>. The indentation button
+			will not anymore be used for that.</li>
 		<li>[<a target="_blank" href="http://dev.fckeditor.net/ticket/915">#915</a>] The undo/redo
 			system has been revamped to work the same across Internet Explorer and Gecko-based
 			browsers (e.g. Firefox). A number of critical bugs in the undo/redo system are also
-			fixed.</li>
+			fixed. </li>
 		<li>[<a target="_blank" href="http://dev.fckeditor.net/ticket/194">#194</a>] The editor
 			now uses the <strong>Data Processor</strong> technology, which makes it possible
@@ -113,6 +146,6 @@
 		<li>[<a target="_blank" href="http://dev.fckeditor.net/ticket/560">#560</a>] The PHP
 			connector will work better if the connector or the userfiles folder is a symlink.</li>
-		<li>[<a target="_blank" href="http://dev.fckeditor.net/ticket/784">#784</a>] Fixed an
-			uninitialized $php_errormsg in the PHP connector.</li>
+		<li>[<a target="_blank" href="http://dev.fckeditor.net/ticket/784">#784</a>] Fixed a
+			non initialized $php_errormsg in the PHP connector.</li>
 		<li>[<a target="_blank" href="http://dev.fckeditor.net/ticket/802">#802</a>] The replace
 			dialog will now advance its searching position correctly and is able to search for
@@ -125,7 +158,7 @@
 			target="_blank" href="http://dev.fckeditor.net/ticket/395">#395</a>] [<a target="_blank"
 				href="http://dev.fckeditor.net/ticket/932">#932</a>] Clicking outside the editor
-			it was possible to paste or apply formating to the rest of the page in IE.</li>
+			it was possible to paste or apply formatting to the rest of the page in IE.</li>
 		<li>[<a target="_blank" href="http://dev.fckeditor.net/ticket/137">#137</a>] Fixed FCKConfig.TabSpaces
-			being ignored, and weired behaviors when pressing tab in edit source mode.</li>
+			being ignored, and weird behaviors when pressing tab in edit source mode.</li>
 		<li>[<a target="_blank" href="http://dev.fckeditor.net/ticket/268">#268</a>] Fixed special
 			XHTML characters present in event attribute values being converted inappropriately
@@ -134,5 +167,5 @@
 			was cut sometimes in IE to just one row if there are multiple instances of the editor.</li>
 		<li>[<a target="_blank" href="http://dev.fckeditor.net/ticket/515">#515</a>] Tables
-			in Firefox didn't inherint font styles properly in Standards mode.</li>
+			in Firefox didn't inherit font styles properly in Standards mode.</li>
 		<li>[<a target="_blank" href="http://dev.fckeditor.net/ticket/321">#321</a>] If FCKeditor
 			is initially hidden in Firefox it will no longer be necessary to call the oEditor.MakeEditable()
@@ -215,5 +248,6 @@
 			the issue where the cursor or selection positions are not restored with undo/redo
 			commands correctly in IE, under some circumstances. </li>
-		<li>[<a target="_blank" href="http://dev.fckeditor.net/ticket/1160">#1160</a>] [<a target="_blank" href="http://dev.fckeditor.net/ticket/1184">#1184</a>] Home, End
+		<li>[<a target="_blank" href="http://dev.fckeditor.net/ticket/1160">#1160</a>] [<a
+			target="_blank" href="http://dev.fckeditor.net/ticket/1184">#1184</a>] Home, End
 			and Tab keys are working properly for numeric fields in dialogs. </li>
 		<li>[<a target="_blank" href="http://dev.fckeditor.net/ticket/68">#68</a>] The style
@@ -221,5 +255,5 @@
 		<li>[<a target="_blank" href="http://dev.fckeditor.net/ticket/525">#525</a>] The union
 			if successive DIVs will work properly now if EnterMode!=div.</li>
-		<li>[<a target="_blank" href="http://dev.fckeditor.net/ticket/1227">#1227</a>] The color 
+		<li>[<a target="_blank" href="http://dev.fckeditor.net/ticket/1227">#1227</a>] The color
 			commands used an unnecessary temporary variable. Thanks to Matthias Miller</li>
 	</ul>
