changed superfluous mentions of v2.0 to match current release

Author: duncdrum

data/development-starter.xml

@@ -41,7 +41,7 @@
         </section>
         <section>
             <title>The Packaging</title>
-            <para>eXist-db 2.0 builds on the concept of self-contained, modular applications which
+            <para>eXist-db builds on the concept of self-contained, modular applications which
                 can be deployed into any database instance using a standardized packaging format.
                 Applications live inside the database, so application code, HTML views, associated
                 services and data all reside in the same place - though maybe in different root

data/repo.xml

@@ -8,7 +8,7 @@
         <title>Package Repository</title>
         <section>
             <title>Introduction</title>
-            <para>The eXist-db package repository is a central component of eXist-db 2.0. It makes
+            <para>The eXist-db package repository is a central component of eXist-db. It makes
                 it easy to manage and deploy external packages (.xar archives) which include
                 everything they need to run third party XQuery libraries, full applications or
                 other XML technology functionality. This document provides technical details on the
@@ -24,9 +24,9 @@
                 </listitem>
             </itemizedlist>
             <para>This split made it difficult to redistribute applications. For larger setups,
-            maintenance easily became tedious. To solve those problems, eXist-db 2.0 introduces the
+            maintenance easily became tedious. To solve those problems, eXist-db 2.0 introduced the
             concept of self-contained, modular applications which can be deployed into any database
-            instance using a standardized packaging format. The eXist-db 2.0 distribution is built around this
+            instance using a standardized packaging format. Later eXist-db distributions are built around this
             concept: documentation, examples and administration utilities have been moved out of the
             webapp directory and into separate application packages, which can be easily installed
             or removed on demand. The Dashboard is now the central hub for managing packages.</para>