MODE-794 Updated the Getting Started and Reference Guide documents wi…

…th information about the shareable nodes feature.

git-svn-id: https://svn.jboss.org/repos/modeshape/trunk@2082 76366958-4244-0410-ad5e-bbfabb93f86b

docs/gettingstarted/src/main/docbook/en-US/content/conclusion.xml

@@ -53,22 +53,21 @@
 	<sect1 id="future">
 		<title>Future directions</title>
 	  <para>
-			With version &versionNumber;, ModeShape introduces support for the <link linkend="&JSR283;">JCR 2.0 API</link>,
-			improvements to existing connectors, and quite a few <ulink url="&ReleaseNotes;">bug fixes and improvements</ulink>.
+			With version &versionNumber;, ModeShape introduces clustering support, shareable nodes, a technology preview of the JBoss AS deployment kit,
+			a JDBC driver, and quite a few <ulink url="&ReleaseNotes;">bug fixes and improvements</ulink>.
 		</para>
-		<para>This means that <emphasis role="strong">ModeShape now implements all of the required JCR 2.0 features</emphasis>: 
+		<para>This means that <emphasis role="strong">ModeShape implements all of the required JCR 2.0 features</emphasis>: 
 			repository acquisition, authentication, reading/navigating, query, export, node type discovery, and permissions and 
 			capability checking. 
 			<emphasis role="strong">ModeShape also implements most of the optional JCR 2.0 features</emphasis>:
 			writing, import, observation, workspace management, versioning, locking, node type management, same-name siblings, 
