This closes apache#171

content/contribute/contribution-guide/index.html

@@ -156,6 +156,7 @@ <h1 id="apache-beam-contribution-guide">Apache Beam Contribution Guide</h1>
   <li><a href="#engage" id="markdown-toc-engage">Engage</a>    <ul>
       <li><a href="#mailing-lists" id="markdown-toc-mailing-lists">Mailing list(s)</a></li>
       <li><a href="#jira-issue-tracker" id="markdown-toc-jira-issue-tracker">JIRA issue tracker</a></li>
+      <li><a href="#online-discussions" id="markdown-toc-online-discussions">Online discussions</a></li>
     </ul>
   </li>
   <li><a href="#design" id="markdown-toc-design">Design</a></li>
@@ -254,6 +255,11 @@ <h3 id="jira-issue-tracker">JIRA issue tracker</h3>
 
 <p>For moderate or large contributions, you should not start coding or writing a design document unless there is a corresponding JIRA issue assigned to you for that work. Simple changes, like fixing typos, do not require an associated issue.</p>
 
+<h3 id="online-discussions">Online discussions</h3>
+<p>We don’t have an official IRC channel. Most of the online discussions happen in the <a href="https://apachebeam.slack.com/">Apache Beam Slack channel</a>. If you want access, you need to send an email to the user mailing list to <a href="mailto:user@beam.apache.org?subject=Regarding Beam Slack Channel&amp;body=Hello%0D%0A%0ACan someone please add me to the Beam slack channel?%0D%0A%0AThanks.">request access</a>.</p>
+
+<p>Chat rooms are great for quick questions or discussions on specialized topics. Remember that we strongly encourage communication via the mailing lists, and we prefer to discuss more complex subjects by email. Developers should be careful to move or duplicate all the official or useful discussions to the issue tracking system and/or the dev mailing list.</p>
+
 <h2 id="design">Design</h2>
 
 <p>To avoid potential frustration during the code review cycle, we encourage you to clearly scope and design non-trivial contributions with the Beam community before you start coding.</p>

content/documentation/pipelines/create-your-pipeline/index.html

@@ -272,7 +272,7 @@ <h2 id="reading-data-into-your-pipeline">Reading Data Into Your Pipeline</h2>
 <p>The following example code shows how to <code class="highlighter-rouge">apply</code> a <code class="highlighter-rouge">TextIO.Read</code> root transform to read data from a text file. The transform is applied to a <code class="highlighter-rouge">Pipeline</code> object <code class="highlighter-rouge">p</code>, and returns a pipeline data set in the form of a <code class="highlighter-rouge">PCollection&lt;String&gt;</code>:</p>
 
 <div class="language-java highlighter-rouge"><pre class="highlight"><code><span class="n">PCollection</span><span class="o">&lt;</span><span class="n">String</span><span class="o">&gt;</span> <span class="n">lines</span> <span class="o">=</span> <span class="n">p</span><span class="o">.</span><span class="na">apply</span><span class="o">(</span>
-  <span class="n">apply</span><span class="o">(</span><span class="s">"ReadLines"</span><span class="o">,</span> <span class="n">TextIO</span><span class="o">.</span><span class="na">Read</span><span class="o">.</span><span class="na">from</span><span class="o">(</span><span class="s">"gs://some/inputData.txt"</span><span class="o">));</span>
+  <span class="s">"ReadLines"</span><span class="o">,</span> <span class="n">TextIO</span><span class="o">.</span><span class="na">Read</span><span class="o">.</span><span class="na">from</span><span class="o">(</span><span class="s">"gs://some/inputData.txt"</span><span class="o">));</span>
 </code></pre>
 </div>
 

src/documentation/pipelines/create-your-pipeline.md

@@ -107,7 +107,7 @@ The following example code shows how to `apply` a `TextIO.Read` root transform t
 
 ```java
 PCollection<String> lines = p.apply(
-  apply("ReadLines", TextIO.Read.from("gs://some/inputData.txt"));
+  "ReadLines", TextIO.Read.from("gs://some/inputData.txt"));
 ```
 
 ## Applying Transforms to Process Pipeline Data
@@ -158,4 +158,4 @@ p.run().waitUntilFinish();
 
 ## What's next
 
-*   [Test your pipeline]({{ site.baseurl }}/documentation/pipelines/test-your-pipeline).
+*   [Test your pipeline]({{ site.baseurl }}/documentation/pipelines/test-your-pipeline).