Updated project plan for Acceleo.
diff --git a/acceleo/plan-juno.xml b/acceleo/plan-juno.xml
index f9ed3cc..c58e280 100644
--- a/acceleo/plan-juno.xml
+++ b/acceleo/plan-juno.xml
@@ -69,16 +69,16 @@
</target_environments>
<compatibility_with_previous_releases>
<html:div>
- <p><strong>API compatibility. </strong> Acceleo 4 will be compatible with the extension points defined
- in Acceleo 3.0, 3.1 and 3.2 but some Java APIs may be deprecated and replaced with new APIs.</p>
+ <html:p><html:strong>API compatibility. </html:strong> Acceleo 4 will be compatible with the extension points defined
+ in Acceleo 3.0, 3.1 and 3.2 but some Java APIs may be deprecated and replaced with new APIs.</html:p>
- <p><strong>Workspace compatibility. </strong>A workspace being used with Acceleo 3.0, 3.1 or 3.2
+ <html:p><html:strong>Workspace compatibility. </html:strong>A workspace being used with Acceleo 3.0, 3.1 or 3.2
will still open and work with Acceleo 4. In general, though, once a workspace is opened with Acceleo 4
there is no guarantee it will continue to work with older versions (that is, there may be some one-time
- migration of some workspace meta data that prevents it being usable in older versions.</p>
+ migration of some workspace meta data that prevents it being usable in older versions.</html:p>
- <p><strong>Project compatibility. </strong>A project being used with Acceleo 3.0, 3.1 or 3.2
- will stay compatible with Acceleo 4.</p>
+ <html:p><html:strong>Project compatibility. </html:strong>A project being used with Acceleo 3.0, 3.1 or 3.2
+ will stay compatible with Acceleo 4.</html:p>
</html:div>
</compatibility_with_previous_releases>
<themes_and_priorities>