-			and orderable child nodes.
-			The remaining optional features (shareable nodes, access control management, lifecycle management, 
+			orderable child nodes, and shareable nodes.
+			The remaining optional features (access control management, lifecycle management, 
 			retention and hold, and transactions) may be introduced in future versions.
 		</para>
 		<para>
-			We also plan to add support for clustering multiple ModeShape engines spread across multiple JVM processes.
-			And each expect to introduce more connectors and sequencers to our library.
-			Other items on our long-term roadmap include a web user interface, Seam integration, and integration with even more kinds of
+			The next release will add more sequencers and improved monitoring and managing in the JBoss AS embedded console.
+			Other items on our long-term roadmap include more connectors and sequencers, a web user interface, Seam integration, and integration with even more kinds of
 			information systems and repositories.
 		</para>
 	</sect1>

docs/gettingstarted/src/main/docbook/en-US/content/introduction.xml

@@ -49,7 +49,7 @@
     , which is capable of persisting the state of an object graph so that it can be read back in at a later time. However, Java
     serialization can quickly become tricky if the classes are changed, and so it's beneficial usually when the information is
     persisted for a very short period of time. For example, serialization is sometimes used to send an object graph from one
-    process to another.  Using serialization for longer-term storage of information is more risky.
+    process to another.  Using serialization for longer-term storage of information is far less useful.
   </para>
   <para>
     One of the more popular and widely-used persistence technologies is the <emphasis>relational database</emphasis>. 
@@ -63,7 +63,7 @@
   <para>
     <emphasis>Object-relational mapping</emphasis>
     libraries automate the creation of this mapping layer and result in far less code that is much more maintainable with
-    performance that is often as good as (if not better than) handwritten JDBC code. The new
+    performance that is often as good as (if not better than) handwritten JDBC code. The
     <ulink url="http://java.sun.com/developer/technicalArticles/J2EE/jpa/">Java Persistence API (JPA)</ulink>
     provide a standard mechanism for defining the mappings (through annotations) and working with these entity objects. Several
     commercial and open-source libraries implement JPA, and some even offer additional capabilities and features that go beyond
@@ -76,10 +76,10 @@
     While relational databases and JPA are solutions that work well for many applications, they are more limited in cases when the
     information structure is highly flexible, the structure is not known <emphasis>a priori</emphasis>, or that structure is
  		subject to frequent change and customization. In these situations, <emphasis>content repositories</emphasis>
-    may offer a better choice for persistence. Content repositories are almost a hybrid with the storage capabilities of
- 		relational databases and the flexibility offered by other systems, such as using files.  Content repositories also
-    typically provide other capabilities as well, including versioning, indexing, search, access control,
-    transactions, and observation. Because of this, content repositories are used by content management systems (CMS), document
+    may offer a better choice for persistence. Content repositories offer the storage capabilities of
+ 		relational databases with the flexibility offered by other systems, such as using files.  Content repositories also
+    typically provide other capabilities as well, including hierarchical organization, versioning, indexing, search, access control,
+    transactions, and observation. Content repositories are often used by content management systems (CMS), document
     management systems (DMS), and other applications that manage electronic files (e.g., documents, images, multi-media, web
     content, etc.) and metadata associated with them (e.g., author, date, status, security information, etc.). The
     <ulink url="http://www.jcp.org/en/jsr/detail?id=170">Content Repository for Java technology API</ulink>
@@ -101,12 +101,13 @@
 	<sect1 id="what_is_jboss_modeshape">
 		<title>ModeShape</title>
 		<para>
-			What makes JCR interesting, however, is that a JCR implementation provides all these features and capabilities regardless
-			of where or how that information is persisted or stored.  <emphasis>This is in fact the main purpose of ModeShape:
-			provide a JCR implementation that provides access to content stored in many different kinds of systems.</emphasis>
-			A ModeShape repository isn't yet another silo of information, but rather it's a JCR view of the information you already have
-			in your environment: files systems, databases, other repositories, services, applications, etc. <emphasis role="strong">ModeShape can 
-			help you understand the systems and information you already have, through a standard Java API.</emphasis>
+			What makes JCR interesting, however, is that a JCR implementation provides all these features and capabilities without exposing
+			where or how that information is stored.  While other JCR implementations embed their own persistence technology, JCR becomes
+			really interesting when it is used on top of existing information. <emphasis>This is in fact the main purpose of ModeShape:
+			provide a JCR implementation that provides access to content stored in many different kinds of systems, including the federation
+			of multiple systems.</emphasis>  A ModeShape repository isn't yet another silo of information, but rather it's a JCR view of the 
+			information you already have in your environment: files systems, databases, other repositories, services, applications, etc. 
+			<emphasis role="strong">ModeShape can help you understand the systems and information you already have, through a standard Java API.</emphasis>
 		</para>
 		<para>
 			Of course when you start providing a unified view of all this information, you start recognizing the need to store more
@@ -120,10 +121,10 @@
 			access, and use the information.
 		</para>
 		<para>
-			So, ModeShape <emphasis>is</emphasis> a JCR 2.0 implementation that can automatically sequence files loaded into the repository,
-			and it can be used as a traditional JCR silo repository.
-			But it <emphasis>can also</emphasis> let your applications use the JCR API to access the content in other systems, and
-			can unify the content from multiple external systems and multiple storage systems to provide a single, federated repository.
+			So, ModeShape <emphasis>is</emphasis> a JCR 2.0 implementation that can be used as a traditional self-contained repository.
+			But ModeShape can do so much more. It can automatically sequence files loaded into the repository, making it easier to reuse
+			that information. It also lets your applications use the JCR API to access the content in other systems, and can unify the 
+			content from multiple external systems and multiple storage systems to provide a single, federated repository.
 		</para>
 	</sect1>
 	<sect1 id="introduction_whats_next">

docs/gettingstarted/src/main/docbook/en-US/content/use_cases.xml

@@ -141,7 +141,7 @@
 		<para>
 			As we'll see in the <link linkend="using_modeshape">next chapter</link>, this is actually the way in which ModeShape manages
 			its own configuration.  In the embedded case, the configuration repository is simply a local (in-memory) repository that
-			is populated by the configuration file (or programmatic API).  In a clustered mode, the repository is centralized.  But either
+			is populated by the configuration file (or programmatic API).  In a clustered mode, the repository can be centralized.  But either
 			way, to ModeShape the configuration is always defined in a repository.
 		</para>
 	</sect1>