anchor.diff:  
   To submit to a remote cluster, you would do:
   
  -[literal]
  +[source]
   ....
   $STORM_HOME/bin/storm jar target/storm-solr-1.0.jar com.lucidworks.storm.StreamingApp \
      example.twitter.TwitterToSolrTopology -env staging
  
positive.code: 
  We’ll get into the specific details of the implementation shortly, but first, let’s see how to run the TwitterToSolrTopology using the `StreamingApp` framework. For local mode, you would do:
  
  [literal]
  ....
  java -classpath $STORM_HOME/lib/*:target/storm-solr-1.0.jar com.lucidworks.storm.StreamingApp \
     example.twitter.TwitterToSolrTopology -localRunSecs 90
  
negative.code: 
  However, you can also specify a different `Config.groovy` file by using the `-config` command-line option when deploying the topology, such as:
  
  [source]
  ....
  $STORM_HOME/bin/storm jar target/storm-solr-1.0.jar com.lucidworks.storm.StreamingApp \
     example.twitter.TwitterToSolrTopology -env staging -config MyConfig.groovy
  