diff --git a/spring-cloud-stream.html b/spring-cloud-stream.html
index 4ae13ef80..5970f3d6b 100644
--- a/spring-cloud-stream.html
+++ b/spring-cloud-stream.html
@@ -459,7 +459,7 @@ public class TimerSource {
 <pre>---
 spring:
   cloud:
-    channels:
+    stream:
       outputChannelName: ${spring.application.name:ticker}</pre>
 </div>
 </div>
@@ -514,7 +514,7 @@ In this case there is only one <code>Source</code> in the application context so
 <h2 id="_multiple_input_or_output_channels">Multiple Input or Output Channels</h2>
 <div class="sectionbody">
 <div class="paragraph">
-<p>A module can have multiple input or output channels all defined either as <code>@Input</code> and <code>@Output</code> methods in an interface (preferrable) or as bean definitions. Instead of just one channel named "input" or "output" you can add multiple <code>MessageChannel</code> methods annotated <code>input.<strong></code> or <code>output.</strong></code> and the names are converted to external channel names on the broker. The external channel names are the <code>spring.cloud.channels.[input|output]ChannelName</code> plus the <code>MessageChannel</code> bean name, period separated. In addition, the bean name can be <code>input.[queue|topic|tap]:*</code> or <code>output.[queue|topic]:*</code> (i.e. with a channel type as a colon-separated prefix), and the semantics of the external bus channel changes accordingly (a tap is like a topic). For example, you can have two <code>MessageChannels</code> called "output" and "output.topic:foo" in a module with <code>outputChannelName=bar</code>, and the result is 2 external channels called "bar" and "topic:foo.bar".</p>
+<p>A module can have multiple input or output channels all defined either as <code>@Input</code> and <code>@Output</code> methods in an interface (preferrable) or as bean definitions. Instead of just one channel named "input" or "output" you can add multiple <code>MessageChannel</code> methods annotated <code>input.<strong></code> or <code>output.</strong></code> and the names are converted to external channel names on the broker. The external channel names are the <code>spring.cloud.stream.[input|output]ChannelName</code> plus the <code>MessageChannel</code> bean name, period separated. In addition, the bean name can be <code>input.[queue|topic|tap]:*</code> or <code>output.[queue|topic]:*</code> (i.e. with a channel type as a colon-separated prefix), and the semantics of the external bus channel changes accordingly (a tap is like a topic). For example, you can have two <code>MessageChannels</code> called "output" and "output.topic:foo" in a module with <code>outputChannelName=bar</code>, and the result is 2 external channels called "bar" and "topic:foo.bar".</p>
 </div>
 </div>
 </div>
@@ -605,7 +605,7 @@ The main set of samples are "vanilla" in the sense that they are not deployable
 <div class="content">
 <pre class="highlight"><code>spring:
   cloud:
-    channels:
+    stream:
       group: tocktap
       name: logger
       index: 0
@@ -616,14 +616,14 @@ The main set of samples are "vanilla" in the sense that they are not deployable
 </div>
 </div>
 <div class="paragraph">
-<p>The <code>spring.cloud.channels.tap</code> section tells the module runner which topic you want to subscribe to. It creates a new group (a tap can&#8217;t be in the same group as the one it is tapping) and starts a new index count, in case anyone wants to listen downstream.</p>
+<p>The <code>spring.cloud.stream.tap</code> section tells the module runner which topic you want to subscribe to. It creates a new group (a tap can&#8217;t be in the same group as the one it is tapping) and starts a new index count, in case anyone wants to listen downstream.</p>
 </div>
 </div>
 </div>
 </div>
 <div id="footer">
 <div id="footer-text">
-Last updated 2015-07-22 03:21:55 UTC
+Last updated 2015-07-22 03:24:53 UTC
 </div>
 </div>
 </body>