Repository: beam-site
Updated Branches:
  refs/heads/asf-site 747746bc4 -> dd3a16da7


[BEAM-919] Remove remaining old use/learn links from website src


Project: http://git-wip-us.apache.org/repos/asf/beam-site/repo
Commit: http://git-wip-us.apache.org/repos/asf/beam-site/commit/84eef87d
Tree: http://git-wip-us.apache.org/repos/asf/beam-site/tree/84eef87d
Diff: http://git-wip-us.apache.org/repos/asf/beam-site/diff/84eef87d

Branch: refs/heads/asf-site
Commit: 84eef87d0f84045d4a19e00b6d210899d9323b71
Parents: 747746b
Author: melissa <[email protected]>
Authored: Tue Apr 18 18:20:29 2017 -0700
Committer: Davor Bonaci <[email protected]>
Committed: Wed Apr 19 12:07:45 2017 -0700

----------------------------------------------------------------------
 src/_posts/2016-03-17-capability-matrix.md            |  4 ++--
 src/_posts/2016-04-03-presentation-materials.md       |  4 ++--
 src/_posts/2016-06-15-first-release.md                |  4 ++--
 src/_posts/2016-08-03-six-months.md                   |  2 +-
 src/_posts/2016-10-12-strata-hadoop-world-and-beam.md |  2 +-
 src/_posts/2016-10-20-test-stream.md                  |  2 +-
 src/contribute/contribution-guide.md                  | 10 +++++-----
 src/contribute/index.md                               |  4 ++--
 src/contribute/release-guide.md                       |  8 ++++----
 src/documentation/sdks/java.md                        |  2 +-
 src/documentation/sdks/python.md                      |  2 +-
 src/get-started/mobile-gaming-example.md              |  2 +-
 src/v2/index.md                                       |  2 +-
 13 files changed, 24 insertions(+), 24 deletions(-)
----------------------------------------------------------------------


