README.md in safubot-0.0.5 vs README.md in safubot-0.0.6

@@ -55,13 +55,13 @@
 		  respond req, "#{e}"
 		end
 	  end
 	end
 
-	# This will fork the Twitter/XMPP streaming processes as needed
-	# and then wait for them. You can call run_nowait if you want
-	# a non-blocking form.
+	# This will run the Twitter/XMPP streaming processes.
+	# If both are needed, the first-enabled one will be forked
+	# into its own process.
 	NiftyBot.new.run
 
 ## <a name="logging">Logging</a>
 Safubot::Log behaves as a Logger instance and will write to stdout by default. You can also tell it to write to a file:
 	Safubot::Log.path = "/some/cool/logfile"
@@ -94,6 +94,6 @@
 	  @xmpp.tell('^_^@jabber.org', "You'd best be maintaining safubot!")
 	end
 
 ## <a name="caveats">Caveats</a>
 
-I've yet to determine how to make multiple libraries with their own EventMachine loops play nice together, so the TweetStream and Blather clients are currently run in their own processes. Keep in mind the effect this will have on the execution context of your event handlers. MongoDB is your friend!
+I've yet to determine how to make multiple libraries with their own EventMachine loops play nice together, so the TweetStream and Blather clients are currently run in separate processes. Keep in mind the effect this will have on the execution context of your event handlers. MongoDB is your friend!