[maven-doxia-site] branch master updated: [MNGSITE-393] Remove maven 2 info

[el...@apache.org]

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

elharo pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/maven-doxia-site.git


The following commit(s) were added to refs/heads/master by this push:
     new c918f58  [MNGSITE-393] Remove maven 2 info
c918f58 is described below

commit c918f588009738b5da46d9c992215677769aa513
Author: Elliotte Rusty Harold <el...@users.noreply.github.com>
AuthorDate: Sun Jun 7 07:54:39 2020 -0400

    [MNGSITE-393] Remove maven 2 info
    
    @hboutemy
---
 content/apt/references/doxia-apt.apt | 5 +----
 1 file changed, 1 insertion(+), 4 deletions(-)

diff --git a/content/apt/references/doxia-apt.apt b/content/apt/references/doxia-apt.apt
index 8d674c1..171241d 100644
--- a/content/apt/references/doxia-apt.apt
+++ b/content/apt/references/doxia-apt.apt
@@ -32,11 +32,8 @@ Enhancements to the APT format
 
   In the following we provide a list of differences/enhancements to the
   original {{{./apt-format.html}APT}} format that were incorporated in Doxia.
-  Note that the original specification still applies to <<Doxia-1.0>>
-  (used e.g. by Maven-2.0.x), the changes outlined here only apply from
-  <<Doxia-1.1>> (used by Maven >= 2.1.x).
   Apart from some exceptions, these differences are usually
-  'backwards-compatible', i.e. any document that gets correctly processed
+  'backwards-compatible'. That is, any document that gets correctly processed
   by Aptconvert should also
   be a valid Doxia input file and lead to identical results when processed
   by a Doxia parser.