fluo-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From mwa...@apache.org
Subject [fluo-website] branch gh-pages updated: Fixes several typos/spelling errors (#107)
Date Thu, 02 Nov 2017 21:07:00 GMT
This is an automated email from the ASF dual-hosted git repository.

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


The following commit(s) were added to refs/heads/gh-pages by this push:
     new 4252f91  Fixes several typos/spelling errors (#107)
4252f91 is described below

commit 4252f91f1127cb0343c376895ea9030e25159be9
Author: Mike Walch <mwalch@apache.org>
AuthorDate: Thu Nov 2 17:06:57 2017 -0400

    Fixes several typos/spelling errors (#107)
---
 _fluo-1-2/administration/run-fluo-in-docker.md                 | 2 +-
 _posts/blog/2015-12-22-beta-2-pre-release-stress-test.md       | 4 ++--
 _posts/blog/2017-07-26-fluo-graduates-from-apache-incubator.md | 2 +-
 _posts/release/2014-10-02-fluo-1.0.0-alpha-1.md                | 8 ++++----
 _recipes-1-2/recipes/export-queue.md                           | 9 ++++-----
 _recipes-1-2/tools/table-optimization.md                       | 6 +++---
 _recipes-1-2/tools/testing.md                                  | 2 +-
 _recipes-1-2/tools/transient.md                                | 6 +++---
 pages/how-to-contribute.md                                     | 4 ++--
 pages/pre-asf-download.md                                      | 2 +-
 pages/related-projects.md                                      | 2 +-
 tour/application-configuration.md                              | 2 +-
 tour/exercise-1.md                                             | 2 +-
 tour/index.md                                                  | 2 +-
 tour/writing-code.md                                           | 2 +-
 15 files changed, 27 insertions(+), 28 deletions(-)

diff --git a/_fluo-1-2/administration/run-fluo-in-docker.md b/_fluo-1-2/administration/run-fluo-in-docker.md
index 95b9883..ca005e8 100644
--- a/_fluo-1-2/administration/run-fluo-in-docker.md
+++ b/_fluo-1-2/administration/run-fluo-in-docker.md
@@ -113,5 +113,5 @@ Learn how to [manage Fluo applications][manage].
 [Accumulo]: https://accumulo.apache.org/
 [Hadoop]: https://hadoop.apache.org/
 [Zookeeper]: https://zookeeper.apache.org/
-[intialize]: {{ page.docs_base }}/administration/initialize
+[initialize]: {{ page.docs_base }}/administration/initialize
 [Marathon]: https://mesosphere.github.io/marathon/
diff --git a/_posts/blog/2015-12-22-beta-2-pre-release-stress-test.md b/_posts/blog/2015-12-22-beta-2-pre-release-stress-test.md
index 499e574..ea9cf07 100644
--- a/_posts/blog/2015-12-22-beta-2-pre-release-stress-test.md
+++ b/_posts/blog/2015-12-22-beta-2-pre-release-stress-test.md
@@ -4,7 +4,7 @@ date: 2015-12-22 15:30:00 +0000
 redirect_from: /beta-2-pre-release-stress-test/
 ---
 
-In preperation for a beta 2 release, the [stress test][3] was run again on EC2.
+In preparation for a beta 2 release, the [stress test][3] was run again on EC2.
 The test went well outperforming the [first stress test][1] and [beta-1 stress
 test][2]. 
 
@@ -18,7 +18,7 @@ computed 1,019,481,332 unique integers.
 The test took a total of 7 hours 30 minutes and 30 seconds.  Over this time
 period 61.7 million NodeObserver and 20 million NodeLoader transactions were
 executed.  The average rate of transactions per second for the entire test was
-2,968 tansactions per second.  At the conclusion of the test, the stress table
+2,968 transactions per second.  At the conclusion of the test, the stress table
 had 3.87 billion entries.
 
 The test was run with the following environment.
diff --git a/_posts/blog/2017-07-26-fluo-graduates-from-apache-incubator.md b/_posts/blog/2017-07-26-fluo-graduates-from-apache-incubator.md
index 35fd80c..57ac86d 100644
--- a/_posts/blog/2017-07-26-fluo-graduates-from-apache-incubator.md
+++ b/_posts/blog/2017-07-26-fluo-graduates-from-apache-incubator.md
@@ -5,7 +5,7 @@ date: 2017-07-26 06:00:00 +0000
 
 Apache Fluo graduated from the [Apache Incubator][incubator] to become a Top-Level Project!
 Graduation signifies Fluo's commitment to the meritocratic process and principles of the
Apache
-Software Foundation. For more information, see the following press annoucements :
+Software Foundation. For more information, see the following press announcements :
 
  * [Apache Software Foundation blog post][post]
  * [@TheASF Tweet][tweet]
diff --git a/_posts/release/2014-10-02-fluo-1.0.0-alpha-1.md b/_posts/release/2014-10-02-fluo-1.0.0-alpha-1.md
index 6fe979f..79689ad 100644
--- a/_posts/release/2014-10-02-fluo-1.0.0-alpha-1.md
+++ b/_posts/release/2014-10-02-fluo-1.0.0-alpha-1.md
@@ -9,7 +9,7 @@ redirect_from:
   - /release-notes/1.0.0-alpha-1/
 ---
 
-Fluo 1.0.0-alpha-1 is the first official release of Fluo. It contains 83 initial tickets
marked for this first milestone. The roadmap for this release included a working initial implementation,
completing an initial pass at the client API (which will be finalized in 1.0.0), and writing
a stress test application.  This release has not been tested much at scale and is not ready
for production use.  More scale and peformance testing will be done for the beta release.
+Fluo 1.0.0-alpha-1 is the first official release of Fluo. It contains 83 initial tickets
marked for this first milestone. The roadmap for this release included a working initial implementation,
completing an initial pass at the client API (which will be finalized in 1.0.0), and writing
a stress test application.  This release has not been tested much at scale and is not ready
for production use.  More scale and performance testing will be done for the beta release.
 
 Below are resources for this release:
 
@@ -63,7 +63,7 @@ Other important improvements and features:
 * [Fluo-98][98]   - Create a Range class for Fluo
 * [Fluo-123][123] - Hide implementation of Bytes in the API
 * [Fluo-130][130] - Expose MiniFluo in public API
-* [Fluo-131][131] - Make LoaderExector implement closeable
+* [Fluo-131][131] - Make LoaderExecutor implement closeable
 * [Fluo-147][147] - Create fluo-accumulo module for Accumulo iterators and formatter
 * [Fluo-175][175] - Add newTransaction() method to FluoClient
 * [Fluo-186][186] - Add Exceptions to API
@@ -74,7 +74,7 @@ All unit and integration tests passed.  Two [stress tests][stress] were
run succ
 
 ## Current Status of Percolator Implementation
 
-The following tables identify the features necessary for a full implementation of Percolator
and the current state of Fluo with regards to the implementation. For alpha, a test to excercise
some of these features at scale was created, however, it was not run at scale for long periods.
One of the goals for beta is to have at least a 24hr run of the scale test, on at least 20
nodes, succeed.
+The following tables identify the features necessary for a full implementation of Percolator
and the current state of Fluo with regards to the implementation. For alpha, a test to exercise
some of these features at scale was created, however, it was not run at scale for long periods.
One of the goals for beta is to have at least a 24hr run of the scale test, on at least 20
nodes, succeed.
 
 ### Necessary features:
 
@@ -86,7 +86,7 @@ The following tables identify the features necessary for a full implementation
o
 | Timestamp Oracle | Provides strictly increasing timestamps; a property required for correct
operation of the snapshot isolation protocol. |  IT,CST |
 | Oracle Failover | When an active Oracle process dies, timestamps should be served from
a different Oracle. They should never go backwards. | IT,[#37][37],[#241][241]<sup>1</sup>
|
 | Lightweight Lock Service | Makes searches for dirty notifications more efficient. Zookeeper
is used in this case. Should be low-latency, replicated, balanced, and persist to a backing
store. |    IT,CST |
-| Multithreaded Transasctions | Allows highly parallel execution of transactions and synchronization
only during get() and commit() upon which transactions actually collide. |    IT,CST |
+| Multithreaded Transactions | Allows highly parallel execution of transactions and synchronization
only during get() and commit() upon which transactions actually collide. |    IT,CST |
 | Snapshot Isolation | Non-serializable isolation mostly implemented through MVCC provided
through Accumulo's timestamp portion of the key. | IT,CST,[#240][240]<sup>1</sup>
|
 | Roll-back / Roll-forward semantics | Failures during the first phase of commit cause transactions
to be rolled back while failures during the second phase can cause them to be rolled forward.
| IT,[#240][240]<sup>1</sup> |
 
diff --git a/_recipes-1-2/recipes/export-queue.md b/_recipes-1-2/recipes/export-queue.md
index 7b42a9b..7f0a33c 100644
--- a/_recipes-1-2/recipes/export-queue.md
+++ b/_recipes-1-2/recipes/export-queue.md
@@ -32,7 +32,7 @@ public class MyObserver implements StringObserver {
     static final Column UPDATE_COL = new Column("meta", "numUpdates");
     static final Column COUNTER_COL = new Column("meta", "counter1");
 
-    //reperesents a Query system extrnal to Fluo that is updated by Fluo
+    // represents a Query system external to Fluo that is updated by Fluo
     QuerySystem querySystem;
 
     @Override
@@ -167,8 +167,7 @@ public class FluoApp {
 }
 ```
 
-Below is updated version of the observer from above thats now using an export
-queue.
+Below is updated version of the observer from above that is now using an export queue.
 
 ```java
 public class MyObserver implements StringObserver {
@@ -273,7 +272,7 @@ that creates the export value.
 In the example above only one transaction will succeed because both are setting
 `row1 fam1:qual1`.  Since adding to the export queue is part of the
 transaction, only the transaction that succeeds will add something to the
-queue.  If the funtion ek() in the example is deterministic, then both
+queue.  If the function ek() in the example is deterministic, then both
 transactions would have been trying to add the same key to the export queue.
 
 With the above method, we know that transactions adding entries to the queue for
@@ -287,7 +286,7 @@ same key.  Both transactions succeed because they are writing to different
 cells (`rowB fam1:qual2` and `rowA fam1:qual2`).  This approach makes it more
 difficult to reason about export entries with the same key, because the
 transactions adding those entries could have overlapped in time.  This is an
-example of write skew mentioned in the Percolater paper.
+example of write skew mentioned in the Percolator paper.
 
  1. TH1 : key1 = ek(`row1`,`fam1:qual1`)
  1. TH1 : val1 = ev(tx1.get(`row1`,`fam1:qual1`), tx1.get(`rowA`,`fam1:qual2`))
diff --git a/_recipes-1-2/tools/table-optimization.md b/_recipes-1-2/tools/table-optimization.md
index e2202bd..c2886c5 100644
--- a/_recipes-1-2/tools/table-optimization.md
+++ b/_recipes-1-2/tools/table-optimization.md
@@ -39,7 +39,7 @@ TableOperations.optimizeTable(fluoConf);
 ## Command Example
 
 Fluo Recipes provides an easy way to optimize a Fluo table for configured
-recipes from the command line.  This should be done after configuring reciped
+recipes from the command line.  This should be done after configuring recipes
 and initializing Fluo.  Below are example command for initializing in this way.
 
 ```bash
@@ -58,8 +58,8 @@ fluo exec app1 org.apache.fluo.recipes.accumulo.cmds.OptimizeTable
 
 ## Table optimization registry
 
-Recipes register themself by calling [TableOptimizations.registerOptimization()][1].  Anyone
can use
-this mechanism, its not limited to use by exisitng recipes.
+Recipes register themselves by calling [TableOptimizations.registerOptimization()][1].  Anyone
can use
+this mechanism, its not limited to use by existing recipes.
 
 [1]: {{ page.javadoc_core }}/org/apache/fluo/recipes/core/common/TableOptimizations.html
 [2]: {{ page.javadoc_accumulo }}/org/apache/fluo/recipes/accumulo/ops/TableOperations.html
diff --git a/_recipes-1-2/tools/testing.md b/_recipes-1-2/tools/testing.md
index cb0eb09..43314b7 100644
--- a/_recipes-1-2/tools/testing.md
+++ b/_recipes-1-2/tools/testing.md
@@ -4,7 +4,7 @@ category: tools
 order: 5
 ---
 
-Fluo includes MiniFluo which makes it possible to write an integeration test that
+Fluo includes MiniFluo which makes it possible to write an integration test that
 runs against a real Fluo instance.  Fluo Recipes provides the following utility
 code for writing an integration test.
 
diff --git a/_recipes-1-2/tools/transient.md b/_recipes-1-2/tools/transient.md
index 2e3b5ec..b9b5d72 100644
--- a/_recipes-1-2/tools/transient.md
+++ b/_recipes-1-2/tools/transient.md
@@ -7,7 +7,7 @@ order: 2
 ## Background
 
 Some recipes store transient data in a portion of the Fluo table.  Transient
-data is data thats continually being added and deleted.  Also these transient
+data is data that is continually being added and deleted.  Also these transient
 data ranges contain no long term data.  The way Fluo works, when data is
 deleted a delete marker is inserted but the data is actually still there.  Over
 time these transient ranges of the table will have a lot more delete markers
@@ -15,7 +15,7 @@ than actual data if nothing is done.  If nothing is done, then processing
 transient data will get increasingly slower over time.
 
 These deleted markers can be cleaned up by forcing Accumulo to compact the
-Fluo table, which will run Fluos garbage collection iterator. However,
+Fluo table, which will run Fluo's garbage collection iterator. However,
 compacting the entire table to clean up these ranges within a table is
 overkill. Alternatively,  Accumulo supports compacting ranges of a table.   So
 a good solution to the delete marker problem is to periodically compact just
@@ -37,7 +37,7 @@ TransientRegistry transientRegistry = new TransientRegistry(fluoConfig.getAppCon
 transientRegistry.addTransientRange(new RowRange(startRow, endRow));
 
 //Initialize Fluo using fluoConfig. This will store the registered ranges in
-//zookeeper making them availiable on any node later.
+//zookeeper making them available on any node later.
 ```
 
 ## Compacting Transient Ranges
diff --git a/pages/how-to-contribute.md b/pages/how-to-contribute.md
index 7b64e5e..2de0ce9 100644
--- a/pages/how-to-contribute.md
+++ b/pages/how-to-contribute.md
@@ -16,7 +16,7 @@ conduct also.
 
 Contributions can be made to the following repositories.  This page contains general instructions
 for all repositories.  Each repository also has a `CONTRIBUTING.md` file containing instructions
-specifaclly for it. For the links columns below, `I` is for issues and `C` is for CONTRIBUTING.md.

+specifically for it. For the links columns below, `I` is for issues and `C` is for CONTRIBUTING.md.

 
 | Repository        | Links           | Description
 | ----------------- | --------------- | -----------
@@ -49,7 +49,7 @@ specifaclly for it. For the links columns below, `I` is for issues and `C`
is fo
 
 1. Create a [Pull Request] in the appropriate repository.  If the work is not complete and
the Pull Request is for feedback, please put `[WIP]` in the subject.
 1. At least one committer (and others in the community) will review your pull request and
add any comments to your code.
-1. Push any changes from the review to the branch as new commits so the reviewer only needs
to review new changes.  Please avoid squasing commits after the review starts.  Squashing
makes it hard for the reviewer to follow the changes.
+1. Push any changes from the review to the branch as new commits so the reviewer only needs
to review new changes.  Please avoid squashing commits after the review starts.  Squashing
makes it hard for the reviewer to follow the changes.
 1. Repeat this process until a reviewer approves the pull request.
 1. When the review process is finished, all commits on the pull request may be squashed by
a committer.  Please avoid squashing as it makes it difficult for the committer to know if
they are merging what was reviewed.
 
diff --git a/pages/pre-asf-download.md b/pages/pre-asf-download.md
index d05b7a1..e00b3a7 100644
--- a/pages/pre-asf-download.md
+++ b/pages/pre-asf-download.md
@@ -9,7 +9,7 @@ permalink: /pre-asf-download/
 Releases of Fluo before it became an Apache project can obtained from [Maven
 central][dl].   The gpg signatures do not show up in the search results but are
 available for download if you add `.asc` to the download URL.  These downloads 
-used to be available on Github, see [INFRA-12374] for details on why this changed.
+used to be available on GitHub, see [INFRA-12374] for details on why this changed.
 
 After downloading a release of Apache Fluo, follow these [installation instructions][install]
to install Fluo on
 a cluster where Accumulo, Hadoop, and Zookeeper are running.
diff --git a/pages/related-projects.md b/pages/related-projects.md
index 1c04151..b1bdd7a 100644
--- a/pages/related-projects.md
+++ b/pages/related-projects.md
@@ -7,7 +7,7 @@ permalink: /related-projects/
 This page list external projects that build on Apache Fluo and may be useful.
 These projects are not necessarily affiliated with or endorsed by the 
 [Apache Software Foundation][asf]. If you would like to add a project to this 
-list, please open an issue or submit a pull request [on Github][web-ghr].
+list, please open an issue or submit a pull request [on GitHub][web-ghr].
 
 ### Projects Using Fluo
 
diff --git a/tour/application-configuration.md b/tour/application-configuration.md
index 5de8503..529ca77 100644
--- a/tour/application-configuration.md
+++ b/tour/application-configuration.md
@@ -14,7 +14,7 @@ To use application configuration, set properties with the prefix `fluo.app`
in y
 file before initialization.  Alternatively use [FluoConfiguration.getAppConfiguration()][fcogac]
to
 set these properties programmatically.  After Fluo is initialized this information can be
accessed
 anywhere by calling [FluoClient.getAppConfiguration()][fclgac],
-[ObserverProvider.Context.getAppConfigurtaion()][opgac], or [Loader.Context.getAppConfiguration()][lcgac].
+[ObserverProvider.Context.getAppConfiguration()][opgac], or [Loader.Context.getAppConfiguration()][lcgac].
 
 The following is a simple example of using application config.   This example sets some application
 config before initialization.  After initialization the configuration is accessed via
diff --git a/tour/exercise-1.md b/tour/exercise-1.md
index f1652ba..92d8afb 100644
--- a/tour/exercise-1.md
+++ b/tour/exercise-1.md
@@ -467,7 +467,7 @@ Then modify `preInit()` in `Main` to the following.
   }
 ```
 
-Add a constuctor to `ContentObserver` and modify `adjustCounts()` to the
+Add a constructor to `ContentObserver` and modify `adjustCounts()` to the
 following.
 
 ```java
diff --git a/tour/index.md b/tour/index.md
index 73a1119..36d0da3 100644
--- a/tour/index.md
+++ b/tour/index.md
@@ -25,7 +25,7 @@ updated using them. Later in the tour, you can implement this use case.
 We recommend following the tour in order. However, all pages are listed below for review.
 When on a
 tour page, the left and right keys on the keyboard can be used to navigate.  If you have
any
 questions or suggestions while going through the tour, please contact us.  There are multiple
-options for getting in touch : [mailing list, IRC][contact], and [Github Issues][issues].
 Any
+options for getting in touch : [mailing list, IRC][contact], and [GitHub Issues][issues].
 Any
 thoughts, solutions, etc  related to this tour can also be tweeted using the hashtag
 [#apachefluotour][aft].
 
diff --git a/tour/writing-code.md b/tour/writing-code.md
index 0094439..f673d94 100644
--- a/tour/writing-code.md
+++ b/tour/writing-code.md
@@ -11,7 +11,7 @@ obtain, edit, and run this basic skeleton.
 git clone -b fluo-tour https://gitbox.apache.org/repos/asf/fluo-website fluo-tour
 cd fluo-tour
 
-#edit Main (all of the following excercises will require this)
+#edit Main (all of the following exercises will require this)
 nano src/main/java/ft/Main.java
 
 #using Maven, run Main (all of the following exercises will require this)

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

Mime
View raw message