Added logbrowser text

README.md

@@ -33,6 +33,6 @@ Running the above example opens a GUI showing the current state of the three rob
 
 A gray arrow between two robots indicates that the source robot will yield to the target robot. Priorities are computed every time a new mission is added. If multiple missions are added in batch, yielding behavior follows a fixed priority which can be specified programmatically. Driving robots always have priority over robots whose missions have been newly computed. The specific poses at which robots yield are computed on the fly based on the current positions of robots and the intersecting areas of their trajectory envelopes (critical sections). This makes it possible to achieve "following" behavior, that is, the yielding pose of a robot is updated online while the "leading" robot drives.
 
-More detailed information is posted in the terminal. It can be inspected offline by running class ```coordination_oru.util.BrowseLogs```, which opens a log browsing window with a panel with the output of each thread that ran in the previous execution of the test program (messages produced concurrently with the one at the current caret position are highlighted).
+More detailed information is posted in the terminal. It can be inspected offline by running class ```coordination_oru.util.BrowseLogs```, which opens a log browsing GUI. The GUI shows a panel with the output of each thread that ran in the previous execution of the test program. Messages produced concurrently with the one at the current caret position are highlighted.
 
 ![alt text](images/logs.png "LogBrowser GUI")