[MNGSITE-393] Remove Maven 2 references (#446)

and other minor copy edits

Author: elharo

content/apt/guides/introduction/introduction-to-profiles.apt

@@ -176,8 +176,8 @@ mvn groupId:artifactId:goal -P profile-1,profile-2,?profile-3
 </profiles>
 +---+
 
-  Ranges can also be used as of Maven 2.1 (refer to the {{{/enforcer/enforcer-rules/versionRanges.html} Enforcer Version Range Syntax}} for more information).
-  Range values must start with either <<<[>>> or <<<(>>> otherwise the value is interpreted as prefix.
+  {{{/enforcer/enforcer-rules/versionRanges.html} Ranges}}  can also be used.
+  Range values must start with either <<<[>>> or <<<(>>>. Otherwise, the value is interpreted as a prefix.
   The following honours versions 1.3, 1.4 and 1.5.
 
 +---+
@@ -337,7 +337,7 @@ mvn groupId:artifactId:goal -Denvironment=test
 </profiles>
 +---+
 
-  As of Maven 2.0.9, the tags <<<\<exists\>>>> and <<<\<missing\>>>> could be interpolated. Supported variables are
+  The tags <<<\<exists\>>>> and <<<\<missing\>>>> can be interpolated. Supported variables are
   system properties like <<<$\{user.home\}>>> and environment variables like <<<$\{env.HOME\}>>>. Please note that
   properties and values defined in the POM itself are not available for interpolation here, e.g. the above example
   activator cannot use <<<$\{project.build.directory\}>>> but needs to hard-code the path <<<target>>>.
@@ -350,7 +350,7 @@ mvn groupId:artifactId:goal -Denvironment=test
 
 ** Deactivating a profile
 
-  Starting with Maven 2.0.10, one or more profiles can be deactivated using the command line by prefixing their
+  One or more profiles can be deactivated using the command line by prefixing their
   identifier with either the character '!' or '-' as shown below:
 
 -----
@@ -453,19 +453,17 @@ mvn groupId:artifactId:goal -P -profile-1,-profile-2,-?profile-3
   Another reason is that this POM info is sometimes being reused from the
   parent POM.
 
-  External files such as <<<settings.xml>>> and <<<profiles.xml>>> also does not support elements
+  External files such as <<<settings.xml>>> and <<<profiles.xml>>> also do not support elements
   outside the POM-profiles. Let us take this scenario for elaboration. When the
-  effective POM get deployed to a remote repository, any person can pickup
+  effective POM is deployed to a remote repository, any person can pickup
   its info out of the repository and use it to build a Maven project directly.
   Now, imagine that if we can set profiles in dependencies, which is very
   important to a build, or in any other elements outside POM-profiles in
   <<<settings.xml>>> then most probably we cannot expect someone else to use that
   POM from the repository and be able to build it. And we have to also think about
   how to share the <<<settings.xml>>> with others. Note that too many files to
-  configure is very confusing and very hard to maintain.
+  configure are very confusing and very hard to maintain.
   Bottom line is that since this is build data, it should be in the POM.
-  One of the goals in Maven 2 is to consolidate all the information needed to
-  run a build into a single file, or file hierarchy which is the POM.
 
 * Profile Order