This is an automated email from the ASF dual-hosted git repository.
mwalch pushed a commit to branch asf-site
in repository https://gitbox.apache.org/repos/asf/fluo-website.git
The following commit(s) were added to refs/heads/asf-site by this push:
new 7328773 Jekyll build from gh-pages:4252f91
7328773 is described below
commit 7328773e2f2cbb10a12e1850fd481d52c99a9fdc
Author: Mike Walch <[email protected]>
AuthorDate: Thu Nov 2 17:09:44 2017 -0400
Jekyll build from gh-pages:4252f91
Fixes several typos/spelling errors (#107)
---
blog/2015/12/22/beta-2-pre-release-stress-test/index.html | 4 ++--
blog/2017/07/26/fluo-graduates-from-apache-incubator/index.html | 2 +-
docs/fluo-recipes/1.2/recipes/export-queue.html | 9 ++++-----
docs/fluo-recipes/1.2/tools/table-optimization.html | 6 +++---
docs/fluo-recipes/1.2/tools/testing.html | 2 +-
docs/fluo-recipes/1.2/tools/transient.html | 6 +++---
docs/fluo/1.2/administration/run-fluo-in-docker.html | 2 +-
feed.xml | 6 +++---
how-to-contribute/index.html | 4 ++--
pre-asf-download/index.html | 2 +-
related-projects/index.html | 2 +-
release/fluo-1.0.0-alpha-1/index.html | 8 ++++----
tour/application-configuration/index.html | 2 +-
tour/basic-read-write/index.html | 2 +-
tour/exercise-1/index.html | 2 +-
tour/index.html | 2 +-
tour/writing-code/index.html | 2 +-
17 files changed, 31 insertions(+), 32 deletions(-)
diff --git a/blog/2015/12/22/beta-2-pre-release-stress-test/index.html
b/blog/2015/12/22/beta-2-pre-release-stress-test/index.html
index a93beb6..e610587 100644
--- a/blog/2015/12/22/beta-2-pre-release-stress-test/index.html
+++ b/blog/2015/12/22/beta-2-pre-release-stress-test/index.html
@@ -119,7 +119,7 @@
<p><a class="twitter-share-button"
href="https://twitter.com/intent/tweet?text=Beta 2 pre-release stress
test&url=https://fluo.apache.org//blog/2015/12/22/beta-2-pre-release-stress-test/&via=ApacheFluo&related=ApacheFluo";
rel="nofollow" target="_blank" title="Share on Twitter">Twitter</a></p>
</div>
<div id="post-content">
- <p>In preperation for a beta 2 release, the <a
href="https://github.com/fluo-io/fluo-stress";>stress test</a> was run again on
EC2.
+ <p>In preparation for a beta 2 release, the <a
href="https://github.com/fluo-io/fluo-stress";>stress test</a> was run again on
EC2.
The test went well outperforming the <a
href="/blog/2014/12/30/stress-test-long-run/">first stress test</a> and <a
href="/release/fluo-1.0.0-beta-1/">beta-1 stress
test</a>.</p>
@@ -133,7 +133,7 @@ computed 1,019,481,332 unique integers.</p>
<p>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.</p>
<p>The test was run with the following environment.</p>
diff --git a/blog/2017/07/26/fluo-graduates-from-apache-incubator/index.html
b/blog/2017/07/26/fluo-graduates-from-apache-incubator/index.html
index 5ab0ae1..dae129d 100644
--- a/blog/2017/07/26/fluo-graduates-from-apache-incubator/index.html
+++ b/blog/2017/07/26/fluo-graduates-from-apache-incubator/index.html
@@ -121,7 +121,7 @@
<div id="post-content">
<p>Apache Fluo graduated from the <a
href="http://incubator.apache.org/";>Apache Incubator</a> 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 :</p>
+Software Foundation. For more information, see the following press
announcements :</p>
<ul>
<li><a
href="https://blogs.apache.org/foundation/entry/the-apache-software-foundation-announces5";>Apache
Software Foundation blog post</a></li>
diff --git a/docs/fluo-recipes/1.2/recipes/export-queue.html
b/docs/fluo-recipes/1.2/recipes/export-queue.html
index c0a4f54..593417f 100644
--- a/docs/fluo-recipes/1.2/recipes/export-queue.html
+++ b/docs/fluo-recipes/1.2/recipes/export-queue.html
@@ -253,7 +253,7 @@ transaction.</p>
<span class="kd">static</span> <span class="kd">final</span> <span
class="n">Column</span> <span class="n">UPDATE_COL</span> <span
class="o">=</span> <span class="k">new</span> <span
class="n">Column</span><span class="o">(</span><span
class="s">"meta"</span><span class="o">,</span> <span
class="s">"numUpdates"</span><span class="o">);</span>
<span class="kd">static</span> <span class="kd">final</span> <span
class="n">Column</span> <span class="n">COUNTER_COL</span> <span
class="o">=</span> <span class="k">new</span> <span
class="n">Column</span><span class="o">(</span><span
class="s">"meta"</span><span class="o">,</span> <span
class="s">"counter1"</span><span class="o">);</span>
- <span class="c1">//reperesents a Query system extrnal to Fluo that is
updated by Fluo</span>
+ <span class="c1">// represents a Query system external to Fluo that is
updated by Fluo</span>
<span class="n">QuerySystem</span> <span class="n">querySystem</span><span
class="o">;</span>
<span class="nd">@Override</span>
@@ -395,8 +395,7 @@ application.</p>
</code></pre>
</div>
-<p>Below is updated version of the observer from above thats now using an
export
-queue.</p>
+<p>Below is updated version of the observer from above that is now using an
export queue.</p>
<div class="language-java highlighter-rouge"><pre
class="highlight"><code><span class="kd">public</span> <span
class="kd">class</span> <span class="nc">MyObserver</span> <span
class="kd">implements</span> <span class="n">StringObserver</span> <span
class="o">{</span>
@@ -503,7 +502,7 @@ that creates the export value.</p>
<p>In the example above only one transaction will succeed because both are
setting
<code class="highlighter-rouge">row1 fam1:qual1</code>. 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.</p>
<p>With the above method, we know that transactions adding entries to the
queue for
@@ -517,7 +516,7 @@ same key. Both transactions succeed because they are
writing to different
cells (<code class="highlighter-rouge">rowB fam1:qual2</code> and <code
class="highlighter-rouge">rowA fam1:qual2</code>). 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.</p>
+example of write skew mentioned in the Percolator paper.</p>
<ol>
<li>TH1 : key1 = ek(<code class="highlighter-rouge">row1</code>,<code
class="highlighter-rouge">fam1:qual1</code>)</li>
diff --git a/docs/fluo-recipes/1.2/tools/table-optimization.html
b/docs/fluo-recipes/1.2/tools/table-optimization.html
index e32875d..cfdd6be 100644
--- a/docs/fluo-recipes/1.2/tools/table-optimization.html
+++ b/docs/fluo-recipes/1.2/tools/table-optimization.html
@@ -261,7 +261,7 @@ want to use them in production.</p>
<h2 id="command-example">Command Example</h2>
<p>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.</p>
<div class="language-bash highlighter-rouge"><pre class="highlight"><code>
@@ -280,8 +280,8 @@ fluo <span class="nb">exec </span>app1
org.apache.fluo.recipes.accumulo.cmds.Opt
<h2 id="table-optimization-registry">Table optimization registry</h2>
-<p>Recipes register themself by calling <a
href="https://static.javadoc.io/org.apache.fluo/fluo-recipes-core/1.1.0-incubating/org/apache/fluo/recipes/core/common/TableOptimizations.html";>TableOptimizations.registerOptimization()</a>.
Anyone can use
-this mechanism, its not limited to use by exisitng recipes.</p>
+<p>Recipes register themselves by calling <a
href="https://static.javadoc.io/org.apache.fluo/fluo-recipes-core/1.1.0-incubating/org/apache/fluo/recipes/core/common/TableOptimizations.html";>TableOptimizations.registerOptimization()</a>.
Anyone can use
+this mechanism, its not limited to use by existing recipes.</p>
diff --git a/docs/fluo-recipes/1.2/tools/testing.html
b/docs/fluo-recipes/1.2/tools/testing.html
index 62bad75..b79d9f3 100644
--- a/docs/fluo-recipes/1.2/tools/testing.html
+++ b/docs/fluo-recipes/1.2/tools/testing.html
@@ -226,7 +226,7 @@
<div class="col-md-2"><a class="pull-right" style="margin-top: 25px;"
href="https://github.com/apache/fluo-website/edit/master/_recipes-1-2/tools/testing.md";
role="button"><i class="glyphicon glyphicon-pencil"></i> <small>Edit this
page</small></a></div>
</div>
- <p>Fluo includes MiniFluo which makes it possible to write an integeration
test that
+ <p>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.</p>
diff --git a/docs/fluo-recipes/1.2/tools/transient.html
b/docs/fluo-recipes/1.2/tools/transient.html
index 100a19c..dd404c3 100644
--- a/docs/fluo-recipes/1.2/tools/transient.html
+++ b/docs/fluo-recipes/1.2/tools/transient.html
@@ -229,7 +229,7 @@
<h2 id="background">Background</h2>
<p>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
@@ -237,7 +237,7 @@ than actual data if nothing is done. If nothing is done,
then processing
transient data will get increasingly slower over time.</p>
<p>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
@@ -258,7 +258,7 @@ using this.</p>
<span class="n">transientRegistry</span><span class="o">.</span><span
class="na">addTransientRange</span><span class="o">(</span><span
class="k">new</span> <span class="n">RowRange</span><span
class="o">(</span><span class="n">startRow</span><span class="o">,</span> <span
class="n">endRow</span><span class="o">));</span>
<span class="c1">//Initialize Fluo using fluoConfig. This will store the
registered ranges in</span>
-<span class="c1">//zookeeper making them availiable on any node later.</span>
+<span class="c1">//zookeeper making them available on any node later.</span>
</code></pre>
</div>
diff --git a/docs/fluo/1.2/administration/run-fluo-in-docker.html
b/docs/fluo/1.2/administration/run-fluo-in-docker.html
index 66cb20d..ab19eeb 100644
--- a/docs/fluo/1.2/administration/run-fluo-in-docker.html
+++ b/docs/fluo/1.2/administration/run-fluo-in-docker.html
@@ -262,7 +262,7 @@ docker run apache/fluo classpath
<h2 id="run-application-in-docker">Run application in Docker</h2>
-<p>Before starting a Fluo oracle and worker using the Fluo Docker image,
[initialize your Fluo application][initialize].
+<p>Before starting a Fluo oracle and worker using the Fluo Docker image, <a
href="/docs/fluo/1.2/administration/initialize">initialize your Fluo
application</a>.
Next, choose a method below to run the oracle and worker(s) of your Fluo
application. In the examples below, the Fluo
application is named <code class="highlighter-rouge">myapp</code> and was
initialized using a Zookeeper node on <code
class="highlighter-rouge">zkhost</code>.</p>
diff --git a/feed.xml b/feed.xml
index 76d2a66..fd6462e 100644
--- a/feed.xml
+++ b/feed.xml
@@ -5,8 +5,8 @@
<description></description>
<link>https://fluo.apache.org//</link>
<atom:link href="https://fluo.apache.org//feed.xml"; rel="self"
type="application/rss+xml" />
- <pubDate>Tue, 31 Oct 2017 19:53:21 +0000</pubDate>
- <lastBuildDate>Tue, 31 Oct 2017 19:53:21 +0000</lastBuildDate>
+ <pubDate>Thu, 02 Nov 2017 21:09:38 +0000</pubDate>
+ <lastBuildDate>Thu, 02 Nov 2017 21:09:38 +0000</lastBuildDate>
<generator>Jekyll v3.3.1</generator>
@@ -14,7 +14,7 @@
<title>Fluo graduates from the Apache incubator!</title>
<description><p>Apache Fluo graduated from the <a
href="http://incubator.apache.org/">Apache Incubator</a> 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 :</p>
+Software Foundation. For more information, see the following press
announcements :</p>
<ul>
<li><a
href="https://blogs.apache.org/foundation/entry/the-apache-software-foundation-announces5">Apache
Software Foundation blog post</a></li>
diff --git a/how-to-contribute/index.html b/how-to-contribute/index.html
index 95e122c..ef8ad98 100644
--- a/how-to-contribute/index.html
+++ b/how-to-contribute/index.html
@@ -128,7 +128,7 @@ conduct also.</p>
<p>Contributions can be made to the following repositories. This page
contains general instructions
for all repositories. Each repository also has a <code
class="highlighter-rouge">CONTRIBUTING.md</code> file containing instructions
-specifaclly for it. For the links columns below, <code
class="highlighter-rouge">I</code> is for issues and <code
class="highlighter-rouge">C</code> is for CONTRIBUTING.md.</p>
+specifically for it. For the links columns below, <code
class="highlighter-rouge">I</code> is for issues and <code
class="highlighter-rouge">C</code> is for CONTRIBUTING.md.</p>
<table>
<thead>
@@ -197,7 +197,7 @@ git push origin fluo-301
</li>
<li>Create a <a
href="https://help.github.com/articles/about-pull-requests/";>Pull Request</a>
in the appropriate repository. If the work is not complete and the Pull
Request is for feedback, please put <code
class="highlighter-rouge">[WIP]</code> in the subject.</li>
<li>At least one committer (and others in the community) will review your
pull request and add any comments to your code.</li>
- <li>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.</li>
+ <li>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.</li>
<li>Repeat this process until a reviewer approves the pull request.</li>
<li>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.</li>
</ol>
diff --git a/pre-asf-download/index.html b/pre-asf-download/index.html
index aa82b64..708007b 100644
--- a/pre-asf-download/index.html
+++ b/pre-asf-download/index.html
@@ -121,7 +121,7 @@
<p>Releases of Fluo before it became an Apache project can obtained from <a
href="https://search.maven.org/#search|gav|1|g%3A%22io.fluo%22%20AND%20a%3A%22fluo-distribution%22">Maven
central</a>. The gpg signatures do not show up in the search results but are
available for download if you add <code class="highlighter-rouge">.asc</code>
to the download URL. These downloads
-used to be available on Github, see <a
href="https://issues.apache.org/jira/browse/INFRA-12374";>INFRA-12374</a> for
details on why this changed.</p>
+used to be available on GitHub, see <a
href="https://issues.apache.org/jira/browse/INFRA-12374";>INFRA-12374</a> for
details on why this changed.</p>
<p>After downloading a release of Apache Fluo, follow these <a
href="/docs/fluo/1.0.0-beta-2/prod-fluo-setup/">installation instructions</a>
to install Fluo on
a cluster where Accumulo, Hadoop, and Zookeeper are running.</p>
diff --git a/related-projects/index.html b/related-projects/index.html
index 9140459..54018f7 100644
--- a/related-projects/index.html
+++ b/related-projects/index.html
@@ -119,7 +119,7 @@
<p>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
<a href="https://www.apache.org/";>Apache Software Foundation</a>. If you would
like to add a project to this
-list, please open an issue or submit a pull request <a
href="https://github.com/apache/fluo-website";>on Github</a>.</p>
+list, please open an issue or submit a pull request <a
href="https://github.com/apache/fluo-website";>on GitHub</a>.</p>
<h3 id="projects-using-fluo">Projects Using Fluo</h3>
diff --git a/release/fluo-1.0.0-alpha-1/index.html
b/release/fluo-1.0.0-alpha-1/index.html
index b655ddd..5e3c661 100644
--- a/release/fluo-1.0.0-alpha-1/index.html
+++ b/release/fluo-1.0.0-alpha-1/index.html
@@ -122,7 +122,7 @@
<div class="post-content">
- <p>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.</p>
+ <p>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.</p>
<p>Below are resources for this release:</p>
@@ -179,7 +179,7 @@
<li><a href="https://github.com/fluo-io/fluo/issues/98";>Fluo-98</a> -
Create a Range class for Fluo</li>
<li><a href="https://github.com/fluo-io/fluo/issues/123";>Fluo-123</a> - Hide
implementation of Bytes in the API</li>
<li><a href="https://github.com/fluo-io/fluo/issues/130";>Fluo-130</a> -
Expose MiniFluo in public API</li>
- <li><a href="https://github.com/fluo-io/fluo/issues/131";>Fluo-131</a> - Make
LoaderExector implement closeable</li>
+ <li><a href="https://github.com/fluo-io/fluo/issues/131";>Fluo-131</a> - Make
LoaderExecutor implement closeable</li>
<li><a href="https://github.com/fluo-io/fluo/issues/147";>Fluo-147</a> -
Create fluo-accumulo module for Accumulo iterators and formatter</li>
<li><a href="https://github.com/fluo-io/fluo/issues/175";>Fluo-175</a> - Add
newTransaction() method to FluoClient</li>
<li><a href="https://github.com/fluo-io/fluo/issues/186";>Fluo-186</a> - Add
Exceptions to API</li>
@@ -191,7 +191,7 @@
<h2 id="current-status-of-percolator-implementation">Current Status of
Percolator Implementation</h2>
-<p>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.</p>
+<p>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.</p>
<h3 id="necessary-features">Necessary features:</h3>
@@ -235,7 +235,7 @@
<td>IT,CST</td>
</tr>
<tr>
- <td>Multithreaded Transasctions</td>
+ <td>Multithreaded Transactions</td>
<td>Allows highly parallel execution of transactions and synchronization
only during get() and commit() upon which transactions actually collide.</td>
<td>IT,CST</td>
</tr>
diff --git a/tour/application-configuration/index.html
b/tour/application-configuration/index.html
index d2a3845..e0191a0 100644
--- a/tour/application-configuration/index.html
+++ b/tour/application-configuration/index.html
@@ -129,7 +129,7 @@ initialization any Fluo client or Observer can access the
configuration.</p>
file before initialization. Alternatively use <a
href="https://javadoc.io/page/org.apache.fluo/fluo-api/1.1.0-incubating/org/apache/fluo/api/config/FluoConfiguration.html#getAppConfiguration--";>FluoConfiguration.getAppConfiguration()</a>
to
set these properties programmatically. After Fluo is initialized this
information can be accessed
anywhere by calling <a
href="https://javadoc.io/page/org.apache.fluo/fluo-api/1.1.0-incubating/org/apache/fluo/api/client/FluoClient.html#getAppConfiguration--";>FluoClient.getAppConfiguration()</a>,
-<a
href="https://javadoc.io/page/org.apache.fluo/fluo-api/1.1.0-incubating/org/apache/fluo/api/observer/ObserverProvider.Context.html#getAppConfiguration--";>ObserverProvider.Context.getAppConfigurtaion()</a>,
or <a
href="https://javadoc.io/page/org.apache.fluo/fluo-api/1.1.0-incubating/org/apache/fluo/api/client/Loader.Context.html#getAppConfiguration--";>Loader.Context.getAppConfiguration()</a>.</p>
+<a
href="https://javadoc.io/page/org.apache.fluo/fluo-api/1.1.0-incubating/org/apache/fluo/api/observer/ObserverProvider.Context.html#getAppConfiguration--";>ObserverProvider.Context.getAppConfiguration()</a>,
or <a
href="https://javadoc.io/page/org.apache.fluo/fluo-api/1.1.0-incubating/org/apache/fluo/api/client/Loader.Context.html#getAppConfiguration--";>Loader.Context.getAppConfiguration()</a>.</p>
<p>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/basic-read-write/index.html b/tour/basic-read-write/index.html
index 38c74f6..c164a65 100644
--- a/tour/basic-read-write/index.html
+++ b/tour/basic-read-write/index.html
@@ -121,7 +121,7 @@
the <code class="highlighter-rouge">exercise(MiniFluo, FluoClient)</code>
function in <a
href="https://github.com/apache/fluo-website/tree/fluo-tour/src/main/java/ft/Main.java";>src/main/java/ft/Main.java</a>.
Then run
<code class="highlighter-rouge">ft.Main</code> as previously mentioned.</p>
-<div class="language-java highlighter-rouge"><pre class="highlight"><code>
<span class="kd">private</span> <span class="kd">static</span> <span
class="kt">void</span> <span class="nf">exercises</span><span
class="o">(</span><span class="n">MiniFluo</span> <span
class="n">mini</span><span class="o">,</span> <span class="n">FluoClient</span>
<span class="n">client</span><span class="o">)</span> <span class="o">{</span>
+<div class="language-java highlighter-rouge"><pre class="highlight"><code>
<span class="kd">private</span> <span class="kd">static</span> <span
class="kt">void</span> <span class="nf">exercise</span><span
class="o">(</span><span class="n">MiniFluo</span> <span
class="n">mini</span><span class="o">,</span> <span class="n">FluoClient</span>
<span class="n">client</span><span class="o">)</span> <span class="o">{</span>
<span class="n">String</span> <span class="n">row</span> <span
class="o">=</span> <span class="s">"kerbalnaut0001"</span><span
class="o">;</span>
<span class="n">Column</span> <span class="n">fName</span> <span
class="o">=</span> <span class="k">new</span> <span
class="n">Column</span><span class="o">(</span><span
class="s">"name"</span><span class="o">,</span> <span
class="s">"first"</span><span class="o">);</span>
<span class="n">Column</span> <span class="n">lName</span> <span
class="o">=</span> <span class="k">new</span> <span
class="n">Column</span><span class="o">(</span><span
class="s">"name"</span><span class="o">,</span> <span
class="s">"last"</span><span class="o">);</span>
diff --git a/tour/exercise-1/index.html b/tour/exercise-1/index.html
index 468e079..9134115 100644
--- a/tour/exercise-1/index.html
+++ b/tour/exercise-1/index.html
@@ -588,7 +588,7 @@ counts by updating an inverted index of word counts.</p>
</code></pre>
</div>
-<p>Add a constuctor to <code class="highlighter-rouge">ContentObserver</code>
and modify <code class="highlighter-rouge">adjustCounts()</code> to the
+<p>Add a constructor to <code class="highlighter-rouge">ContentObserver</code>
and modify <code class="highlighter-rouge">adjustCounts()</code> to the
following.</p>
<div class="language-java highlighter-rouge"><pre class="highlight"><code>
diff --git a/tour/index.html b/tour/index.html
index 2bd02d4..6dc86f9 100644
--- a/tour/index.html
+++ b/tour/index.html
@@ -134,7 +134,7 @@ updated using them. Later in the tour, you can implement
this use case.</p>
<p>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 : <a href="/contactus/">mailing list, IRC</a>,
and <a href="https://github.com/apache/fluo-website/issues";>Github Issues</a>.
Any
+options for getting in touch : <a href="/contactus/">mailing list, IRC</a>,
and <a href="https://github.com/apache/fluo-website/issues";>GitHub Issues</a>.
Any
thoughts, solutions, etc related to this tour can also be tweeted using the
hashtag
<a href="https://twitter.com/hashtag/apachefluotour";>#apachefluotour</a>.</p>
diff --git a/tour/writing-code/index.html b/tour/writing-code/index.html
index 506c140..a257f9a 100644
--- a/tour/writing-code/index.html
+++ b/tour/writing-code/index.html
@@ -125,7 +125,7 @@ obtain, edit, and run this basic skeleton.</p>
git clone -b fluo-tour https://gitbox.apache.org/repos/asf/fluo-website
fluo-tour
<span class="nb">cd </span>fluo-tour
-<span class="c">#edit Main (all of the following excercises will require
this)</span>
+<span class="c">#edit Main (all of the following exercises will require
this)</span>
nano src/main/java/ft/Main.java
<span class="c">#using Maven, run Main (all of the following exercises will
require this)</span>
--
To stop receiving notification emails like this one, please contact
['"[email protected]" <[email protected]>'].
