accumulo-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From mwa...@apache.org
Subject [accumulo-website] branch master updated: ACCUMULO-4735 Fixed typos and spelling errors (#34)
Date Fri, 03 Nov 2017 15:47:11 GMT
This is an automated email from the ASF dual-hosted git repository.

mwalch pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/accumulo-website.git


The following commit(s) were added to refs/heads/master by this push:
     new cba2cca  ACCUMULO-4735 Fixed typos and spelling errors (#34)
cba2cca is described below

commit cba2cca49e5729866a608f75fefa388229df7aaf
Author: Mike Walch <mwalch@apache.org>
AuthorDate: Fri Nov 3 11:47:10 2017 -0400

    ACCUMULO-4735 Fixed typos and spelling errors (#34)
---
 _docs-2-0/administration/configuration-management.md        |  2 +-
 _docs-2-0/administration/in-depth-install.md                | 12 ++++++------
 _docs-2-0/administration/kerberos.md                        |  8 ++++----
 _docs-2-0/administration/replication.md                     |  4 ++--
 _docs-2-0/administration/ssl.md                             |  4 ++--
 _docs-2-0/development/development_tools.md                  |  2 +-
 _docs-2-0/development/iterators.md                          |  6 +++---
 _docs-2-0/development/proxy.md                              |  2 +-
 _docs-2-0/development/security.md                           |  2 +-
 _docs-2-0/getting-started/quick-install.md                  |  4 ++--
 _docs-2-0/getting-started/shell.md                          |  2 +-
 _docs-2-0/getting-started/table_design.md                   |  2 +-
 _docs-2-0/troubleshooting/advanced.md                       | 10 +++++-----
 _posts/blog/2014-05-03-accumulo-classloader.md              |  2 +-
 _posts/blog/2016-11-16-simpler-scripts-and-config.md        |  6 +++---
 _posts/blog/2017-03-06-security-performance-implications.md |  2 +-
 _posts/blog/2017-04-21-introducing-uno-and-muchos.md        |  4 ++--
 _posts/release/2014-03-06-accumulo-1.5.1.md                 |  2 +-
 _posts/release/2014-05-02-accumulo-1.6.0.md                 |  4 ++--
 _posts/release/2014-09-25-accumulo-1.6.1.md                 |  2 +-
 _posts/release/2015-05-18-accumulo-1.7.0.md                 |  2 +-
 _posts/release/2015-09-19-accumulo-1.5.2.md                 |  2 +-
 _posts/release/2016-06-22-accumulo-1.7.2.md                 |  4 ++--
 _posts/release/2016-09-06-accumulo-1.8.0.md                 |  6 +++---
 _posts/release/2016-09-18-accumulo-1.6.6.md                 |  4 ++--
 _posts/release/2017-02-26-accumulo-1.8.1.md                 |  2 +-
 contributor/git.md                                          |  2 +-
 contributor/making-release.md                               |  2 +-
 contributor/verifying-release.md                            |  4 ++--
 29 files changed, 55 insertions(+), 55 deletions(-)

diff --git a/_docs-2-0/administration/configuration-management.md b/_docs-2-0/administration/configuration-management.md
index 5090dc6..92ede68 100644
--- a/_docs-2-0/administration/configuration-management.md
+++ b/_docs-2-0/administration/configuration-management.md
@@ -19,7 +19,7 @@ The configuration locations above are described in detail below.
 ### Default values
 
 All [properties][props] have a default value that is listed for each property on the [properties][props]
page. Default values are set in the source code.
-While defalt values have the lowest precendence, they are usually optimal.  However, there
are cases where a change can increase query and ingest performance.
+While default values have the lowest precedence, they are usually optimal.  However, there
are cases where a change can increase query and ingest performance.
 
 ### accumulo-site.xml
 
diff --git a/_docs-2-0/administration/in-depth-install.md b/_docs-2-0/administration/in-depth-install.md
index 532fcc3..ded3fec 100644
--- a/_docs-2-0/administration/in-depth-install.md
+++ b/_docs-2-0/administration/in-depth-install.md
@@ -436,7 +436,7 @@ Make sure the host in question has the new configuration, or else the
tablet
 server won't start; at a minimum this needs to be on the host(s) being added,
 but in practice it's good to ensure consistent configuration across all nodes.
 
-### Decomissioning a Tablet Server
+### Decommissioning a Tablet Server
 
 If you need to take a node out of operation, you can trigger a graceful shutdown of a tablet
 server. Accumulo will automatically rebalance the tablets across the available tablet servers.
@@ -536,12 +536,12 @@ that the only volume displayed is the volume from the current namenode's
HDFS UR
 
     Listing volumes referenced in accumulo.root tablets section
             Volume : hdfs://namenode.example.com:8020/accumulo
-    Listing volumes referenced in accumulo.root deletes section (volume replacement occurrs
at deletion time)
+    Listing volumes referenced in accumulo.root deletes section (volume replacement occurs
at deletion time)
 
     Listing volumes referenced in accumulo.metadata tablets section
             Volume : hdfs://namenode.example.com:8020/accumulo
 
-    Listing volumes referenced in accumulo.metadata deletes section (volume replacement occurrs
at deletion time)
+    Listing volumes referenced in accumulo.metadata deletes section (volume replacement occurs
at deletion time)
 
 After verifying the current volume is correct, shut down the cluster and transition HDFS
to the HA nameservice.
 
@@ -573,12 +573,12 @@ new nameservice volume shows up with `accumulo admin volumes`.
     Listing volumes referenced in accumulo.root tablets section
             Volume : hdfs://namenode.example.com:8020/accumulo
             Volume : hdfs://nameservice1/accumulo
-    Listing volumes referenced in accumulo.root deletes section (volume replacement occurrs
at deletion time)
+    Listing volumes referenced in accumulo.root deletes section (volume replacement occurs
at deletion time)
 
     Listing volumes referenced in accumulo.metadata tablets section
             Volume : hdfs://namenode.example.com:8020/accumulo
             Volume : hdfs://nameservice1/accumulo
-    Listing volumes referenced in accumulo.metadata deletes section (volume replacement occurrs
at deletion time)
+    Listing volumes referenced in accumulo.metadata deletes section (volume replacement occurs
at deletion time)
 
 Some erroneous GarbageCollector messages may still be seen for a small period while data
is transitioning to
 the new volumes. This is expected and can usually be ignored.
@@ -709,7 +709,7 @@ Each release of Accumulo is built with a specific version of Apache
 Hadoop, Apache ZooKeeper and Apache Thrift.  We expect Accumulo to
 work with versions that are API compatible with those versions.
 However this compatibility is not guaranteed because Hadoop, ZooKeeper
-and Thift may not provide guarantees between their own versions. We
+and Thrift may not provide guarantees between their own versions. We
 have also found that certain versions of Accumulo and Hadoop included
 bugs that greatly affected overall stability.  Thrift is particularly
 prone to compatibility changes between versions and you must use the
diff --git a/_docs-2-0/administration/kerberos.md b/_docs-2-0/administration/kerberos.md
index d3a041b..29529e4 100644
--- a/_docs-2-0/administration/kerberos.md
+++ b/_docs-2-0/administration/kerberos.md
@@ -12,7 +12,7 @@ A centralized key-distribution center (KDC) is the service that coordinates
 authentication between a client and a server. Clients and servers use "tickets",
 obtained from the KDC via a password or a special file called a "keytab", to
 communicate with the KDC and prove their identity. A KDC administrator must
-create the principal (name for the client/server identiy) and the password
+create the principal (name for the client/server identity) and the password
 or keytab, securely passing the necessary information to the actual user/service.
 Properly securing the KDC and generated ticket material is central to the security
 model and is mentioned only as a warning to administrators running their own KDC.
@@ -29,7 +29,7 @@ using GSSAPI that Kerberos implements.
 
 Kerberos is a very complicated software application and is deserving of much
 more description than can be provided here. An [explain like I`m 5](http://www.roguelynn.com/words/explain-like-im-5-kerberos/)
-blog post is very good at distilling the basics, while [MIT Keberos's project page](http://web.mit.edu/kerberos/)
+blog post is very good at distilling the basics, while [MIT Kerberos's project page](http://web.mit.edu/kerberos/)
 contains lots of documentation for users or administrators. Various Hadoop "vendors"
 also provide free documentation that includes step-by-step instructions for
 configuring Hadoop and ZooKeeper (which will be henceforth considered as prerequisites).
@@ -123,7 +123,7 @@ server processes don't have an interactive console to enter a password
into.
 kadmin.local -q "xst -k accumulo.hostname.keytab accumulo/host.domain.com"
 ```
 
-To simplify deployments, at thet cost of security, all Accumulo principals could
+To simplify deployments, at the cost of security, all Accumulo principals could
 be globbed into a single keytab
 
 ```
@@ -568,7 +568,7 @@ on, is extremely important when negotiating an SASL connection. This problem
com
 servers are not configured to listen on the address denoted by their FQDN.
 
 The values in the Accumulo "hosts" files (In `accumulo/conf`: `masters`, `monitors`, `tservers`,
`tracers`,
-and `gc`) should match the instance componentof the Kerberos server principal (e.g. `host`
in `accumulo/host@EXAMPLE.COM`).
+and `gc`) should match the instance component of the Kerberos server principal (e.g. `host`
in `accumulo/host@EXAMPLE.COM`).
 
 **Q**: After configuring my system for Kerberos, server processes come up normally and I
can interact with the system. However,
 when I attempt to use the "Recent Traces" page on the Monitor UI I get a stacktrace similar
to:
diff --git a/_docs-2-0/administration/replication.md b/_docs-2-0/administration/replication.md
index 9cd5586..628222c 100644
--- a/_docs-2-0/administration/replication.md
+++ b/_docs-2-0/administration/replication.md
@@ -338,7 +338,7 @@ Due to the asynchronous nature of replication and the expectation that
hardware
 it is generally not recommended to not configure replication on a table which has Iterators
set which are not idempotent.
 While the replication implementation can make some simple assertions to try to avoid re-replication
of data, it is not
 presently guaranteed that all data will only be sent to a peer once. Data will be replicated
at least once. Typically,
-this is not a problem as the VersioningIterator will automaticaly deduplicate this over-replication
because they will
+this is not a problem as the VersioningIterator will automatically deduplicate this over-replication
because they will
 have the same timestamp; however, certain Combiners may result in inaccurate aggregations.
 
 As a concrete example, consider a table which has the SummingCombiner configured to sum all
values for
@@ -403,7 +403,7 @@ The structure of the key-value is as follows:
 <HDFS_uri_to_WAL> repl:<local_table_id> [] -> <protobuf>
 ```
 
-This entry is created based on a replication entry from the Accumlo metadata table, and is
deleted from the replication table
+This entry is created based on a replication entry from the Accumulo metadata table, and
is deleted from the replication table
 when the WAL has been fully replicated to all remote Accumulo tables.
 
 ### Work section
diff --git a/_docs-2-0/administration/ssl.md b/_docs-2-0/administration/ssl.md
index a104adf..9aad37e 100644
--- a/_docs-2-0/administration/ssl.md
+++ b/_docs-2-0/administration/ssl.md
@@ -6,7 +6,7 @@ order: 8
 
 Accumulo, through Thrift's TSSLTransport, provides the ability to encrypt
 wire communication between Accumulo servers and clients using secure
-sockets layer (SSL). SSL certifcates signed by the same certificate authority
+sockets layer (SSL). SSL certificates signed by the same certificate authority
 control the "circle of trust" in which a secure connection can be established.
 Typically, each host running Accumulo processes would be given a certificate
 which identifies itself.
@@ -121,4 +121,4 @@ keytool -import -trustcacerts -alias server-crt -file server.crt -keystore
serve
 ```
 
 The `server.jks` file is the Java keystore containing the certificate for a given host. The
above
-methods are equivalent whether the certficate is generate for an Accumulo server or a client.
+methods are equivalent whether the certificate is generate for an Accumulo server or a client.
diff --git a/_docs-2-0/development/development_tools.md b/_docs-2-0/development/development_tools.md
index 54cceed..01bceb9 100644
--- a/_docs-2-0/development/development_tools.md
+++ b/_docs-2-0/development/development_tools.md
@@ -10,7 +10,7 @@ Accumulo has several tools that can help developers test their code.
 
 [MiniAccumuloCluster] is a standalone instance of Apache Accumulo for testing. It will
 create Zookeeper and Accumulo processes that write all of their data to a single local
-directory. [MiniAccumuloCluster] makes it easy to code agaist a real Accumulo instance.
+directory. [MiniAccumuloCluster] makes it easy to code against a real Accumulo instance.
 Developers can write realistic-to-end integration tests that mimic the use of a normal
 Accumulo instance.
 
diff --git a/_docs-2-0/development/iterators.md b/_docs-2-0/development/iterators.md
index 11e30b5..cb4e37b 100644
--- a/_docs-2-0/development/iterators.md
+++ b/_docs-2-0/development/iterators.md
@@ -198,7 +198,7 @@ while (!overSizeLimit(batch)) {
         batch.add(new KeyValue(key, val)
         if (systemDataSourcesChanged()) {
             // code does not show isolation case, which will
-            // keep using same data sources until a row boundry is hit 
+            // keep using same data sources until a row boundary is hit
             range = new Range(key, false, range.endKey(), range.endKeyInclusive());
             break;
         }
@@ -422,5 +422,5 @@ identify common pitfalls in user-created Iterators.
 [iterator-test-harness]: {{ page.docs_baseurl }}/development/development_tools#iterator-test-harness
 [BatchScanner]: {{ page.javadoc_core}}/org/apache/accumulo/core/client/BatchScanner.html
 [Scanner]: {{ page.javadoc_core }}/org/apache/accumulo/core/client/Scanner.html
-[BatchWriter]: {{ page.javdoc_core }}/org/apache/accumulo/core/client/BatchWriter.html
-[WholeRowIterator]: {{ page.javdoc_core }}/org/apache/accumulo/core/iterators/user/WholeRowIterator.html
+[BatchWriter]: {{ page.javadoc_core }}/org/apache/accumulo/core/client/BatchWriter.html
+[WholeRowIterator]: {{ page.javadoc_core }}/org/apache/accumulo/core/iterators/user/WholeRowIterator.html
diff --git a/_docs-2-0/development/proxy.md b/_docs-2-0/development/proxy.md
index 2cca885..8a33b8f 100644
--- a/_docs-2-0/development/proxy.md
+++ b/_docs-2-0/development/proxy.md
@@ -66,7 +66,7 @@ to how generate source from a thrift file.
 ### Thrift library
 
 Language-specific Thrift libraries can be installed using an OS or language package manager
(i.e gem, pip, etc).
-For example, `pip install thrift` will install Python-specific thrift libaries on your machine.
+For example, `pip install thrift` will install Python-specific thrift libraries on your machine.
 
 ## Proxy Client Examples
 
diff --git a/_docs-2-0/development/security.md b/_docs-2-0/development/security.md
index 2e65d22..951d213 100644
--- a/_docs-2-0/development/security.md
+++ b/_docs-2-0/development/security.md
@@ -117,7 +117,7 @@ authorization, and permission handling.
 Authentication verifies the identity of a user. In Accumulo, authentication occurs when
 the `getConnector` method of [Instance] is called with a principal (i.e username)
 and an [AuthenticationToken] which is an interface with multiple implementations. The most
-common implementation is [PasswordToken] which is the default authenticaton method for Accumulo
+common implementation is [PasswordToken] which is the default authentication method for Accumulo
 out of the box.
 
 ```java
diff --git a/_docs-2-0/getting-started/quick-install.md b/_docs-2-0/getting-started/quick-install.md
index 8346bb5..037725b 100644
--- a/_docs-2-0/getting-started/quick-install.md
+++ b/_docs-2-0/getting-started/quick-install.md
@@ -59,7 +59,7 @@ Follow the steps below to configure `accumulo-env.sh`:
 
 2. Accumulo tablet servers are configured by default to use 1GB of memory (768MB is allocated
to
    JVM and 256MB is allocated for native maps). Native maps are allocated memory equal to
33% of
-   the tserver JVM heap. The table below can be used if you would like to change tsever memory
+   the tserver JVM heap. The table below can be used if you would like to change tserver
memory
    usage in the `JAVA_OPTS` section of `accumulo-env.sh`:
 
     | Native? | 512MB             | 1GB               | 2GB                 | 3GB       
   |
@@ -104,7 +104,7 @@ Each method above has instructions below.
 
 ### Run Accumulo processes
 
-Start Accumulo processes (tserver, master, moniitor, etc) using command below:
+Start Accumulo processes (tserver, master, monitor, etc) using command below:
 
     accumulo tserver
 
diff --git a/_docs-2-0/getting-started/shell.md b/_docs-2-0/getting-started/shell.md
index 7796d10..43f1136 100644
--- a/_docs-2-0/getting-started/shell.md
+++ b/_docs-2-0/getting-started/shell.md
@@ -27,7 +27,7 @@ and then display the following prompt:
 
 ## Basic Administration
 
-The `tables` command will list all existings tables.
+The `tables` command will list all existing tables.
 
     root@myinstance> tables
     accumulo.metadata
diff --git a/_docs-2-0/getting-started/table_design.md b/_docs-2-0/getting-started/table_design.md
index af5b17f..87b747d 100644
--- a/_docs-2-0/getting-started/table_design.md
+++ b/_docs-2-0/getting-started/table_design.md
@@ -190,7 +190,7 @@ including nodes, their attributes, and connections to other nodes.
 
 Rather than storing individual events, Entity-Attribute or Graph tables store
 aggregate information about the entities involved in the events and the
-relationships between entities. This is often preferrable when single events aren't
+relationships between entities. This is often preferable when single events aren't
 very useful and when a continuously updated summarization is desired.
 
 The physical schema for an entity-attribute or graph table is as follows:
diff --git a/_docs-2-0/troubleshooting/advanced.md b/_docs-2-0/troubleshooting/advanced.md
index 95d9ce6..474a942 100644
--- a/_docs-2-0/troubleshooting/advanced.md
+++ b/_docs-2-0/troubleshooting/advanced.md
@@ -113,7 +113,7 @@ Ensure your client has adequate memory and is not being swapped out to
disk.
 
 ## HDFS Failures
 
-**I had disasterous HDFS failure.  After bringing everything back up, several tablets refuse
to go online.**
+**I had disastrous HDFS failure.  After bringing everything back up, several tablets refuse
to go online.**
 
 Data written to tablets is written into memory before being written into indexed files. 
In case the server
 is lost before the data is saved into a an indexed file, all data stored in memory is first
written into a
@@ -170,7 +170,7 @@ but the basic approach is:
 * Stop all accumulo processes on all nodes
 * Move the accumulo directory in HDFS out of the way:
        $ hadoop fs -mv /accumulo /corrupt
-* Re-initalize accumulo
+* Re-initialize accumulo
 * Recreate tables, users and permissions
 * Import the directories under `/corrupt/tables/<id>` into the new instance
 
@@ -206,7 +206,7 @@ When an Accumulo data file is corrupt, the most reliable way to restore
Accumulo
 operations is to replace the missing file with an ``empty'' file so that
 references to the file in the METADATA table and within the tablet server
 hosting the file can be resolved by Accumulo. An empty file can be created using
-the CreateEmpty utiity:
+the CreateEmpty utility:
 
     $ accumulo org.apache.accumulo.core.file.rfile.CreateEmpty /path/to/empty/file/empty.rf
 
@@ -245,7 +245,7 @@ WAL file, never being able to succeed.
 
 In the cases where the WAL file's original contents are unrecoverable or some degree
 of data loss is acceptable (beware if the WAL file contains updates to the Accumulo
-metadat table!), the following process can be followed to create an valid, empty
+metadata table!), the following process can be followed to create an valid, empty
 WAL file. Run the following commands as the Accumulo unix user (to ensure that
 the proper file permissions in HDFS)
 
@@ -326,7 +326,7 @@ omission of new data.
 
 Yes, you can recover them by running the LocalWALRecovery utility (not available in 1.8 and
later) on each node that needs recovery performed. The utility
 will default to using the directory specified by `logger.dir.walog` in your configuration,
or can be
-overriden by using the `--local-wal-directories` option on the tool. It can be invoked as
follows:
+overridden by using the `--local-wal-directories` option on the tool. It can be invoked as
follows:
 
     accumulo org.apache.accumulo.tserver.log.LocalWALRecovery
 
diff --git a/_posts/blog/2014-05-03-accumulo-classloader.md b/_posts/blog/2014-05-03-accumulo-classloader.md
index 83fbe33..84539bc 100644
--- a/_posts/blog/2014-05-03-accumulo-classloader.md
+++ b/_posts/blog/2014-05-03-accumulo-classloader.md
@@ -54,7 +54,7 @@ The goal here is to enable multiple tenants to share the same Accumulo instance.
 </property>
 ```
 
-Context classloaders do not have to be defined in the accumulo-site.xml file. The "general.vfs.context.classpath.{context}"
property can be defined on the table either programatically or manually in the shell. Then
set the "table.classpath.context" property on your table.
+Context classloaders do not have to be defined in the accumulo-site.xml file. The "general.vfs.context.classpath.{context}"
property can be defined on the table either programmatically or manually in the shell. Then
set the "table.classpath.context" property on your table.
 
 ### Known Issues
 
diff --git a/_posts/blog/2016-11-16-simpler-scripts-and-config.md b/_posts/blog/2016-11-16-simpler-scripts-and-config.md
index 1ad3f22..7a83349 100644
--- a/_posts/blog/2016-11-16-simpler-scripts-and-config.md
+++ b/_posts/blog/2016-11-16-simpler-scripts-and-config.md
@@ -21,9 +21,9 @@ bootstrap_hdfs.sh    config.sh                start-daemon.sh          
       s
 ```
 
 The number of scripts made it difficult to know which scripts to use.  If you added the `bin/`
directory to your 
-`PATH`, it could add unecessary commands to your PATH or cause commands to be overriden due
generic names
+`PATH`, it could add unnecessary commands to your PATH or cause commands to be overridden
due generic names
 (like 'start-all.sh'). The number of scripts were reduced by removing scripts that are no
longer used and combining
-scripts with similiar functionality.
+scripts with similar functionality.
 
 Starting with 2.0.0, Accumulo will only have 4 scripts in its `bin/` directory:
 
@@ -129,7 +129,7 @@ Services:
   monitor     Accumulo monitor
   master      Accumulo master
   tserver     Accumulo tserver
-  tracer      Accumulo tracter
+  tracer      Accumulo tracer
 
 Commands:
   start       Starts service
diff --git a/_posts/blog/2017-03-06-security-performance-implications.md b/_posts/blog/2017-03-06-security-performance-implications.md
index 01d2410..4f196e9 100644
--- a/_posts/blog/2017-03-06-security-performance-implications.md
+++ b/_posts/blog/2017-03-06-security-performance-implications.md
@@ -143,7 +143,7 @@ in the output generated by [ContinuousStatsCollector](https://github.com/apache/
 
 
 As can be seen in the plots above, the different security settings have 
-relatively consistent, discernable median run characteristics.  The big
+relatively consistent, discernible median run characteristics.  The big
 dip in each TOTAL_INGEST coincides with a large number of major
 compactions, a rate decrease for TABLE_RECS, and a decrease in 
 AVG_FILES/TABLET. 
diff --git a/_posts/blog/2017-04-21-introducing-uno-and-muchos.md b/_posts/blog/2017-04-21-introducing-uno-and-muchos.md
index 6117619..1c28593 100644
--- a/_posts/blog/2017-04-21-introducing-uno-and-muchos.md
+++ b/_posts/blog/2017-04-21-introducing-uno-and-muchos.md
@@ -89,8 +89,8 @@ Use `muchos ssh` to ssh to the cluster and `muchos terminate` to terminate
all E
 
 ## Conclusion
 
-Uno and Muchos automate installing Accumulo for developmment and testing. While not recommended
for production
-use at this time, Muchos is a great reference for running Accumulo in production. System
admistrators can
+Uno and Muchos automate installing Accumulo for development and testing. While not recommended
for production
+use at this time, Muchos is a great reference for running Accumulo in production. System
administrators can
 reference the [Ansible] code in Muchos to automate management of their own clusters.
 
 [install]: https://github.com/apache/accumulo/blob/master/INSTALL.md
diff --git a/_posts/release/2014-03-06-accumulo-1.5.1.md b/_posts/release/2014-03-06-accumulo-1.5.1.md
index 780129b..e5dc95b 100644
--- a/_posts/release/2014-03-06-accumulo-1.5.1.md
+++ b/_posts/release/2014-03-06-accumulo-1.5.1.md
@@ -129,7 +129,7 @@ to disk before unloading a Tablet.
 When using Accumulo 1.5 and Hadoop 2, Accumulo will call hsync() on HDFS.
 Calling hsync improves durability by ensuring data is on disk (where other older 
 Hadoop versions might lose data in the face of power failure); however, calling
-hsync frequently does noticably slow writes. A simple work around is to increase 
+hsync frequently does noticeably slow writes. A simple work around is to increase
 the value of the tserver.mutation.queue.max configuration parameter via accumulo-site.xml.
 
 A value of "4M" is a better recommendation, and memory consumption will increase by
diff --git a/_posts/release/2014-05-02-accumulo-1.6.0.md b/_posts/release/2014-05-02-accumulo-1.6.0.md
index 916c0c9..7277179 100644
--- a/_posts/release/2014-05-02-accumulo-1.6.0.md
+++ b/_posts/release/2014-05-02-accumulo-1.6.0.md
@@ -216,7 +216,7 @@ If this is happening often a possible work around is to set `general.rpc.timeout
  * [ACCUMULO-1407][ACCUMULO-1407] Fix documentation for deleterows
  * [ACCUMULO-1428][ACCUMULO-1428] Document native maps
  * [ACCUMULO-1946][ACCUMULO-1946] Include dfs.datanode.synconclose in hdfs configuration
documentation
- * [ACCUMULO-1956][ACCUMULO-1956] Add section on decomissioning or adding nodes to an Accumulo
cluster
+ * [ACCUMULO-1956][ACCUMULO-1956] Add section on decommissioning or adding nodes to an Accumulo
cluster
  * [ACCUMULO-2441][ACCUMULO-2441] Document internal state stored in RFile names
  * [ACCUMULO-2590][ACCUMULO-2590] Update public API in readme to clarify what's included
 
@@ -326,7 +326,7 @@ The following acronyms are used in the test testing table.
 [ACCUMULO-1933]: https://issues.apache.org/jira/browse/ACCUMULO-1933 "Make unit on memory
parameters case-insensitive"
 [ACCUMULO-1946]: https://issues.apache.org/jira/browse/ACCUMULO-1946 "Include dfs.datanode.synconclose
in hdfs configuration documentation"
 [ACCUMULO-1950]: https://issues.apache.org/jira/browse/ACCUMULO-1950 "Reduce the number of
calls to hsync"
-[ACCUMULO-1956]: https://issues.apache.org/jira/browse/ACCUMULO-1956 "Add section on decomissioning
or adding nodes to an Accumulo cluster"
+[ACCUMULO-1956]: https://issues.apache.org/jira/browse/ACCUMULO-1956 "Add section on decommissioning
or adding nodes to an Accumulo cluster"
 [ACCUMULO-1958]: https://issues.apache.org/jira/browse/ACCUMULO-1958 "Range constructor lacks
key checks, should be non-public"
 [ACCUMULO-1985]: https://issues.apache.org/jira/browse/ACCUMULO-1985 "Cannot bind monitor
on remote host to all interfaces"
 [ACCUMULO-1994]: https://issues.apache.org/jira/browse/ACCUMULO-1994 "Proxy does not handle
Key timestamps correctly"
diff --git a/_posts/release/2014-09-25-accumulo-1.6.1.md b/_posts/release/2014-09-25-accumulo-1.6.1.md
index 46c3a45..6b5e81e 100644
--- a/_posts/release/2014-09-25-accumulo-1.6.1.md
+++ b/_posts/release/2014-09-25-accumulo-1.6.1.md
@@ -92,7 +92,7 @@ parameter, like [ACCUMULO-2360][3], to prevent this error.
 ### Offline tables can prevent tablet balancing
 
 Before 1.6.1, when a table with many tablets was created, ingested into, and
-taken offline, tablet balancing may have stoppped. This would happen if there
+taken offline, tablet balancing may have stopped. This would happen if there
 were tablet migrations for the table, because the migrations couldn't occur.
 The balancer will not run when there are outstanding migrations; therefore, a
 system could become unbalanced. [ACCUMULO-2694][4] introduces a fix to ensure
diff --git a/_posts/release/2015-05-18-accumulo-1.7.0.md b/_posts/release/2015-05-18-accumulo-1.7.0.md
index 144ec1a..1230d69 100644
--- a/_posts/release/2015-05-18-accumulo-1.7.0.md
+++ b/_posts/release/2015-05-18-accumulo-1.7.0.md
@@ -124,7 +124,7 @@ files in a table.
 
 These provided convenience options to select files execute using a specialized
 compaction strategy. Options were also added to the shell to specify an
-arbitrary compaction strategy. The option to specify an arbitrry compaction
+arbitrary compaction strategy. The option to specify an arbitrary compaction
 strategy is mutually exclusive with the file selection and file creation
 options, since those options are unique to the specialized compaction strategy
 provided. See `compact --help` in the shell for the available options.
diff --git a/_posts/release/2015-09-19-accumulo-1.5.2.md b/_posts/release/2015-09-19-accumulo-1.5.2.md
index 9569f6b..1a73486 100644
--- a/_posts/release/2015-09-19-accumulo-1.5.2.md
+++ b/_posts/release/2015-09-19-accumulo-1.5.2.md
@@ -102,7 +102,7 @@ parameter, like [ACCUMULO-2360][3], to prevent this error.
 ### Offline tables can prevent tablet balancing
 
 Before 1.5.2, when a table with many tablets was created, ingested into, and
-taken offline, tablet balancing may have stoppped. This would happen if there
+taken offline, tablet balancing may have stopped. This would happen if there
 were tablet migrations for the table, because the migrations couldn't occur.
 The balancer will not run when there are outstanding migrations; therefore, a
 system could become unbalanced. [ACCUMULO-2694][4] introduces a fix to ensure
diff --git a/_posts/release/2016-06-22-accumulo-1.7.2.md b/_posts/release/2016-06-22-accumulo-1.7.2.md
index 8d156ff..e9da275 100644
--- a/_posts/release/2016-06-22-accumulo-1.7.2.md
+++ b/_posts/release/2016-06-22-accumulo-1.7.2.md
@@ -33,9 +33,9 @@ Upgrading to Apache Commons VFS 2.1 fixes several issues with classloading
out o
 
 There was a bug ([ACCUMULO-4148][ACCUMULO-4148]) where multiple put calls with identical
keys and no timestamp would exhibit different behaviour depending on whether native maps were
enabled or not. This behaviour would result in hidden mutations with native maps, and has
been corrected.
 
-### Open WAL files could prevent DataNode decomission
+### Open WAL files could prevent DataNode decommission
 
-An improvement was introduced to allow a max age before WAL files would be automatically
rolled. Without a max age, they could stay open for writing indefinitely, blocking the Hadoop
DataNode decomissioning process. For more information, see [ACCUMULO-4004][ACCUMULO-4004].
+An improvement was introduced to allow a max age before WAL files would be automatically
rolled. Without a max age, they could stay open for writing indefinitely, blocking the Hadoop
DataNode decommissioning process. For more information, see [ACCUMULO-4004][ACCUMULO-4004].
 
 ### Remove unnecessary copy of cached RFile index blocks
 
diff --git a/_posts/release/2016-09-06-accumulo-1.8.0.md b/_posts/release/2016-09-06-accumulo-1.8.0.md
index 28ba7a7..80e7ffb 100644
--- a/_posts/release/2016-09-06-accumulo-1.8.0.md
+++ b/_posts/release/2016-09-06-accumulo-1.8.0.md
@@ -29,7 +29,7 @@ very seriously and have invested much time to ensure that we meet the promises
s
 ### Speed up WAL roll overs
 
 Performance of writing mutations is improved by refactoring the
-bookeeping required for Write-Ahead Log (WAL) files and by creating a
+bookkeeping required for Write-Ahead Log (WAL) files and by creating a
 standby WAL for faster switching when the log is full. This was a
 substantial refactor in the way WALs worked, but smoothes overall
 ingest performance in addition to provides a increase in write speed
@@ -124,7 +124,7 @@ Please see the [Accumulo User Manual chapter on Iterator Testing][ITER_TEST]
for
 Previously, the default port for the monitor was 50095. You will need to update your links
to point to port 9995. The default
 port for the GC process was also changed from 50091 to 9998, although this an RPC port used
internally and automatically discovered.
 These default ports were changed because the previous defaults fell in the Linux Ephemeral
port range. This means that the operating
-system, when a port in this range was unusued, would allocate this port for dynamic network
communication. This has the side-effect of
+system, when a port in this range was unused, would allocate this port for dynamic network
communication. This has the side-effect of
 temporal bind issues when trying to start these services (as the operating
 system might have allocated them elsewhere). By moving these
 defaults out of the ephemeral range, we can guarantee that the Monitor and GC
@@ -139,7 +139,7 @@ will reliably start. These values are still configurable by setting
  * [ACCUMULO-2883] API to fetch current tablet assignments
  * [ACCUMULO-3871] Support for running integration tests in MapReduce
  * [ACCUMULO-3920] Deprecate the MockAccumulo class and remove usage in our tests
- * [ACCUMULO-4339] Make hadoop-minicluster optional dependency of acccumulo-minicluster
+ * [ACCUMULO-4339] Make hadoop-minicluster optional dependency of accumulo-minicluster
  * [ACCUMULO-4318] BatchWriter, ConditionalWriter, and ScannerBase now extend AutoCloseable
  * [ACCUMULO-4326] Value constructor now accepts Strings (and Charsequences)
  * [ACCUMULO-4354] Bump dependency versions to include gson, jetty, and sl4j
diff --git a/_posts/release/2016-09-18-accumulo-1.6.6.md b/_posts/release/2016-09-18-accumulo-1.6.6.md
index 42093ca..5053485 100644
--- a/_posts/release/2016-09-18-accumulo-1.6.6.md
+++ b/_posts/release/2016-09-18-accumulo-1.6.6.md
@@ -54,11 +54,11 @@ identical keys and no timestamp would exhibit different behaviour depending
on
 whether native maps were enabled or not. This behaviour would result in hidden
 mutations with native maps, and has been corrected.
 
-### Open WAL files could prevent DataNode decomission
+### Open WAL files could prevent DataNode decommission
 
 An improvement was introduced to allow a max age before WAL files would be
 automatically rolled. Without a max age, they could stay open for writing
-indefinitely, blocking the Hadoop DataNode decomissioning process. For more
+indefinitely, blocking the Hadoop DataNode decommissioning process. For more
 information, see [ACCUMULO-4004][ACCUMULO-4004].
 
 ### Remove unnecessary copy of cached RFile index blocks
diff --git a/_posts/release/2017-02-26-accumulo-1.8.1.md b/_posts/release/2017-02-26-accumulo-1.8.1.md
index 986b9d4..0584ffd 100644
--- a/_posts/release/2017-02-26-accumulo-1.8.1.md
+++ b/_posts/release/2017-02-26-accumulo-1.8.1.md
@@ -73,7 +73,7 @@ fixed in [ACCUMULO-4572][ACCUMULO_4572].
 
 ### HostRegexTableLoadBalancer used stale information
 
-The HostRegexTableLoadBalander maintains an internal mapping of tablet
+The HostRegexTableLoadBalancer maintains an internal mapping of tablet
 server pools and tablet server status. It was updated at a
 configurable interval initially as an optimization. Unfortunately it
 had the negative side effect of providing the assignment and balance
diff --git a/contributor/git.md b/contributor/git.md
index e389737..2a1f552 100644
--- a/contributor/git.md
+++ b/contributor/git.md
@@ -270,7 +270,7 @@ with `<apache_id>/ACCUMULO-<issue#>[-description]`.
 
     `git checkout <apache_id>/ACCUMULO-<issue#> master`
 
-2. Create the feature, commiting early and often to appropriately outline the
+2. Create the feature, committing early and often to appropriately outline the
 "story" behind the feature and it's implementation.
 
 3. As long as you have not collaborating with others, `git-rebase` your feature
diff --git a/contributor/making-release.md b/contributor/making-release.md
index 1bde7b5..78256e1 100644
--- a/contributor/making-release.md
+++ b/contributor/making-release.md
@@ -41,7 +41,7 @@ Given all of this, it's recommended that you only attempt making a release
from
 
 You should use the provided script assemble/build.sh to create the release candidate. This
script is
 desirable as it activates all necessary maven profiles in addition to verifying that certain
preconditions
-are met, like RPM signing availablilty and the ability to sign files using GPG. The --test
option can 
+are met, like RPM signing availability and the ability to sign files using GPG. The --test
option can
 be used as a dry run for creating a release candidate. The --create-release-candidate option
should be 
 used to create the actual release candidate.
 
diff --git a/contributor/verifying-release.md b/contributor/verifying-release.md
index 789e334..515589d 100644
--- a/contributor/verifying-release.md
+++ b/contributor/verifying-release.md
@@ -26,7 +26,7 @@ Below are some suggested tests that can be run (feel free to run your own
custom
 * Build the [Accumulo Examples][examples] repo using the release candidate by updating the
`accumulo.version`
   property in the `pom.xml` and using the staging repo. Also, run the unit/integration tests
using `mvn verify`.
 
-* Run Accumulo's distributed tests (i.e. random walk, continous ingest). These tests are
intended to be run for days
+* Run Accumulo's distributed tests (i.e. random walk, continuous ingest). These tests are
intended to be run for days
   on end while injecting faults into the system. These are the tests that truly verify the
correctness of Accumulo on
   real systems. Starting with 2.0, these tests are run using the [Accumulo Testing repo][at].
See the [README.md][at-readme]
   for more information.  Before 2.0, these tests are found in Accumulo tarball at `test/system/randomwalk`
and
@@ -43,7 +43,7 @@ release, the release should be vetoed via the normal voting process. New
major r
 
 ### Stand alone
 
-The following steps can be taken without having an underlying cluster. They SHOULD be handled
with each Hadoop profile available for a given release version. To activate an alternative
profile specify e.g. "-Dhadoop.profile=2" for the Hadoop 2 profile on the Maven commandline.
Some older versions of Accumulo referred to Hadoop profiles diferently; see the README that
came with said versions for details on building against different Hadoop versions.
+The following steps can be taken without having an underlying cluster. They SHOULD be handled
with each Hadoop profile available for a given release version. To activate an alternative
profile specify e.g. "-Dhadoop.profile=2" for the Hadoop 2 profile on the Maven commandline.
Some older versions of Accumulo referred to Hadoop profiles differently; see the README that
came with said versions for details on building against different Hadoop versions.
 
   1. All JUnit tests must pass.  This should be a requirement of any patch so it should never
be an issue of the codebase.
     - Use "mvn package" to run against the default profile of a particular release

-- 
To stop receiving notification emails like this one, please contact
['"commits@accumulo.apache.org" <commits@accumulo.apache.org>'].

Mime
View raw message