http://git-wip-us.apache.org/repos/asf/beam-site/blob/84eef87d/src/_posts/2016-03-17-capability-matrix.md
----------------------------------------------------------------------
diff --git a/src/_posts/2016-03-17-capability-matrix.md 
b/src/_posts/2016-03-17-capability-matrix.md
index a125103..775f014 100644
--- a/src/_posts/2016-03-17-capability-matrix.md
+++ b/src/_posts/2016-03-17-capability-matrix.md
@@ -579,9 +579,9 @@ With initial code drops complete ([Dataflow SDK and 
Runner](https://github.com/a
 
 While we’d love to have a world where all runners support the full suite of 
semantics included in the Beam Model (formerly referred to as the [Dataflow 
Model](http://www.vldb.org/pvldb/vol8/p1792-Akidau.pdf)), practically speaking, 
there will always be certain features that some runners can’t provide. For 
example, a Hadoop-based runner would be inherently batch-based and may be 
unable to (easily) implement support for unbounded collections. However, that 
doesn’t prevent it from being extremely useful for a large set of uses. In 
other cases, the implementations provided by one runner may have slightly 
different semantics that those provided by another (e.g. even though the 
current suite of runners all support exactly-once delivery guarantees, an 
[Apache Samza](http://samza.apache.org/) runner, which would be a welcome 
addition, would currently only support at-least-once).
 
-To help clarify things, we’ve been working on enumerating the key features 
of the Beam model in a [capability matrix]({{ site.baseurl 
}}/learn/runners/capability-matrix/) for all existing runners, categorized 
around the four key questions addressed by the model: <span 
class="wwwh-what-dark">What</span> / <span class="wwwh-where-dark">Where</span> 
/ <span class="wwwh-when-dark">When</span> / <span 
class="wwwh-how-dark">How</span> (if you’re not familiar with those 
questions, you might want to read through [Streaming 
102](http://oreilly.com/ideas/the-world-beyond-batch-streaming-102) for an 
overview). This table will be maintained over time as the model evolves, our 
understanding grows, and runners are created or features added.
+To help clarify things, we’ve been working on enumerating the key features 
of the Beam model in a [capability matrix]({{ site.baseurl 
}}/documentation/runners/capability-matrix/) for all existing runners, 
categorized around the four key questions addressed by the model: <span 
class="wwwh-what-dark">What</span> / <span class="wwwh-where-dark">Where</span> 
/ <span class="wwwh-when-dark">When</span> / <span 
class="wwwh-how-dark">How</span> (if you’re not familiar with those 
questions, you might want to read through [Streaming 
102](http://oreilly.com/ideas/the-world-beyond-batch-streaming-102) for an 
overview). This table will be maintained over time as the model evolves, our 
understanding grows, and runners are created or features added.
 
-Included below is a summary snapshot of our current understanding of the 
capabilities of the existing runners (see the [live version]({{ site.baseurl 
}}/learn/runners/capability-matrix/) for full details, descriptions, and Jira 
links); since integration is still under way, the system as whole isn’t yet 
in a completely stable, usable state. But that should be changing in the near 
future, and we’ll be updating loud and clear on this blog when the first 
supported Beam 1.0 release happens.
+Included below is a summary snapshot of our current understanding of the 
capabilities of the existing runners (see the [live version]({{ site.baseurl 
}}/documentation/runners/capability-matrix/) for full details, descriptions, 
and Jira links); since integration is still under way, the system as whole 
isn’t yet in a completely stable, usable state. But that should be changing 
in the near future, and we’ll be updating loud and clear on this blog when 
the first supported Beam 1.0 release happens.
 
 In the meantime, these tables should help clarify where we expect to be in the 
very near term, and help guide expectations about what existing runners are 
capable of, and what features runner implementers will be tackling next.
 

http://git-wip-us.apache.org/repos/asf/beam-site/blob/84eef87d/src/_posts/2016-04-03-presentation-materials.md
----------------------------------------------------------------------
diff --git a/src/_posts/2016-04-03-presentation-materials.md 
b/src/_posts/2016-04-03-presentation-materials.md
index 2a535e6..fe9f3bd 100644
--- a/src/_posts/2016-04-03-presentation-materials.md
+++ b/src/_posts/2016-04-03-presentation-materials.md
@@ -9,7 +9,7 @@ authors:
   - takidau
 ---
 
-Are you interested in giving a presentation about Apache Beam? Perhaps you 
want to talk about Apache Beam at a local Meetup or a convention. Excellent!  
The Apache Beam community is excited to expand and grow the community. To help 
kickstart this process, we are excited to announce an initial set of [Apache 
Beam presentation materials]({{ site.baseurl }}/learn/presentation-materials/) 
which anyone can use to give a presentation about Apache Beam.
+Are you interested in giving a presentation about Apache Beam? Perhaps you 
want to talk about Apache Beam at a local Meetup or a convention. Excellent!  
The Apache Beam community is excited to expand and grow the community. To help 
kickstart this process, we are excited to announce an initial set of [Apache 
Beam presentation materials]({{ site.baseurl 
}}/contribute/presentation-materials/) which anyone can use to give a 
presentation about Apache Beam.
 
 <!--more-->
 
@@ -21,4 +21,4 @@ As a community, we want to build a shared collection of high 
quality presentatio
 * Using Apache Beam with runners
     * [Google Cloud Dataflow](https://goo.gl/2ay8mi)
 
-As Apache Beam grows, so will this repository of presentation materials. We 
are excited to add new materials as the Apache Beam ecosystem grows with new 
runners, SDKs, and so on. If you are interested in contributing content or have 
a request, please see the [Apache Beam presentation materials]({{ site.baseurl 
}}/learn/presentation-materials/) page or email the 
[`[email protected]`](mailto:[email protected]) mailing list with your 
ideas or questions.
+As Apache Beam grows, so will this repository of presentation materials. We 
are excited to add new materials as the Apache Beam ecosystem grows with new 
runners, SDKs, and so on. If you are interested in contributing content or have 
a request, please see the [Apache Beam presentation materials]({{ site.baseurl 
}}/contribute/presentation-materials/) page or email the 
[`[email protected]`](mailto:[email protected]) mailing list with your 
ideas or questions.

http://git-wip-us.apache.org/repos/asf/beam-site/blob/84eef87d/src/_posts/2016-06-15-first-release.md
----------------------------------------------------------------------
diff --git a/src/_posts/2016-06-15-first-release.md 
b/src/_posts/2016-06-15-first-release.md
index fe11cae..c3c57ca 100644
--- a/src/_posts/2016-06-15-first-release.md
+++ b/src/_posts/2016-06-15-first-release.md
@@ -20,7 +20,7 @@ making them readily available for our users. The initial 
release includes the
 SDK for Java, along with three runners: Apache Flink, Apache Spark and Google
 Cloud Dataflow, a fully-managed cloud service. The release is available both
 in the [Maven Central 
Repository](http://search.maven.org/#search%7Cga%7C1%7Cg%3A%22org.apache.beam%22),
-as well as a download from the [project’s website]({{ site.baseurl 
}}/use/releases/).
+as well as a download from the [project’s website]({{ site.baseurl 
}}/get-started/downloads/).
 
 The goal of this release was process-oriented. In particular, the Beam
 community wanted to release existing functionality to our users, build and
@@ -35,5 +35,5 @@ anticipated, perhaps one every 1-2 months.
 As always, the Beam community welcomes feedback. Stabilization, usability and
 the developer experience will be our focus for the next several months. If you
 have any comments or discover any issues, I’d like to invite you to reach out
-to us via [user’s mailing list]({{ site.baseurl }}/use/mailing-lists/) or the
+to us via [user’s mailing list]({{ site.baseurl }}/get-started/support/) or 
the
 [Apache JIRA issue tracker](https://issues.apache.org/jira/browse/BEAM/).

http://git-wip-us.apache.org/repos/asf/beam-site/blob/84eef87d/src/_posts/2016-08-03-six-months.md
----------------------------------------------------------------------
diff --git a/src/_posts/2016-08-03-six-months.md 
b/src/_posts/2016-08-03-six-months.md
index 73305e4..4b57c01 100644
--- a/src/_posts/2016-08-03-six-months.md
+++ b/src/_posts/2016-08-03-six-months.md
@@ -39,5 +39,5 @@ But perhaps most importantly, we’re committed to building 
an involved, welcomi
 * Had multiple talks on Beam at venues including ApacheCon, Hadoop Summit, 
Kafka Summit, JBCN Barcelona, and Strata.
 * Presented at multiple existing meetups and are starting to organize some of 
our own.
 
-While it’s nice to reflect back on all we’ve done, we’re working full 
_stream_ ahead towards a stable release and graduation from incubator. And 
we’d love your help -- join the [mailing lists]({{ site.baseurl 
}}/use/mailing-lists/), check out the [contribution guide]({{ site.baseurl 
}}/contribute/contribution-guide/), and grab a [starter 
task](https://issues.apache.org/jira/browse/BEAM-520?jql=project%20%3D%20BEAM%20AND%20resolution%20%3D%20Unresolved%20AND%20labels%20in%20(newbie%2C%20starter))
 from Jira!
+While it’s nice to reflect back on all we’ve done, we’re working full 
_stream_ ahead towards a stable release and graduation from incubator. And 
we’d love your help -- join the [mailing lists]({{ site.baseurl 
}}/get-started/support/), check out the [contribution guide]({{ site.baseurl 
}}/contribute/contribution-guide/), and grab a [starter 
task](https://issues.apache.org/jira/browse/BEAM-520?jql=project%20%3D%20BEAM%20AND%20resolution%20%3D%20Unresolved%20AND%20labels%20in%20(newbie%2C%20starter))
 from Jira!
 

http://git-wip-us.apache.org/repos/asf/beam-site/blob/84eef87d/src/_posts/2016-10-12-strata-hadoop-world-and-beam.md
----------------------------------------------------------------------
diff --git a/src/_posts/2016-10-12-strata-hadoop-world-and-beam.md 
b/src/_posts/2016-10-12-strata-hadoop-world-and-beam.md
index 4cc9fb4..1642edd 100644
--- a/src/_posts/2016-10-12-strata-hadoop-world-and-beam.md
+++ b/src/_posts/2016-10-12-strata-hadoop-world-and-beam.md
@@ -28,5 +28,5 @@ On management and thought leader side, Beam went from 
“what’s Beam?” at pr
 
 We rounded out the tutorial with live demonstrations of Beam running on Apache 
Spark, Apache Flink, the local runner, and DataFlow runner. Then, we brought in 
the big brainpower and had a Q and A session.
 
-If you’re attending a conference, we encourage you to look for a Beam 
session. If you want to use these materials to give your own Beam talk or 
tutorial, we’re happy to help you. In addition to this tutorial, we have 
[other presentation materials]({{ site.baseurl 
}}/learn/presentation-materials/). You can reach out to us on the [user mailing 
list]({{ site.baseurl }}/use/mailing-lists/).
+If you’re attending a conference, we encourage you to look for a Beam 
session. If you want to use these materials to give your own Beam talk or 
tutorial, we’re happy to help you. In addition to this tutorial, we have 
[other presentation materials]({{ site.baseurl 
}}/contribute/presentation-materials/). You can reach out to us on the [user 
mailing list]({{ site.baseurl }}/get-started/support/).
 

http://git-wip-us.apache.org/repos/asf/beam-site/blob/84eef87d/src/_posts/2016-10-20-test-stream.md
----------------------------------------------------------------------
diff --git a/src/_posts/2016-10-20-test-stream.md 
b/src/_posts/2016-10-20-test-stream.md
index a013582..500680a 100644
--- a/src/_posts/2016-10-20-test-stream.md
+++ b/src/_posts/2016-10-20-test-stream.md
@@ -306,4 +306,4 @@ The addition of TestStream alongside window and 
pane-specific matchers in PAsser
 has enabled the testing of Pipelines which produce speculative and late panes.
 This permits tests for all styles of pipeline to be expressed directly within 
the
 Java SDK. If you have questions or comments, we’d love to hear them on the
-[mailing lists]({{ site.baseurl }}/use/mailing-lists/).
+[mailing lists]({{ site.baseurl }}/get-started/support/).

http://git-wip-us.apache.org/repos/asf/beam-site/blob/84eef87d/src/contribute/contribution-guide.md
----------------------------------------------------------------------
diff --git a/src/contribute/contribution-guide.md 
b/src/contribute/contribution-guide.md
index d55dd25..62ec895 100644
--- a/src/contribute/contribution-guide.md
+++ b/src/contribute/contribution-guide.md
@@ -18,7 +18,7 @@ We use a review-then-commit workflow in Beam for all 
contributions.
 
 **For larger contributions or those that affect multiple components:**
 
-1. **Engage**: We encourage you to work with the Beam community on the [Apache 
JIRA issue tracker](https://issues.apache.org/jira/browse/BEAM) and 
[developer’s mailing list]({{ site.baseurl }}/use/mailing-lists/) to identify 
good areas for contribution.
+1. **Engage**: We encourage you to work with the Beam community on the [Apache 
JIRA issue tracker](https://issues.apache.org/jira/browse/BEAM) and 
[developer’s mailing list]({{ site.baseurl }}/get-started/support/) to 
identify good areas for contribution.
 1. **Design:** More complicated contributions will likely benefit from some 
early discussion in order to scope and design them well.
 
 **For all contributions:**
@@ -34,7 +34,7 @@ We look forward to working with you!
 ### Mailing list(s)
 We discuss design and implementation issues on the [email protected] 
mailing list, which is archived 
[here](https://lists.apache.org/[email protected]). Join by 
emailing 
[`[email protected]`](mailto:[email protected]).
 
-If interested, you can also join the other [mailing lists]({{ site.baseurl 
}}/use/mailing-lists/).
+If interested, you can also join the other [mailing lists]({{ site.baseurl 
}}/get-started/support/).
 
 ### JIRA issue tracker
 We use the Apache Software Foundation's 
[JIRA](https://issues.apache.org/jira/browse/BEAM) as an issue tracking and 
project management tool, as well as a way to communicate among a very diverse 
and distributed set of contributors. To be able to gather feedback, avoid 
frustration, and avoid duplicated efforts all Beam-related work should be 
tracked there.
@@ -380,7 +380,7 @@ Some larger features are developed on a feature branch 
before being merged into
 To contribute code on a feature branch, use the same process as above, but 
replace `master` with the [name of the branch]({{ site.baseurl 
}}/contribute/work-in-progress/#feature-branches).
 
 Since feature branches are often used for new components, you may find that
-there is no [committer]({{ site.baseurl }}/project/team/) familiar with all 
the details of the
+there is no [committer]({{ site.baseurl }}/contribute/team/) familiar with all 
the details of the
 new language or runner. In that case, consider asking someone else familiar
 with the technology to do an initial review before looping in a committer for a
 final review and merge.
@@ -407,7 +407,7 @@ A new runner should:
 
 1. Be able to handle a subset of the model that address a significant set of 
use cases (aka. ‘traditional batch’ or ‘processing time streaming’)
 1. Update the capability matrix with the current status
-1. Add a webpage under `learn/runners`
+1. Add a webpage under `documentation/runners`
 
 A new SDK should:
 
@@ -415,7 +415,7 @@ A new SDK should:
 1. Begin fleshing out the common composite transforms (Count, Join, etc) and 
IO connectors (Text, Kafka, etc)
 1. Have at least one runner that can execute the complete model (may be a 
direct runner)
 1. Provide integration tests for executing against current and future runners
-1. Add a webpage under `learn/sdks`
+1. Add a webpage under `documentation/sdks`
 
 
 ### Website

http://git-wip-us.apache.org/repos/asf/beam-site/blob/84eef87d/src/contribute/index.md
----------------------------------------------------------------------
diff --git a/src/contribute/index.md b/src/contribute/index.md
index 6101a8a..1fa2326 100644
--- a/src/contribute/index.md
+++ b/src/contribute/index.md
@@ -20,6 +20,6 @@ Learn about the best practices for developing new PTransforms.
 #### Resources
 Resources for contributing to Beam, including mailing lists, the main GitHub 
repo, and the issues tracker.
 
-* [Mailing Lists]({{ site.baseurl }}/use/mailing-lists/)
+* [Mailing Lists]({{ site.baseurl }}/get-started/support/)
 * [Source Repository]({{ site.baseurl }}/contribute/source-repository)
-* [Issue Tracking]({{ site.baseurl }}/use/issue-tracking/)
+* [Issue Tracking]({{ site.baseurl }}/get-started/support/)

http://git-wip-us.apache.org/repos/asf/beam-site/blob/84eef87d/src/contribute/release-guide.md
----------------------------------------------------------------------
diff --git a/src/contribute/release-guide.md b/src/contribute/release-guide.md
index c60e527..4f10de2 100644
--- a/src/contribute/release-guide.md
+++ b/src/contribute/release-guide.md
@@ -15,7 +15,7 @@ The Apache Beam project periodically declares and publishes 
releases. A release
 
 The Beam community treats releases with great importance. They are a public 
face of the project and most users interact with the project only through the 
releases. Releases are signed off by the entire Beam community in a public vote.
 
-Each release is executed by a *Release Manager*, who is selected among the 
[Beam committers]({{ site.baseurl }}/project/team). This document describes the 
process that the Release Manager follows to perform a release. Any changes to 
this process should be discussed and adopted on the [dev@ mailing list]({{ 
site.baseurl }}/use/mailing-lists).
+Each release is executed by a *Release Manager*, who is selected among the 
[Beam committers]({{ site.baseurl }}/contribute/team). This document describes 
the process that the Release Manager follows to perform a release. Any changes 
to this process should be discussed and adopted on the [dev@ mailing list]({{ 
site.baseurl }}/get-started/support/).
 
 Please remember that publishing software has legal consequences. This guide 
complements the foundation-wide [Product Release 
Policy](http://www.apache.org/dev/release.html) and [Release Distribution 
Policy](http://www.apache.org/dev/release-distribution).
 
@@ -344,7 +344,7 @@ Finally, propose a pull request with these changes. 
(Don’t merge before finali
 
 1. Maven artifacts deployed to the staging repository of 
[repository.apache.org](https://repository.apache.org/content/repositories/)
 1. Source distribution deployed to the dev repository of 
[dist.apache.org](https://dist.apache.org/repos/dist/dev/beam/)
-1. Website pull request proposed to list the [release]({{ site.baseurl 
}}/use/releases/), publish the [Java API reference manual]({{ site.baseurl 
}}/documentation/sdks/javadoc/), and publish the [Python API reference 
manual]({{ site.baseurl }}/documentation/sdks/pydoc/).
+1. Website pull request proposed to list the [release]({{ site.baseurl 
}}/get-started/downloads/), publish the [Java API reference manual]({{ 
site.baseurl }}/documentation/sdks/javadoc/), and publish the [Python API 
reference manual]({{ site.baseurl }}/documentation/sdks/pydoc/).
 
 You can (optionally) also do additional verification by:
 1. Check that Python zip file contains the `README.md`, `NOTICE`, and 
`LICENSE` files.
@@ -458,7 +458,7 @@ Create a new Git tag for the released version by copying 
the tag for the final r
 
 ### Merge website pull request
 
-Merge the website pull request to [list the release]({{ site.baseurl 
}}/use/releases/), publish the [Python API reference manual]({{ site.baseurl 
}}/documentation/sdks/pydoc/), and the [Java API reference manual]({{ 
site.baseurl }}/documentation/sdks/javadoc/) created earlier.
+Merge the website pull request to [list the release]({{ site.baseurl 
}}/get-started/downloads/), publish the [Python API reference manual]({{ 
site.baseurl }}/documentation/sdks/pydoc/), and the [Java API reference 
manual]({{ site.baseurl }}/documentation/sdks/javadoc/) created earlier.
 
 ### Mark the version as released in JIRA
 
@@ -469,7 +469,7 @@ In JIRA, inside [version 
management](https://issues.apache.org/jira/plugins/serv
 * Maven artifacts released and indexed in the [Maven Central 
Repository](https://search.maven.org/#search%7Cga%7C1%7Cg%3A%22org.apache.beam%22)
 * Source distribution available in the release repository of 
[dist.apache.org](https://dist.apache.org/repos/dist/release/beam/)
 * Source distribution removed from the dev repository of 
[dist.apache.org](https://dist.apache.org/repos/dist/dev/beam/)
-* Website pull request to [list the release]({{ site.baseurl }}/use/releases/) 
and publish the [API reference manual]({{ site.baseurl 
}}/documentation/sdks/javadoc/) merged
+* Website pull request to [list the release]({{ site.baseurl 
}}/get-started/downloads/) and publish the [API reference manual]({{ 
site.baseurl }}/documentation/sdks/javadoc/) merged
 * Release tagged in the source code repository
 * Release version finalized in JIRA. (Note: Not all committers have 
administrator access to JIRA. If you end up getting permissions errors ask on 
the mailing list for assistance.)
 

http://git-wip-us.apache.org/repos/asf/beam-site/blob/84eef87d/src/documentation/sdks/java.md
----------------------------------------------------------------------
diff --git a/src/documentation/sdks/java.md b/src/documentation/sdks/java.md
index 474dc93..3275914 100644
--- a/src/documentation/sdks/java.md
+++ b/src/documentation/sdks/java.md
@@ -11,7 +11,7 @@ The Java SDK for Apache Beam provides a simple, powerful API 
for building both b
 
 ## Get Started with the Java SDK
 
-Get started with the [Beam Programming Model]({{ site.baseurl 
}}/learn/programming-guide/) to learn the basic concepts that apply to all SDKs 
in Beam.
+Get started with the [Beam Programming Model]({{ site.baseurl 
}}/documentation/programming-guide/) to learn the basic concepts that apply to 
all SDKs in Beam.
 
 See the [Java API Reference]({{ site.baseurl }}/documentation/sdks/javadoc/) 
for more information on individual APIs.
 

http://git-wip-us.apache.org/repos/asf/beam-site/blob/84eef87d/src/documentation/sdks/python.md
----------------------------------------------------------------------
diff --git a/src/documentation/sdks/python.md b/src/documentation/sdks/python.md
index 89fbb06..aeffcdc 100644
--- a/src/documentation/sdks/python.md
+++ b/src/documentation/sdks/python.md
@@ -9,7 +9,7 @@ The Python SDK for Apache Beam provides a simple, powerful API 
for building batc
 
 ## Get Started with the Python SDK
 
-Get started with the [Beam Programming Guide]({{ site.baseurl 
}}/learn/programming-guide) to learn the basic concepts that apply to all SDKs 
in Beam. Then, follow the [Beam Python SDK Quickstart]({{ site.baseurl 
}}/get-started/quickstart-py) to set up your Python development environment, 
get the Beam SDK for Python, and run an example pipeline.
+Get started with the [Beam Programming Guide]({{ site.baseurl 
}}/documentation/programming-guide) to learn the basic concepts that apply to 
all SDKs in Beam. Then, follow the [Beam Python SDK Quickstart]({{ site.baseurl 
}}/get-started/quickstart-py) to set up your Python development environment, 
get the Beam SDK for Python, and run an example pipeline.
 
 See the [Python API Reference]({{ site.baseurl }}/documentation/sdks/pydoc/) 
for more information on individual APIs.
 

http://git-wip-us.apache.org/repos/asf/beam-site/blob/84eef87d/src/get-started/mobile-gaming-example.md
----------------------------------------------------------------------
diff --git a/src/get-started/mobile-gaming-example.md 
b/src/get-started/mobile-gaming-example.md
index 8c1b5d7..7519d3b 100644
--- a/src/get-started/mobile-gaming-example.md
+++ b/src/get-started/mobile-gaming-example.md
@@ -10,7 +10,7 @@ redirect_from: /use/mobile-gaming-example/
 * TOC
 {:toc}
 
-This section provides a walkthrough of a series of example Apache Beam 
pipelines that demonstrate more complex functionality than the basic 
[WordCount]({{ site.baseurl }}/use/wordcount-example) examples. The pipelines 
in this section process data from a hypothetical game that users play on their 
mobile phones. The pipelines demonstrate processing at increasing levels of 
complexity; the first pipeline, for example, shows how to run a batch analysis 
job to obtain relatively simple score data, while the later pipelines use 
Beam's windowing and triggers features to provide low-latency data analysis and 
more complex intelligence about user's play patterns.
+This section provides a walkthrough of a series of example Apache Beam 
pipelines that demonstrate more complex functionality than the basic 
[WordCount]({{ site.baseurl }}/get-started/wordcount-example) examples. The 
pipelines in this section process data from a hypothetical game that users play 
on their mobile phones. The pipelines demonstrate processing at increasing 
levels of complexity; the first pipeline, for example, shows how to run a batch 
analysis job to obtain relatively simple score data, while the later pipelines 
use Beam's windowing and triggers features to provide low-latency data analysis 
and more complex intelligence about user's play patterns.
 
 > **Note**: These examples assume some familiarity with the Beam programming 
 > model. If you haven't already, we recommend familiarizing yourself with the 
 > programming model documentation and running a basic example pipeline before 
 > continuing. Note also that these examples use the Java 8 lambda syntax, and 
 > thus require Java 8. However, you can create pipelines with equivalent 
 > functionality using Java 7.
 

http://git-wip-us.apache.org/repos/asf/beam-site/blob/84eef87d/src/v2/index.md
----------------------------------------------------------------------
diff --git a/src/v2/index.md b/src/v2/index.md
index e4b7e0d..987f8a1 100644
--- a/src/v2/index.md
+++ b/src/v2/index.md
@@ -12,7 +12,7 @@ layout: v2home
 
 </div>
 </div>
-<p><a class="btn btn-large btn-success" href="{{ site.baseurl 
}}/get-started/releases/">Download</a></p>
+<p><a class="btn btn-large btn-success" href="{{ site.baseurl 
}}/get-started/downloads/">Download</a></p>
 </div>
 </div>
 </div>

Reply via email to