anchor.diff:  
   To create a stream using an `http` source, but still using the same `log` sink, we would change the original command above to
   
  -    dataflow:> stream create --definition "http | log" --name myhttpstream --deploy
  -
  +```
  +dataflow:> stream create --definition "http | log" --name myhttpstream --deploy
  +```
   which will produce the following output from the server
   
  -....
  +```
   2016-01-13 18:42:19.162  INFO 19463 --- [nio-9393-exec-7] o.s.c.d.a.s.l.OutOfProcessModuleDeployer : deploying module org.springframework.cloud.stream.module:log-sink:jar:exec:1.0.0.BUILD-SNAPSHOT instance 0
      Logs will be in /var/folders/hs/h87zy7z17qs6mcnl4hj8_dp00000gp/T/spring-cloud-data-flow-2185888994718649403/myhttpstream.log
   2016-01-13 18:42:19.180  INFO 19463 --- [nio-9393-exec-7] o.s.c.d.a.s.l.OutOfProcessModuleDeployer : deploying module org.springframework.cloud.stream.module:http-source:jar:exec:1.0.0.BUILD-SNAPSHOT instance 0
      Logs will be in /var/folders/hs/h87zy7z17qs6mcnl4hj8_dp00000gp/T/spring-cloud-data-flow-2185888994718649403/myhttpstream.http
  -....
  +```
   
   Note that we don't see anydefin other output this time until we actually post some data (using shell command). In order to see the randomly assigned port on which the http source is listening, execute:
  -
  -	dataflow:> runtime modules
  -
  +```
  +dataflow:> runtime modules
  +```
   You should see that the corresponding http source has a `url` property containing the host and port information on which it is listening. You are now ready to post to that url, e.g.:
  -
  -  dataflow:> http post --target http://localhost:1234 --data "hello"
  -  dataflow:> http post --target http://localhost:1234 --data "goodbye"
  -
  +```
  +dataflow:> http post --target http://localhost:1234 --data "hello"
  +dataflow:> http post --target http://localhost:1234 --data "goodbye"
  +```
   and the stream will then funnel the data from the http source to the output log implemented by the log sink
   
  -  2016-01-13 21:15:34.825  INFO 54348 --- [hannel-adapter1] log.sink                                 : hello
  -  2016-01-13 21:17:36.544  INFO 54348 --- [hannel-adapter1] log.sink                                 : goodbye
  +```
  +2016-01-13 21:15:34.825  INFO 54348 --- [hannel-adapter1] log.sink                                 : hello
  +2016-01-13 21:17:36.544  INFO 54348 --- [hannel-adapter1] log.sink                                 : goodbye
  +```
   
   Of course, we could also change the sink implementation. You could pipe the output to a file (`file`), to hadoop (`hdfs`) or to any of the other sink modules which are provided. You can also define your own modules.
   
   == Simple Stream Processing
   
   As an example of a simple processing step, we can transform the payload of the HTTP posted data to upper case using the stream definitions
  -
  -    http | transform --expression=payload.toUpperCase() | log
  -
  +```
  +http | transform --expression=payload.toUpperCase() | log
  +```
   To create this stream enter the following command in the shell
  -
  -    dataflow:> stream create --definition "http | transform --expression=payload.toUpperCase() | log" --name mystream --deploy
  -
  +```
  +dataflow:> stream create --definition "http | transform --expression=payload.toUpperCase() | log" --name mystream --deploy
  +```
   Posting some data (using shell command)
  -
  -  dataflow:> http post --target http://localhost:1234 --data "hello"
  -
  +```
  +dataflow:> http post --target http://localhost:1234 --data "hello"
  +```
   Will result in an uppercased 'hello' in the log
   
  -  15:18:21,345  WARN ThreadPoolTaskScheduler-1 logger.myprocstream:141 - HELLO
  +```
  +15:18:21,345  WARN ThreadPoolTaskScheduler-1 logger.myprocstream:141 - HELLO
  +```
   
   See the xref:processors#spring-cloud-stream-modules-processors[Processors] section for more information.
   
   == DSL Syntax
   
   In the examples above, we connected a source to a sink using the pipe symbol `|`. You can also pass parameters to the source and sink configurations. The parameter names will depend on the individual module implementations, but as an example, the `http` source module exposes a `server.port` setting which allows you to change the data ingestion port from the default value. To create the stream using port 8000, we would use
  -
  -    dataflow:> stream create --definition "http --server.port=8000 | log" --name myhttpstream
  -
  +```
  +dataflow:> stream create --definition "http --server.port=8000 | log" --name myhttpstream
  +```
   The shell provides tab completion for module parameters and also the shell command `module info` provides some additional documentation.  For more comprehensive documentation on module parameters, please see the xref:modules#modules[Modules] chapter.
   
   == Advanced Features
  
positive.code: 
  A high level DSL is used to create stream definitions. The DSL to define a stream that has an http source and a file sink (with no processors) is shown below
  
       http | file
  
  The DSL mimics a UNIX pipes and filters syntax. Default values for ports and filenames are used in this example but can be overridden using `--` options, such as
  
       http --port=8091 | file --dir=/tmp/httpdata/
  
  To create these stream definitions you make an HTTP POST request to the Spring Cloud Data Flow Server. More details can be found in the sections below.
  
  == Creating a Simple Stream
  
negative.code: 
  You can delete a stream by issuing the `stream destroy` command from the shell:
  
  ```
  dataflow:> stream destroy --name ticktock
  ```
  
  == Deploying and Undeploying Streams
  
  Often you will want to stop a stream, but retain the name and definition for future use. In that case you can `undeploy` the stream by name and issue the `deploy` command at a later time to restart it.
  ```
  dataflow:> stream undeploy --name ticktock
  dataflow:> stream deploy --name ticktock
  ```
  
  == Other Source and Sink Types
  
  