svn commit: r1680065 - /accumulo/site/trunk/content/release_notes/1.7.0.mdtext

[kt...@apache.org]

Author: kturner
Date: Mon May 18 18:32:59 2015
New Revision: 1680065

URL: http://svn.apache.org/r1680065
Log:
ACCUMULO-3737 fixed some typos

Modified:
    accumulo/site/trunk/content/release_notes/1.7.0.mdtext

Modified: accumulo/site/trunk/content/release_notes/1.7.0.mdtext
URL: http://svn.apache.org/viewvc/accumulo/site/trunk/content/release_notes/1.7.0.mdtext?rev=1680065&r1=1680064&r2=1680065&view=diff
==============================================================================
--- accumulo/site/trunk/content/release_notes/1.7.0.mdtext (original)
+++ accumulo/site/trunk/content/release_notes/1.7.0.mdtext Mon May 18 18:32:59 2015
@@ -24,15 +24,15 @@ Apache Accumulo 1.7.0 is a release that
 
 ### Client Authentication with Kerberos
 
-Kerberos is far and away the de-facto means provide strong authentication across Hadoop
-and other related components. Kerberos uses requires a centralized key distribution center
+Kerberos is far and away the de-facto means to provide strong authentication across Hadoop
+and other related components. Kerberos requires a centralized key distribution center
 to authentication users who have credentials provided by an administrator. When Hadoop is
 configured for use with Kerberos, all users must provide Kerberos credentials to interact
 with the filesystem, launch YARN jobs, or even view certain web pages.
 
 While Accumulo has long supported operation on Hadoop with Kerberos enabled, it required
 Accumulo users to still use password-based authentication. [ACCUMULO-2815][ACCUMULO-2815]
-added support to Accumulo to allow Accumulo clients to use a single set of Kerberos
+added support allowing Accumulo clients to use a single set of Kerberos
 credentials to interact with Accumulo and all other Hadoop components.
 
 This authentication leverages the [Simple Authentication and Security Layer (SASL)][SASL]
@@ -61,7 +61,7 @@ This data-center replication feature is
 a disaster recovery strategy. Data can be automatically sent from a primary instance to one
 or more other Accumulo instances. Conversely to normal Accumulo operation in which ingest and
 query are strongly consistent, replication is a lazy, eventually consistent operation. This
-is desirable for replication as it prevent additional latency for ingest operations on the
+is desirable for replication as it prevents additional latency for ingest operations on the
 primary instance. Additionally, outages between the primary instance and replicas can sustain
 prolonged outages without any administrative overhead.