Remove --backend flag for now; keep everything default.

docs/tutorials/getting-started-centralized.md

@@ -199,15 +199,13 @@ Run this on the same server as your elasticsearch server.
 To run the logstash web server, just run the jar with 'web' as the first
 argument. 
 
-    java -jar logstash-%VERSION%-flatjar.jar web --backend elasticsearch://127.0.0.1/
-
-As with the indexer, you should see the Logstash web interface connection:
-
-    [2012-07-02 13:28:34,818][INFO ][cluster.service          ] [Baron Samedi] added {[Nebulon][kaO6QIojTIav2liuTjGOsA][inet[/192.168.1.194:9302]]{client=true, data=false},}
+    java -jar logstash-%VERSION%-flatjar.jar web
 
 Just point your browser at the http://127.0.0.1:9292/ and start searching
 logs!
 
+The web interface is called 'kibana' - you can learn more about kibana at <http://kibana.org>
+
 # Distributing the load
 At this point we've been simulating a distributed environment on a single machine. If only the world were so easy.
 In all of the example configurations, we've been explicitly setting the connection to connect to `127.0.0.1` despite the fact in most network-related plugins, that's the default host.

docs/tutorials/getting-started-simple.md

@@ -127,9 +127,9 @@ Obviously this is fairly useless this way. Let's add the final step and test wit
 We've already proven that events can make it into Elasticsearch. However using curl for everything is less than ideal.
 Logstash ships with a built-in web interface. It's fairly spartan but it's a good proof-of-concept. Let's restart our logstash process with an additional option:
 
-    java -jar logstash-%VERSION%-flatjar.jar agent -f logstash-simple.conf -- web --backend elasticsearch://localhost/
+    java -jar logstash-%VERSION%-flatjar.jar agent -f logstash-simple.conf -- web
 
-One important thing to note is that the `web --backend` option is actually its own set of commmand-line options. We're essentially starting two programs in one.
+One important thing to note is that the `web` option is actually its own set of commmand-line options. We're essentially starting two programs in one.
 This is worth remembering as you move to an external Elasticsearch server. The options you specify in your logstash.conf have no bearing on the web ui. It has its own options.
 
 Again, the reason for testing without the web interface is to ensure that the logstash agent itself is getting events into Elasticsearch. This is different than the Logstash web ui being able to read them.
@@ -178,7 +178,7 @@ Put this in a file called "logstash-complex.conf"
 
 Now run it all (again. Be sure to stop your previous Logstash tests!):
 
-    java -jar logstash-%VERSION%-flatjar.jar agent -f logstash-complex.conf -- web --backend elasticsearch://localhost/
+    java -jar logstash-%VERSION%-flatjar.jar agent -f logstash-complex.conf -- web
 
 Point your browser at <http://yourserver:9292> and start searching!