diff --git a/doc/faq.html b/doc/faq.html
index 5dae4e0..c0603fe 100644
--- a/doc/faq.html
+++ b/doc/faq.html
@@ -302,12 +302,6 @@ struct MyPump : PumpBase
  local transitions are supposed to work, see
  <a href="http://thread.gmane.org/gmane.comp.lib.boost.user/18641">here</a> 
  for more information</li>
-<li>The origin of a transition to history must not be a direct or indirect 
-inner state of the state containing the history pseudo state. UML2.0 
-explicitly allows this, the semantics of the library will be changed 
-accordingly for the 1.35 release, see
-<a href="http://thread.gmane.org/gmane.comp.lib.boost.user/18641">here</a> for 
-more information</li>
  <li>There is no direct support for the UML2.0 elements entry point and exit 
  point. However, both can easily be simulated, the former with a typedef and 
  the latter with a state that is a template (with the transition destination 
diff --git a/doc/future_and_history.html b/doc/future_and_history.html
index 2d861c9..b7a55d5 100644
--- a/doc/future_and_history.html
+++ b/doc/future_and_history.html
@@ -45,8 +45,6 @@
   review):</p>
 
   <ol>
-    <li>Make transitions to history UML2.0 compliant, see
-    <a href="faq.html#Uml2">here</a> for more information</li>
     <li>Optimize state-entry and state-exit for speed and code-size</li>
 
     <li>Implement <code>simple_state::triggering_event()</code>, which
@@ -165,6 +163,8 @@
     <li>Declared <code>state_base::~state_base virtual</code> for GCC. This 
     makes state exit slightly slower but does away with loads of &quot;has 
     virtual functions but non-virtual destructor&quot; warnings</li>
+    <li>Made transitions to history UML2.0 compliant, see
+    <a href="faq.html#Uml2">here</a> for more information</li>
   </ul>
 
   <p>17 December, 2005</p>